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

Date and Time

Thursday 11/14/19, 3pm Eastern

Zoom URL

https://lyrasis.zoom.us/j/897871318

Participants

Goals

Discussion topics

Time

Item

Presenter

Notes

5 min

Ice Breaker Question: Favorite (or least favorite) Thanksgiving food?

Kevin Schlottmann

10 min

Standing item: review metadata tickets

Kevin Schlottmann

Link to board

10 min

Discussion topic for December TAC meeting

We need to lead a discussion for the December TAC meeting

5 min

Deliverables from previous meeting

GitHub Deliverables:

Sandbox API Enquiry:

  • This is enabled: curl -H 'Accepts: application/json' -X POST "http://sandbox.archivesspace.org/api/users/admin/login?password=admin"

20 min

Reviewing the Work Plan

DACS tooltips review - volunteer to lead?

Focus on test processes for import and export

5 min

Anything else?

Action items

  •  

Notes

Christine has indicated to me that they shall not be available to attend the meeting scheduled today, as they are attending the ArchivesSpace Southeast Regional Forum.

Introductions

Review the Metadata Tickets

Most of these are namespacing issues, we don’t need to weight in on these

Unless the developers need us to provide specific information

AMW943: Export accession record as MARC record

This seems like use case we should support

Accessioning then creating a catalog record, seems like a reasonable proposal

Any thoughts?

Specific point on the provenance data is a separate discussion

EAD has two potential fields…and that wouldn’t directly map to a single field

MARC might also suffer from this problem

Accession to MARC might be blocked by this, given how the accession records currently work within the system

Columbia Libraries accessions everything and then export the MARC using the resource record rather than the accession record

We looked at this, and let it go through developer prioritization

All concur, no comments on this issue

  • No labels