Versions Compared

Old Version 11

changes.mady.by.user Valerie Addonizio

Saved on

compared with

New Version 12

changes.mady.by.user Valerie Addonizio

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

Workplan: 2021-2022 Metadata Sub-team Work Plan

Accomplishments

  • 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

      Jira Legacy
      serverSystem JIRA
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyANW-1568
      (ERR)

      Jira Legacy
      serverSystem JIRA
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyANW-1567
      (ERR)

      Jira Legacy
      serverSystem JIRA
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyANW-1565
      (ERR)

      Jira Legacy
      serverSystem JIRA
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyANW-1260
      (KS)

      Jira Legacy
      serverSystem JIRA
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyANW-1566
      (ERR)

      Jira Legacy
      serverSystem JIRA
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyANW-1557
      (KS)

    • Jira Legacy
      serverSystem JIRA
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyANW-1411
      (VA)

    • Jira Legacy
      serverSystem JIRA
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyANW-1410
      (VA)

    • Jira Legacy
      serverSystem JIRA
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyANW-1409
      (VA)

    • Jira Legacy
      serverSystem JIRA
      serverId36c489e2-4fb0-353a-985b-64038401be2f
      keyANW-1408
      (VA)

    • Identified behaviors that can be removed and simplified

  • Addressed default behavior for MARC 300 fields

    Jira Legacy
    serverSystem JIRA
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-1260

  • Identified desired behavior for logging

    Jira Legacy
    serverSystem JIRA
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-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

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)

  •  

    Jira Legacy
    serverSystem JIRA
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-547
    , 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,

    Jira Legacy
    serverSystem JIRA
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-1558
    we should do an email announcement to the listserv and Google Group

...

  • 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 (green star)

Stop doing 🛑

Keep doing (blue star)

  • Increase community engagement

    • Reports out to the community via the listserv (i.e. we’ve done this, what do you think)

    • Engage ticket writers and commenters (invite to meetings, ask to work on specs)

  • Have Program Manger and/or Community Engagement Coordinator attend quarterly for questions

  • Working meetings was acknowledged as a good idea but it didn’t work for everyone, so this isn’t so much a “stop doing” as a “continue if needed/wanted”

  • Presenting at the Online Forum

  • 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.

    • Put in document formerly know as Tiers of Support

  • Reminder of Action Items in email form

  • Explicit and helpful links in agenda and emails

  • GitHub File Watcher

  • Dedicated reading time in the meetings

Recommendations for finishing up this term

  1. 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

...

  • 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

...