Date and Time
Thursday 11/14/19, 3pm Eastern
Zoom URL
https://lyrasis.zoom.us/j/897871318
Participants
James Griffin (Unlicensed) (Note taker)
Goals
Discussion topics
Time | Item | Presenter | Notes |
|---|---|---|---|
5 min | Ice Breaker Question: Favorite (or least favorite) Thanksgiving food? | ||
10 min | Standing item: review metadata tickets | ||
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:
| |
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
Questions Regarding Process
New usability sub-team and advisory council will have a similar role, Dev. Pri. will find usability issues which require some weighing in on
Peeking around the meeting minutes for the Usability Sub-Team to evaluate what they are doing
Dev. Pri. is tagging metadata issues which may or may not require our input
We should leave a comment for cases where the issue looks like it requires input
ANW320
On 10/08, Dan left a note, sub-team found that there was insufficient information
Many times there will be tickets which do not outline the entire solution
Program team does not want any tickets which reach them which do not outline an explicit path to be taken for a solution
Dev. Pri. does not feel as if this is their role either; they do feel as if they have some freedom in order to provide some guidance for a solution
This ticket is missing a recommendation for the best option forward, and metadata standards should inform this
Dan confirmed that the case was that the tag “metadata” was applied in response to this
Dev. Pri. might also want to be in the position where a separate label “metadata-standards” is applied, as there might be tickets where “metadata” is applied but where the input from this sub-team is not required
Dev. Pri. will try to be more explicit regarding what is needed in terms of when input is needed in order to proceed with making a ticket actionable
December TAC Meeting