Time | Item | Notes |
|---|
2 mins | Intro | |
3 mins | Quick orientation | Files are linked in the Quick Links section above. |
3 mins | What is it we do, broadly? | Ongoing ticket review and communication with devs Ongoing review of import/export mappings and the evolving landscape of pertinent standards Support user communities by responding to tickets and/or soliciting feedback Special projects
|
5 mins | What we did last term | |
10 mins | What we’ll do this term | Continue to work with DevPri on tickets of interest to the group Check in with ongoing MARC work | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
|---|
| key | ANW-1688 |
|---|
|
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
|---|
| key | ANW-1602 |
|---|
|
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
|---|
| key | ANW-1748 |
|---|
|
Pivot to EAD 2002 exporter – this will depend a lot on how the MARC work is prioritized Data Modeling Task Force? Link to more information Look into RiC? This relates to the data modeling work. This work has never made it to the top of this group’s priority list. It’s unclear if there is demand for compliance with Records in Context among the ArchivesSpace community. GitHub protocols: we briefly touched on this, but it didn’t come together. It would be good to establish a review and approval protocol for pushes to the repo such that the person that makes the change is not also the person that pushes the change. It’s just good practice to have multiple sets of eyes on changes!
|
5 mins | Logistics | |
2 mins | Next steps / Homework | Workplans are due by Wednesday, September 27. https://archivesspace.atlassian.net/wiki/spaces/AC/pages/3137994933/Guidelines+for+ArchivesSpace+Council+Sub-Teams#Sub-team-Workplans Workplan Template |