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 19 Next »

Microsoft Teams meeting

Click here to join the meeting

Participants

Minutes

Current Work Plan

2021-2022 Metadata Sub-team Work Plan

Previous Agendas

2021-08-19 Metadata meeting notes

2021-09-16 Metadata meeting notes

2021-10-20 Metadata meeting notes

Discussion Topics

Time

Item

Notes

10 min

Tiers of Support

I want to follow up on this item from last term: Get the tiers of support on GitHub and get that link to Christine for the https://archivesspace.org/ site

 Follow-up on Tiers of Support

Is this the final version, at the top of this page: 2019-2020 Metadata Standards sub-team Work Plan?

Is there any documentation, like why something is in tier 1 versus tier 2? If we publish this, I suggest we include a bit more about how these tiers are decided.

I recall a decision that this go on GitHub. Where exactly?

25 min

Update on progress

Action items from last agenda: https://archivesspace.atlassian.net/wiki/spaces/AC/pages/2944106518/2021-10-20+Metadata+meeting+notes#Action-Items

Thank you to Elizabeth for reporting back on ANW-768: https://archivesspace.atlassian.net/browse/ANW-768

 Follow-up:

<ref> elements are not currently repeatable in a single index note in AS.  It is repeatable in both EAD2002 and EAD3, but it needs to be nested within a <ptrgrp> wrapper when repeated.  I spoke to Mark Custer at Yale about this and he thinks we should support it in AS because the workaround requires repeating index entries (e.g. an indexentry with a ptrgrp and 5 refs becomes 5 index entries, all with the same name heading).

Addressing this ticket means: within the index, allow the reference and the reference text for each item within an index note to repeat.  Amending the EAD3 and EAD2002 import/export to create multiple references for each index item when <ptrgrp> is present within <indexentry>. 

Not sure on priority, but absolutely think this is something that needs to be supported since it’s supported in both EAD3 and EAD2002 and we know of people having to develop workarounds.

10 min

New/Ongoing ticket review

Check for new tickets. If there are no new tickets, we will move on.

https://archivesspace.atlassian.net/browse/ANW-943?filter=13658

  • What would a spec look like in this case? A crosswalk between MARC and the data model for Accessions?

https://archivesspace.atlassian.net/browse/ANW-1350

  • Thoughts? I volunteer to test and submit a comment.

10 min

Brainstorm

An ambitious Work plan item is Recommend and provide feedback on a workflow that alerts the Metadata Sub-Team to relevant tickets as they are submitted and reviewed

I thought of that recently when this ticket was marked as complete: https://archivesspace.atlassian.net/browse/ANW-1174

I’d like to brainstorm (if we have time) on how to be alerted to and follow-up on code changes like the one above.

I set up a test of https://app.github-file-watcher.com but not sure I have it working.

5 min

Next steps/homework

No new agenda items in the next agenda! I want us to have space and time to address past and current business

Action Items

Minutes

  • No labels