Closed mcantelon closed 7 years ago
I like this idea, but I think it might be best suited for a separate repo, since it's a significant departure from the existing behaviour.
The current format returned is a direct representation of the internal structures in metsrw. While simple, I'm not sure that is the best API for users. More thought should be put into the best way to represent that data for queries - eg. reflecting the structure of a METS file (dmdsec, amdsec, filesec, structmap, etc), reflecting information about objects (objects with all the information about a file, including its amdsec, dmdsec, derivatives, etc), reflecting internal data structures, or something else
This is true generally in metsrw - that more development on the API structure and goals needs to happen, and that work should be a precursor to expanding the API itself.
I think it's time to close this PR but I won't delete the branch.
REST server for METS parsing.