Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

[note: still in draft]

Goals

  • Ongoing ticket review and communication with devs

  • Ongoing review of import/export mappings and the evolving landscape of pertinent standards

  • Support user communities by responding to tickets and/or soliciting feedback

  • Special projects

Specific Tasks or Projects

Use this section to identify the specific tasks or projects your sub-team intends to work on this year. Consider organizing them into ongoing and discrete tasks, if appropriate.

Ongoing/Recurring Tasks

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

In-Progress Projects Carried Over from Last Term

  • Ensure that the MARC importer behaves as expected, according to subteam guidance and user feedback.
  • Ensure that the MARC exporter behaves as expected, according to subteam guidance and user feedback.
  • Look into the EAD 2002 importer and exporter; establish whether ArchivesSpace’s reading of EAD 2002 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?

New Projects for This Term

  •  

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.

Maintenance Activities (Optional)

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?

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.

  • No labels