-
Notifications
You must be signed in to change notification settings - Fork 6
2023 01 19 Board Meeting Notes
- Karin Bredenberg
- Aaron Elkiss
- Juha Lehtonen
- Tobias Steinke
- Robin Wendler
- Inge Hofsink
- Andreas Nef
The deadline for iPRES submissions is March 10, 2023. A paper is needed for a submission. We will submit a tutorial for METS 2. This will be similar to the tutorials for METS 1 we did it the past, but instead of presenting use cases in the second part we will present transformations from METS 1 to METS 2. Karin will provide an updated version of the old tutorial submission as starting point for our new submission. As many of us don't know yet for sure if we will be in Champaign, the presenters are not yet decided.
The video recordings of the iPRES 2022 presentations are now available on YouTube. A link to the video of the METS 2 presentation will be send to the METS mailing list by Tobias as a reminder to provide feedback.
We will post more requests for feedback on other mailing lists like PREMIS or MODS. The mail text should be enhanced with a link to the video of the iPRES 2022 presentation. Inge will present METS 2 at the Rosetta WG next week and provide the feedback that she got afterwards.
Aaron created a XSLT (https://gist.github.com/aelkiss/453491999e1b6bbd541d281d888f71ea) for METS 1 to METS 2 and tested it with examples of the registered profiles. Several examples had nested File Groups. Currently these will not be transformed to METS 2. There were a few other things, but overall the transformations worked pretty good. A difficulty might be removing the old name space declarations. Karin pointed out a similar transformation that might help by finding a solution for this problem: https://github.com/SAA-SDT/eac1-to-eac2-conversion
The priority for now is to create the iPRES submission for March.
The fixed values lists of METS 1 can be used as a starting point for controlled vocabularies. But are we able to maintain these and how? An editable version on the LOC web page might be too complicated. XML versions of the lists for usage with Schematron would make sense. Maybe a web text version of the lists could be automatically derived from the XML files.