Workplan
2021-2022 Metadata Sub-team Work Plan
Accomplishments
Completed re-working and actual data modeling for the EAD2002 importer mapping
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
- ANW-1568Getting issue details... STATUS (ERR)
- ANW-1567Getting issue details... STATUS (ERR)
- ANW-1565Getting issue details... STATUS (ERR)
- ANW-1260Getting issue details... STATUS (KS)
Identified behaviors that can be removed and simplified
Addressed default behavior for MARC 300 fields - ANW-1260Getting issue details... STATUS
Identified desired behavior for logging - ANW-1558Getting issue details... STATUS
Commented on tickets as appropriate [list of tickets]
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 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)
- ANW-547Getting 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-1558Getting 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 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
Rotating group of ex officio from Metadata who sit in on Dev Pri meetings
Elizabeth volunteers
Kevin volunteers
Our metadata rep for this term
Leadership for next term
Lead: Regine Heberlein
Vice Lead: To be identified from new members next term
Outgoing Lead: Valerie Addonizio