Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Signature file improvements? #80

Closed
Hwesta opened this issue Oct 6, 2016 · 4 comments
Closed

Signature file improvements? #80

Hwesta opened this issue Oct 6, 2016 · 4 comments
Labels
feature New functionality to be developed OAG Issues to be discussed by OPF Advisory Group P2 Medium priority issues to be scheduled in a future release

Comments

@Hwesta
Copy link
Contributor

Hwesta commented Oct 6, 2016

Some ideas for improving how signature files are handled

One idea is to use Roy to create signature files. This would allow access to a wider range of formats since it can include information from Apache Tika, freedesktop.org MIME-info and Library of Congress FDDs.

Another is to use DROID's signature files directly, since they're what PRONOM offers by default, and not have to perform a transformation. This may be a simpler change than above.

Other suggestions welcome!

@ghost ghost added feature New functionality to be developed P2 Medium priority issues to be scheduled in a future release labels Mar 13, 2019
@carlwilson carlwilson self-assigned this May 5, 2020
@carlwilson
Copy link
Member

This needs decomposing in the light of other signature work, @carlwilson to pick up with sig file review.

@carlwilson carlwilson added this to the v1.6 milestone May 5, 2020
@carlwilson
Copy link
Member

Another is to use DROID's signature files directly, since they're what PRONOM offers by default, and not have to perform a transformation. This may be a simpler change than above.

This isn't the case because the reason for compiling the sigs is that they can be then used with a standard regular expression engine. Using the PRONOM sigs "raw" would necessitate the development of a matching algorithm instead.

The idea of using Roy to allow other sig sources is definitely interesting though.

@carlwilson carlwilson linked a pull request Apr 20, 2021 that will close this issue
@carlwilson carlwilson removed a link to a pull request Apr 20, 2021
@carlwilson carlwilson added the OAG Issues to be discussed by OPF Advisory Group label Jun 15, 2022
@carlwilson carlwilson removed this from the v1.6 milestone Jun 15, 2022
@carlwilson
Copy link
Member

Hackathon 2023 Review: Not selected for initial tasks. Adding support for multiple signature sources is likely a prerequisite. Doing that well/properly is a task in itself and should be logged as a feature request.

@carlwilson
Copy link
Member

Closing this as is covered by #218

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New functionality to be developed OAG Issues to be discussed by OPF Advisory Group P2 Medium priority issues to be scheduled in a future release
Projects
None yet
Development

No branches or pull requests

2 participants