Accomplishments
Presented at the 2022 Online Forum and solicited community feedback
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 [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]
Commented on tickets as appropriate [list of tickets]
Piloted working meetings to help members get work done
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
Priorities for next term
Continue work on the EAD importer in earnest
Spec for dropping MARC import support (if not completed by this term)
ANW-547 - Getting issue details... STATUS , folder for spec documents here: https://drive.google.com/drive/u/1/folders/1G4ACVJ9r3FUfStsnyZkDJWbyU-bErZzl
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, 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.
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.
Retrospective in Brief
Start doing | Stop doing 🛑 | Keep doing |
|---|---|---|
Recommendations for finishing up this term
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
We wanted to put forward the request that Pull Requests that change the importers should have more context, like the ticket number. I believe Kevin gave this example of exactly where this would be helpful: ​​
However, at the top of that screen I saw a link to the PR itself, #2624
By following that link I found this: ​​ , which does give the full context of this ticket: ​​
So my question is, is this just a matter of us knowing where to look? It seems that the AS Dev did do a good job on the context here, so I’m now less sure of what we’re critiquing/requesting, unless you can provide another example.
Leadership for next term
Lead: Regine Heberlein
Vice Lead: To be identified from new members next term
Outgoing Lead: Valerie Addonizio