January 14, 2026 Board Meeting - mets/METS-board GitHub Wiki

Attendees

Excuses: Inge, Aaron, Robin

From last meeting: can we use specific styles to accommodate this? https://github.com/mets/METS-guide/issues/57
We would not have to create PDF files manually each time a change is done to the guide.

Tobias: Be more explicit regarding the necessity to keep the correct specific version of the METS schema.
Karin: One should generally keep the respective version with the packages themselves.
Juha: You can create a URI rewriting catalog to use local paths.
Karin: We can abolutely be more specific about the need to store local copies and be clear about the respective versions, but not necessarily how to implement as these are quite individual.
Link to practical examples (Juha?)

How does the validation relate to the profiles? e-ARK does reference from the profiles to Schematron rules.
Need an example of a METS version 2 profile.
Requires finalization of the draft version of the profiles for METS version 2.
For the context of validation, we don't necessarily need entire profile documents.

Call for submission is open, closes on March 9: https://ipres2026.dk/call-for-contributions/submission-guidelines/submission-instructions-peer-reviewed/
Karin: Difficult to understand the needs from previous iPres, attendees were partly expecting and introduction to METS rather than an open discussion.
Tobias: Maybe go back to a tutorial/workshop again? A paper is difficult to imagine.
Andreas: Doing something focussed on curernt work: validation/migration?
Tobias: similar to workshop 2023: introduction to METS mostly version 2, migration, examples
Karin: 2023 tutorial had already a section on conformance.
Tobias will create a draft.