...
Time | Item | Presenter | Notes |
|---|---|---|---|
5 min | Ice Breaker Question: Favorite vacation spot | ||
|
|
| |
2 min | Update on process for Metadata Standards generated tickets | Dev/Pri does not need to be involved in approving bug fix tickets created by the Metadata Standards subteam. | |
15 min | Standing item: review metadata tickets | Specific tickets =flagged for us by Christine Di Bella https://archivesspace.atlassian.net/browse/ANW-805 I (Kevin) think the last comment in the ticket is correct (Nancy Kennedy’s); let’s review and comment if we agree. | |
5 min | Language of Description EAD Export issue update | https://archivesspace.atlassian.net/browse/ANW-969 Cory Nimer confirmed this was likely an oversight. See below for a proposed response. | |
10 min | Priority fields | Set of priority fields for both MARC and EAD. See below for proposed references (are the better / more recent sources for EAD?) and MARC fields. | |
5 min | Anything else? |
Notes
(Ice Breaker Responses)
Update from Laney
Laney is going to be leaving the ArchivesSpace community for another opportunity, and hence, they were not available to attend this meeting.
When their (former) role is filled, the Sub-Team shall look to try and invite the new person to discuss this topic
Dev/Pri Update
Update from Daniel
Did Dev/Pri need to be included in discussions for tickets designated as bugfixes from the Metadata Standards Sub-Team?
This was determined not to be necessary
Christine, Kevin, or James will request permission to update the individual tickets in order to label these as bug fixes
Awaiting prioritization to ready for implementation is the normal workflow
We have the authority to circumvent this and just register these as bugfixes and see these advanced
James will be responsible for advancing tickets as
...
JIRA bugfixes
Metadata Tickets
Proposed answer for ANW-969:
...