-
Notifications
You must be signed in to change notification settings - Fork 10
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
XSLT for LOC XML to PRONOM #15
Comments
Also, sorry for the poor formatting |
Many thanks @archivist-liz! If I can help untangle our XML, please shout. You are correct that we can have multiples of certain fields, depending on the scope of the FDD. |
@archivist-liz no worries I fixed the formatting :-) |
Thanks @adamretter! This makes it look cleaner. Sadly there are still some intellectual issues (like what to do when there are multiple MIME types, etc). |
That depends on how you'd like such multiple-valued fields to be displayed. Do you want them all concatenated in one CSV cell like "audio/mid audio/m audio/midi ..." or do you want one CSV column per MIME type? |
Taking @kmurmur's mapping in Issue #7 I tried to start writing an XSLT to extract the relevant fields and output to a CSV. This is a work in progress at best. The LOC FDD contains multiple entries for certain fields, so I'm having trouble mapping/extracting them, for example MIME Type. (This probably mostly has to do with my week xml/xslt skills, but I'm still at a big of a loss here.) Example from LOC FDD 119 on MIDI:
Secondly, due to the formatting within the XML, I can't get a string delimiter to function right. It works better with a single quote, but still not all the time. I'm attaching
a screenshot of the command running over a directory with all the LOC FDD XML files (which can be downloaded here: https://www.loc.gov/preservation/digital/formats/fddXML.zip), and the resulting csv file (saved as xslx). Not really sure whether it's worth it to keep working on this in this way.
pronomtest1.xlsx
Here's the xslt code:
The text was updated successfully, but these errors were encountered: