Accomplishments
Presented at the 2022 Online Forum and solicited community feedback
Completed the update to the MARC importer with significant improvements
Mapping MARC elkements to DACS elements and prioritized
Documented missing behaviors and added [list of tickets forthcoming]
Identified behaviors that can be removed and simplified
Addressed default behavior for MARC 300 fields [ticket]
Identified desired behavior for logging [ticket]
Piloted working meetings to help members get work done
Priorities for next term
Continue work on the EAD importer
Develop a workflow for maintaining the importer/exporters sustainably. Suggestion to add metadata standards tags to tickets that require touching those files in the codebase. It is currently a major problem that Metadata Standards team members need to be able to partially read Ruby code to be a part of this group.
Revise the AS to MARC documentation and publish
Recommendations:
Being included upstream
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
It would help us if the name of the pull request had the ticket number; could you take us through this so that we know what's going on here?
Unresolved business from this term
Bring up the retiring of MARC behaviors at the next joint UAC/TAC meeting, which will be in the fall. Elizabeth Roke should handle that communication
If we get Kevin’s ticket, ANW-1558 - Getting issue details... STATUS we should do an email announcement to the listserv and Google Group
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.
Retrospective
Start doing | Stop doing 🛑 | Keep doing |
|---|---|---|
Leadership for next term
Lead: Regine Heberlein
Outgoing Lead: Valerie Addonizio