Participants
...
Time | Item | Notes | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
2 mins | Intro | Some text lifted directly from emails, below: | ||||||||
10 minutes | Ticket updates |
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 (Draft is in Agenda, linked here): · 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 Direct follow ups:
Minutes: Each addressed in Action Items and this work is complete for now. | ||||||||
15 minutes | MARC importer documentation and progress | Elizabeth Roke Next and final steps? The tickets for 300 and 852 actually tie this work up well. 264, 583, and 584. Totally feasible to finish the spreadsheet this term. Minutes from Discussion:
Direct questions to address in the next meeting:
Minutes: Elizabeth Roke proposed a compromise to the compromise: Pull all the non-core fields (2xx, 3xx, 754, 856) except the 5xx’s; for the 5xx’s, everything that is a core field gets mapped, but everything that is a 5xx just gets a mapping to a local note, like a 590. We know this a relatively big change, maybe put this in the roadmap, so that it doesn’t happen quietly . Elizabeth volunteers to write that spec, including the justification. You get a list of what was imported. | ||||||||
10 minutes | Tiers of Support | Valerie Addonizio Next and final steps? Minutes (polished): In conversation about the origins and fate of the Tiers of Support we came to the conclusion that the Tiers may serve a purpose in recording our internal decisions making (i.e. what, based on the community as it stands, gets prioritized over something else), but decided that its role as a public-facing position document was limited. Instead, we discussed the bigger difficulty in all our work related to standards, and that is the lack of a an ASpace data model for us to compare other standards' models to. We positioned a hypothetical task – whether undertaken by this group, informed by this group, or working wholly separate from this group – of deriving and documenting the ArchivesSpace data model. The rough minutes from the meeting were:
| ||||||||
10 minutes | ANW-547 |
I’d like you to focus exclusively on resources/components and not on Agents. The original writer of the ticket was talking about resources/components and then it was a commenter that opened the discussion to Agents. I’d like to separate out the Agents question and focus back on just the resource and component level. Minutes: Sounds good for the interface, and Valerie Addonizio can do a mock-up of what ti would look like. This sounds like three tickets: the interface, EAD exports, EAD imports. Less confident about how to do the export. | ||||||||
10 minutes | Updated EAD Mapping | I have asked Jared Campbell to work with some sample EAD mappings between now and the end of term. Key here is to to prepare for the work of next term. Some thoughts: What to focus on next might not be so much what to actually do in the spreadsheet as designing the next phase of work for a team with various comfort levels. Minutes: We expect Jared’s notes in the next meeting. | ||||||||
New/Ongoing ticket review | Revisiting:
| |||||||||
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:
Expand | | |||||||||
| Done:
| |||||||||
Review Work Plan Items | ||||||||||
5 min | Next steps/homework |
Action Items
- Kevin Schlottmann Extent:
Jira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1260
- Kevin Schlottmann Importer reporting ticket
- Kevin Schlottmann 852 $j:
Jira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1557 - Valerie Addonizio Mock up what
would look like in the interfaceJira Legacy server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-547 - Elizabeth Roke Spec for final work on MARC importer, see minutes above
Long term Action Items (by or at end of term)
- Elizabeth Roke
Contact Mark about the EAD4 questions andinvite him to a future meeting - Elizabeth Roke and Valerie Addonizio Alert Christine to the updated version of the MARC importer mapping + inquire about how they might want the new tickets delivered (and good suggestion from Kevin to include the DACS mapping element in the ticket creation). Also inquire about keeping an older version of the mapping for posterity.
- Elizabeth Roke and Valerie Addonizio Contact Christine about publishing the Draft of Tiers of Support
- and our stance on being included upstream in decisions that effect external standards
- Valerie Addonizio Put RiC review in the notes in our retrospective. 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.
- Valerie Addonizio Put our statement about being included upstream in the notes in our retrospective
...