2022-01-27 and 2022-02-03 Metadata meeting notes

5 mins

Intro

Two meetings back to back, one agenda (this one); James' resignation from TAC; new meeting time?

AS Online Forum: March 21-22, 2022

Presenting was one of our workplan goals for this term. Please review our preexisting page for

But now the rubber hits the road! We should:

1. Confirm that we are presenting

2. Confirm what we are presenting

3. Brainstorm how to net feedback

4. Assign responsibilities

Records in Context

Please see your email (subject line Re: TAC/UAC RiC call for comments) for background on this agenda item.

• We cannot comment on a draft

• Put we want this topic put in this year’s retrospective because this group absolutely must render an opinion on this at some point

Tiers of Support

Please review and comment here:

Goal is to publish this by the end of term.

Background: This was an effort that partly pre-dated my work on TAC-MD and is an entirely new topic for some. The point of this document is to state what standards AS supports and more significantly, to what degree they are supported. The definitions and explanations are a distillation of past conversations, while the actual list of standards themselves is a holdover from last term or the term before, and is something we will revisit. For example, is it time that EAC-CPF be upgraded to Tier 1 support? Does the talk around EAD4 mean we leave EAD3 Tier 2? Etc.

MARC importer documentation and progress

We are not finished with MARC yet!

This topic is especially significant for the AS Online Forum as being able to present a list of things being removed, a list of things being added, and the new mapping will all be significant preparations.

• Elizabeth has included filtered views which are awesome and give a top-down look at what does map to DACS and what does not. Any line currently highlighted in yellow was not on the last published version of this spreadsheet.

• Since the core mapping is complete, the next step is to go into the core code and see what is supported that isn’t documented, and what is documented that isn’t supported. Also, once that is complete, reach out to Christine to ask her how she wants this (short of just creating a huge batch of tickets). Kevin suggested the DACS mapping be included in those tickets, to tie the room together.

MARC 510 versus 581

@Kevin Schlottmann Review of an ongoing discussion re: https://archivesspace.atlassian.net/browse/ANW-1350

Above was 2022-01-27; below was 2022-02-03

Updates from last time

(one whole week later)

• @Elizabeth Roke Is looking for feedback: Everything that isn’t highlighted is in the code correctly.  The highlights are things that are missing in the code.  Could someone double-check my mappings to AS?  I’m a little unsure as to the data model, so some of the note types might not be using the correct terminology.  There’s only a couple of these, so it would be great if someone had time to do it this week and I can then work on getting the code amended.  Here’s the spreadsheet link:

  • Also her question: is it our intention to pull the non-core elements out of the current mappings?  I can’t remember if we were looking for community feedback on this before we did it.

  • My recollection is that we’re keeping the non-core elements in the code, changing their color, stating that we’re doing this at the online forum, and then (this part I’m speculating on, we haven’t discussed it) maybe we can meet with Christine on the plan for actually removing them and keeping a version of the mapping for posterity.

  • The review that Elizabeth needed was completed during the meeting

• @Kevin Schlottmann Any concerns since last meeting?

• @Valerie Addonizio

  • going once…. going twice.,..

  • See @Elizabeth Roke Action item below

  • This revealed that TAC-MD was approached about EAC changes beforehand and we declined, so we should state that we’ve learned, gotten our footing, and would like to be included in the future

  • Meeting times? Render your verdict on whether you can schedule meetings two hours later (9am PST/12pm EST), three hours later (10am/1pm), or four hours later (11am/2pm EST) on the same days?

    • Minutes: Noon-1pm Eastern looks like it will work @Valerie Addonizio checked with Jared and changed the meeting time

  • Doodle for March 3rd

    • Thank you!

  • Minutes: Bumped to next meeting: There are new matches in your subscription to changes in archivesspace/archivesspace to files that match backend/app/converters/lib/marcxml_bib_base_map.rb!

    Here's what changed:

    • backend/app/converters/lib/marcxml_bib_base_map.rb (modified)

    • To see the changes, click here.

New/Ongoing ticket review

Check for new tickets.

In the last meeting we reviewed and we had the following comments. Another review of this ticket is a low priority (at this time) given the items above.

• Minutes: Bumped to next meeting

Kevin’s drafted ticket

Kevin sent us a draft of a ticket requesting that the AS importer code confirm the elements that were handled by an ingest process, allowing users an assessment of what was not handled. Here is his draft, below:

• Minutes: We reviewed why we reversed this ticket; I had to leave the meeting before a final conclusion on whether to remove the detailed reporting of what fields were mapped

Missing retrospectives

Elizabeth let me know that we are missing retrospectives from the Wiki. I raised this question and Christine said that she, as the admin, does have access to the deleted pages, but asked that we try and confirm what is missing given that Metadata hasn’t been around for long and that retrospectives may have been appended to other pages.

We have only been around for two terms prior to this one:

1. for 2020-2021

2. There was a draft of one here was this the final for 2019-2020?

• Minutes: We do still think we are missing the 2019-2020 retrospective by Dallas Pillen, @Valerie Addonizio alerted Christine

EAD Mapping reorganization

Purely optional: Opening the floor to @Regine Heberlein to show us her continuing work and invite comments.

5 min

Next steps/homework