2019 01 24 Board Meeting Notes - mets/METS-board GitHub Wiki

Attendees:

  • Aaron Elkiss
  • Karin Bredenburg
  • Sean Mosely
  • Andreas Nef
  • Tobias Steinke

Notes from last time are still in a draft email. Aaron to update based on questions about XLink.

F2F meeting / iPRES 2019

The F2F is preferred for iPRES in Amsterdam. Karin discovered that ICA is going to be in Adelaide this year (with the same date as originally planned), not Edinburgh?

Karin had uploaded a link to her Google Drive draft for submission for https://drive.google.com/drive/folders/1sLr1owm2vPdcnOief-DUEcpf_kNPtVfl. The last day for submission is the 18th of March.

Karin is working on three submissions:

  • Preservation Metadata Workshop (Combination METS and PREMIS)
  • METS Tutorial (METS Board)
  • PREMIS Tutorial (PREMIS EC)

Combined PREMIS and METS tutorial seems promising. Need to have 3 people on the paper. Not all 3 need to go. There were 3 for the Boston tutorial so we could change who was talking. We can re-use a lot from that tutorial, probably almost everything. Last time Karin, Tom, Juha talked. Andreas is very likely to attend, so can be a part of that. We will put Sean's name on it as well as Juha's which might help in him getting funding. Sean still might not be able to make it. Karin, Andreas, Tobias will likely be able to make it. Hopefully others will be able to make it as well. Karin will put her name on all 3 tutorials to make sure they don't happen at the same time.

Karin will work on the submissions, others should feel free to make edits as well. They are in Word format now and that's the format they ultimately want submission in. Probably not many changes needed to the tutorial. Mostly we might want to think about more exercises.

There is another meeting on the calendar (7 Mar) before submission deadline. We should try to have everything finalized by then.

Besides a tutorial we need to check to see that we can have a meeting room for a board meeting.

METS Rights Schema

We should be set to go. Do we need anything from Nancy (as the creator?) Shouldn't need anything but permission. Need to see what DLF needs for assigning permission. ** Will ask Robin to contact DLF or otherwise look into it.**

METS Overview

behaviorSec

Sections about behaviorSec a bunch of links to the Fedora context at the time. Andreas is inclined to remove it - of historical value to know where it came from, but probably not useful any more.

Recent behaviorSec example from umich of indicating when to use 2up viewer for page images (e.g. when recto/verso was scanned vs. recto only)

Is there a specific use case implied by the METS specification? Is it worth keeping? The example use case could be done without the behaviorSec.

Are there other use cases where reason for existence is becoming more clear?

The people who wanted it in the beginning didn't use it.

The tutorial in Boston mentioned it but didn't elaborate.

Probably makes sense to remove from the overview/introduction, at least except for a brief mention.

Translations

Where did translations come from? Probably like with the introduction with PREMIS - somebody just sent a translation. Since we are making it up to date, we could send a message to the METS list and see if anybody wants to re-translate and we can publish.

Worth updating the XML in the examples in the translations?

We can share just the changes that were made so people don't have to re-translate the whole thing.

We can go ahead and merge the pull requests.

METS Schema Documentation

Karin provides the Oxygen export for other schemas she's working with. We still don't get the comments from the METS schema given the history. They should be in a documentation element if we want them to show up in the export. Probably worth having the changelog separately in the METS schema repository, or in an XML element instead of just a comment.

Could have an xsd:annotation for each version history.

Karin is going on a road trip to Prague for XML Prague and can ask how people are handling the version history of a schema or see if there's some common way of doing that.

Schema documentation: Concerns about accessibility of embedded images. Seems broadly comparable to what's there, but would like to get more feedback from others.

XLink issues

XLink:type example - depends on which validator you are using. Karin will see if it's reproducible or has some documentation about the failures.

Other XLink issues: will wait until we have resolution on #19.

Board membership changes

General agreement Inge should join. Karin will send welcome info.

Tom also sent info on the old Google Drive with applications. Should we open up a new call? There are some people who haven't attended meetings recently who are still on the board. We will hold off on a new call for now.

Migrating things from Tom's ownership.

Karin put a list of information in the Trello board about what we need:

Contact info for LC - Karin has it

Move the Trello Board? - currently owned by Tom, needs to be moved

Administrator of Git? - Everyone on the board (for the most part) is an owner; we went through and made some updates.

Are there documents somewhere else? - Any hidden Google Drive, Dropbox, etc?

Open issues? - Tom was holding some of them.

Open requests? - Haven't put up an issue template for people who want changes to schema, etc.

Updating the web site

Where are profile registrations sent? Both the ones submitting and the handling afterwards. - All those mails as far as Karin knows have been going to Tom. What does the web site say? Did Tom take over all of Brian's stuff? He was responsible for profiles before. EMail address: [email protected] (which doesn't work - should be [email protected]). Need to have a look through the web pages and correct email addresses. Glen should be able to answer where [email protected] ends up. Andreas created a Github ticket for this. Karin will email Glen about this.

List of board members (on LoC web site) also needs to be updated. Need to remove Leah and Tom; add Inge; remove co-chair info; move ex-officio people to the end of the list; remove individual emails. Tobias will take the list and make it up to date.

LoC is online and they are working, but some people aren't able to participate in certain things because of the shutdown. They have a budget but there might be other implications for the shutdown.

Other things on http://www.loc.gov/standards/mets/mets-board.html that needs to be updated? Some broken links?

  • remove reference to "or individual board members" for contacting people
  • Still true that METS board meeting are open to the public? Connection info is available, but we don't publish it beforehand when we're going to have the meetings... The big open meeting is the yearly F2F meeting.
  • Should just remove entire paragraph (More information ... individual Board members)

Will ask Glen to redirect emails about METS profile mails to METS board listserv. (Karin will do this?)

Lots of stuff elsewhere that is out of date .. front page with news, tools page, etc. There is general agreement that we need to review the web site in general. Perhaps more things (for example the list of tools) could be linked to the wiki for easier editing. We should make a GitHub issue for reviewing the web site, and everybody could take one page.