...
...
Workplan
...
2021-2022 Metadata Sub-team Work Plan
...
Presented at the 2022 Online Forum and solicited community feedback
Include stats that I generated after the Forum
Completed an update to the MARC importer with significant improvements:
Mapped MARC elements to DACS elements and prioritized DACS mappings
Documented missing behaviors and created tickets for same
(ERR)Jira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1568
(ERR)Jira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1567
(ERR)Jira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1565
(KS)Jira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1260
(ERR)Jira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1566
(KS)Jira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1557
(VA)Jira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1411
(VA)Jira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1410
(VA)Jira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1409
(VA)Jira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1408 Identified behaviors that can be removed and simplified
Addressed default behavior for MARC 300 fields
Jira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1260 Identified desired behavior for logging
Jira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1558 Commented on tickets as appropriate [list of tickets]
Piloted working meetings to help members get work done - it was acknwoledged 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 more transparent process for how we do what we do
Task Force idea - Want to suggest an ad hoc taskforce to update the ASpace data model
Priorities for next term
Continue work on the EAD importer in earnest
Revisiting Tiers of Support as a principles document
Spec for dropping MARC import support (if not completed by this term)
, folder for spec documents here: https://drive.google.com/drive/u/1/folders/1G4ACVJ9r3FUfStsnyZkDJWbyU-bErZzlJira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-547 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,
we should do an email announcement to the listserv and Google GroupJira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1558
...
Being included upstream - Valerie has drafted an email to be sent to the entire council at either the end of this term and/or the beginning of next term, plus I will explicitly mention it at the final TAC meeting this term.
Some of this feeling was generated after all the changes that came with 3.0, but we’ve moved forward on that concern forgetting that we were invited to participate and declined. So this is about aligning both our own expectations about our work and being included further upstream in changes.
This is a good example of where things that the metadata group should weigh in on are buried in specification documents and tickets. Note that the specification includes a request to amend the EAD and EAD3 exports
Communicate it to Christine, the developers, but also TAC and Dev Pri.
More about a heads up than an approval process; fundamental to needing to track changes to documentation. Even if it becomes the primary job of this group to actively document and track those changes. We need to be tagged any time anything touches an importer/exporter
...