Page Comparison

2021-2022 Workplan

2021-2022 Metadata Sub-team Work Plan

...

• Piloted working meetings to help members get work done - it was acknowledged as a good idea but it didn’t work for everyone

• Improved reactive strategies for tracking changes

  • Tested and implemented https://app.github-file-watcher.com/ to be automatically notified of changes made to the import/exporter code

  • Tested and implemented a subscription to a Jira filter for the Metadata tag

• Tiers of Support - Attempt at a more transparent process for how we do what we do

...

• Proposed strategies for the EAD work as discussed in the last meeting of term:

  • Invite Brian Hoffman (ASpace Dev) to present on the EAD importer. Key to this would be preparing a few concrete questions or asking for a demonstration of how he himself would fill out the spreadsheet. Early efforts to de-mystify the code would benefit the whole group.

  • Remember and embrace the fact that it took three years to complete the MARC importer (and there’s still some work to be done!) so take some pressure off: this work may not happen fast and it doesn’t need to. On that same note, embrace this by preparing for how this work could be spread out: would it be more like chunking the work (starting at the top and dividing into sections) or more like iterative processing, where there are multiples passes across the whole, each of which accomplishes something.

• Revisit Draft of Tiers of Support as a principles document instead of a statement on scope

• Spec for dropping MARC import support:

  • Pull all the non-core fields (2xx, 3xx, 754, 856) except the 5xx’s; for the 5xx’s, everything that is a core field gets mapped, but everything that is a 5xx just gets a mapping to a local note, like a 590. We know this a relatively big change, maybe put this in the roadmap, so that it doesn’t happen quietly. Elizabeth volunteers to write that spec, including the justification. You’ll get a list of what was imported.

•  Spec for

  Jira Legacy
  server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-547

  , folder for spec documents here: https://drive.google.com/drive/u/1/folders/1G4ACVJ9r3FUfStsnyZkDJWbyU-bErZzl

  • Update since retrospective: Nevermind! Looks like Princeton sponsored this

• Bring up the retiring of MARC behaviors at the next joint UAC/TAC meeting, which will be in the fall. Elizabeth Roke nominated to handle that communication

• If we get Kevin’s ticket,

  Jira Legacy
  server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1558

  we should do an email announcement to the listserv and Google Group

• NEW Task Force idea - Suggest an ad hoc taskforce to update the ASpace data model

  • Continue working on the justification of that idea as recorded in this document https://docs.google.com/document/d/1-4E1BYAGT-GCAWLZaWwtsPgeGJqnt6y04e6r82EYxCY/edit?usp=sharing (TAC-MD subteam members should have access to that link without a problem)

  • Note that there is an old (pre-container and location modeling) entity relationship model archived in the Wayback Machine: https://web.archive.org/web/20150324043730/https://www.gliffy.com/publish/2269861/

  • Valerie has tested Whimsical, Regine suggests Mermaid

  • Next steps: Present this idea at an early TAC meeting and prepare for the follow through on determining leadership. Also formalizing the document linked above. Note that an ad hoc group can be made up of anyone, but leadership and structure should probably come from within TAC.

• NEW Pilot a Rotating group of ex officio’s from Metadata who sit in on Dev Pri meetings

  • This excellent idea came from the acknowledgement that there’s only so much we can ask of our fellows to alert us to changes, and sometimes they may simply not be aware that these changes will impact TAC-MD

  • The idea was raised that we begin a rotating roaster of Metadata reps who sit in on Dev Pri meetings to listen and know when a ticket should be tagged for us to review. This is a strategy to get us involved further upstream.

  • We settled on the idea that one person volunteers each term, and one additional person volunteers as a backup in case the volunteer cannot make a meeting. Kevin volunteers for next term, with Elizabeth as a backup

  • Next step is: reaching out to Dev Pri with this idea and getting the volunteer(s) invited to their meetings

• RiC review

  • Essentially we know we absolutely must render a verdict on this, but we decline to do so on a draft. We have doubts about the stated aspirations (transmission standard, descriptive standard, one ring to rule them all). We want to be included in the decision of how ASpace reacts, and not just the recipients of said decision.

...

Recommendations for being included further upstream was one of our last kind-of unsettled tasks for term, so it was discussed as part of the retrospective. This discussion lead to the idea of the ex officio’s attending Dev Pri meetings.

A reminder on some background context:

...

•  Mention tagging Metadata at the final meeting of this term
•  Mention tagging Metadata at the first meeting of next term
•  Focus on the EAD2002 importer
•  Ex Officio idea! Seek orange text in the sections above for more details; that idea came out of this last-minute discussion
•  Data model task force idea. Seek green text above. Mention this in an early TAC meeting to get the ball rolling.

...