Versions Compared

Old Version 3

changes.mady.by.user Kevin Clair

Saved on

compared with

New Version 4

changes.mady.by.user Kevin Clair

Saved on

Key

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

...

  •  Continue working with Development Prioritization on tickets relating to metadata standards support – writing user stories, advising on prioritization of metadata tickets, etc.

Timeline: Ongoing.
Members:

In-Progress Projects Carried Over from Last Term

  •  Ensure that the MARC importer behaves as expected, according to subteam guidance and user feedback.
    •  Almost done (95%?)
  •  Ensure that the MARC exporter behaves as expected, according to subteam guidance and user feedback.
  •  Look into the EAD 2002 importer; establish whether ArchivesSpace’s reading of EAD 2002 is in line with the specification, and draft tickets for development for any issues we find.
  •  Look into the EAD 2002 exporter; establish whether ArchivesSpace’s reading of EAD 2002 EAD2002 is in line with the specification, and draft tickets for development for any issues we find.
  •  Establish good practices for how we share work products (importer/exporter tests, documentation, etc.)
    •  Continue to use GitHub?
    •  Continue to use Google Drive?
    •  Use Atlassian in some way?

Timeline:

New Projects for This Term

  •  Circling back to the user community
    •  Collaboration with UAC on metadata conversations
    •  Determine a process for bringing user questions or concerns about metadata back to this group (and to others in the Advisory Committees?)

Timeline: Talk about user engagement with metadata at the ArchivesSpace Online Forum in the spring (exact date TBD).

Out-of-Scope (Optional)

  • We considered the extent to which ArchivesSpace should support Records in Context (RiC). This was a carry-over from our 2022/23 work plan. We decided that because RiC is still a draft specification, there is no use case for ArchivesSpace to support it at this time, but will monitor developments.

...

Use this space to identify any actions or considerations necessary to support the maintenance of your sub-team’s tasks or projects once they have been completed. Is there documentation that needs to be created? Do future sub-team members need particular permissions to complete certain work?

Determine who “owns” our collaboration spaces (Google Drive and GitHub, primarily). Set up a plan for transferring ownership across terms, if needed.

Themes (Optional)

This section is optional, but a space to identify any underlying themes that run throughout multiple tasks or projects. This can also be a space to identify how you intend to approach your work this term. This can also be helpful when revisiting the workplan at the end of term with an eye towards the sub-team’s retrospective, or at the beginning of next term.

  • Greater engagement with the ArchivesSpace user community

    • Do the activities that Metadata Standards undertakes make sense for the larger community? Can they relate to our work, or is it mainly for the benefit of advanced/high-resourced ArchivesSpace users?

  • Documentation of how ArchivesSpace deals with metadata that it uses or does not use in import/export

  • “Regularizing” our work so that things that are heavy lifts now can become standard ongoing work for future iterations of the Metadata Standards team