Skip to content

Conversation

ross-spencer
Copy link
Contributor

@ross-spencer ross-spencer commented Sep 27, 2020

To workaround #3 we now forward the request to a locally running copy of the signature development utility 1.0. The code is in the PHP folder and the new bootstrap piece converts the signal from the new web form into legacy compatible sequences. The PHP code has not been changed other than to send the XML back to the caller slightly differently. 1.0 is a well-proven application and so users should be able to take confidence in the output of this work.

This work won't be merged as-is just yet. I think we'll keep it in a workaround branch, possibly a new release.

Notes on installation are: here.

Connected to #3

PUID and MIMEType were not being output correctly. A mix of copy
and paste errors and an oversight!
Standard signature now outputs:

   * {format-name}-{format-version}-signature-file.xml

Container signature now outputs:

   * {format-description]-{format-puid}-{today's-date}.xml
We had some left over JavaScript after simplifying the clone method
and so this is removed here. The form field offsets are also reset
to zero which is more intuitive for those that want to set them
explicitly.
We reduce some of the default percentages in Skeleton web-framework
to present a more condensed layout.
@ross-spencer ross-spencer force-pushed the bootstrap-utility-1.0 branch from 0ec49a5 to 85efed6 Compare October 2, 2020 01:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant