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

Create a file identification/characterization service #308

Closed
ruebot opened this issue Jul 24, 2016 · 6 comments
Closed

Create a file identification/characterization service #308

ruebot opened this issue Jul 24, 2016 · 6 comments

Comments

@ruebot
Copy link
Member

ruebot commented Jul 24, 2016

This service would do file identification and characterization on NonRDFSources.

This microservice would:

  1. Extract file identification/characterization using FITS
    • FITS could be run locally on the server
    • FITS could be run as a web service on another server
  2. Selected output from FITS would be save as properties on the resource. We will use this Technical Metadata Profile.
  3. FITS xml output would be saved as a NonRDFSource, and will be related to the NonRDFSource FITS was run on with an iana:describes predicate

The information gathered by this microservice would inform PDX and derivative creation microservices.

@Islandora-CLAW/committers @Islandora-CLAW/sprinters let me know what you think.

@acoburn
Copy link
Contributor

acoburn commented Jul 25, 2016

Feel free to make use of this Camel-based service if it would be useful: https://gitlab.amherst.edu/acdc/repository-extension-services/tree/master/acrepo-exts-fits

Given a URL prefix (e.g. http://example.org/technical/metadata), the path will be mapped to a Fedora object (e.g. http://example.org/technical/metadata/object/foo -> http://repository.example.org/fcrepo/rest/object/foo), the binary is POSTed to a FITS Servlet (running somewhere) and the XML metadata is returned. It runs in OSGi and is intended to be compatible with API-X.

@acoburn
Copy link
Contributor

acoburn commented Jul 25, 2016

Note: the acrepo-exts-fits service only performs step 1 from above. I have not yet written 2 or 3, but I will need them eventually. I was anticipating that steps 2 and 3 would be written in some scripting language (personally, I'd choose python, but if you all plan to write it in PHP, I'd be inclined to use your code).

@ruebot
Copy link
Member Author

ruebot commented Jul 25, 2016

@acoburn browsing through y'alls code, I'm not a 100% certain, but are y'all using the FITS webservice?

@acoburn
Copy link
Contributor

acoburn commented Jul 25, 2016

@ruebot yes, I'm using the webservice. The main reason for that is to avoid needing to save the fedora:Binary to disk before invoking FITS. This way, it also gives me the flexibility to run the FITS webservice wherever I want (i.e. on a separate system).

@ruebot
Copy link
Member Author

ruebot commented Jul 25, 2016

@acoburn EXCELLENT. I think this will make @DiegoPino happy, and possibly Danny in 7 days 😄

note to self, create a CLAW Call agenda item to talk about the future of Alpaca, and how Amherst's work might fit into it

@ruebot
Copy link
Member Author

ruebot commented Jul 25, 2016

https://github.com/Islandora-CLAW/CLAW/wiki/August-10,-2016#agenda -- Give Danny until the second week 😄

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

No branches or pull requests

3 participants