Page Comparison

Welcome/Introductions/Announcements

• Welcome to new members!

• Seeking new co-chair for later this fall.

  • Maggie is TAC Chair and Lydia will be rotating off of UAC at the end of this term.

  • A new co-chair could shadow us and learn the ropes.

• Draft 2019-2020 work plan

  • Dev Pri can decide on themes in how we tackle tickets.

  • Discussion about whether to prioritize newer tickets so that the community feels like they are being heard.

  • Previous initiative from the summer of 2018-2019, we focused on evaluating Ready for Implementation tickets on their candidacy for new queue: Ready for Community Developer.

• Coming soon! Dev Pri survey: https://www.surveymonkey.com/r/WPZYHLX

  • Let us know if you have feedback asap!

• Please update your interests/strengths on the wiki!

  • Helps us assign tickets

Jira tickets

Lydia Tang (Unlicensed)

1. 
   https://archivesspace.atlassian.net/browse/ANW-535

2. Is this still an open issue?

https://archivesspace.atlassian.net/browse/ANW-341 Related to---

3.https://archivesspace.atlassian.net/browse/ANW-825

1. Recommending to close this because it no longer appears to be an issue.

2. recommending to close as a duplicate to ANY-273

3. pass

1.

2.

3.

Edgar Garcia (Unlicensed)

1. https://archivesspace.atlassian.net/browse/ANW-696

2. https://archivesspace.atlassian.net/browse/ANW-733

3. https://archivesspace.atlassian.net/browse/ANW-913

1.

2.

3.

1.

2.

3.

Laney/Lora

1.https://archivesspace.atlassian.net/browse/ANW-303

2.https://archivesspace.atlassian.net/browse/ANW-737

1. Recommending to move this forward as ready for implementations

2.

1.

2. Closed it as “will not do” since there isn’t anything there to do

Lori Dedeyan

1. https://archivesspace.atlassian.net/browse/ANW-850

2. https://archivesspace.atlassian.net/browse/ANW-853

3. https://archivesspace.atlassian.net/browse/ANW-230

1.

2.

3.

1. Ready for community developer, mark asterisk.

2. Awaiting more info

3.

Alicia Detelich

1. https://archivesspace.atlassian.net/browse/ANW-819

2. https://archivesspace.atlassian.net/browse/ANW-841

3. https://archivesspace.atlassian.net/browse/ANW-917

1.

2.

3.

1. Able to replicate, not for community developer, pass it. Needs to have Digital object component ids.

2. Pass and indicate link to other tickets

3. Alicia will comment, info pass to community dev.

Randy Kuehn

1. https://archivesspace.atlassian.net/browse/ANW-918

2. https://archivesspace.atlassian.net/browse/ANW-488

3. https://archivesspace.atlassian.net/browse/ANW-554

1. “ns2” appears in deprecated extref tag / EAD3 export removes “ns2” and validates

2. Unsure if it’s recommended to include a “provenance” note in a resource record (DACS)

3. 2016 - waiting for clarification

1. Question for metadata standards - what are we going to do with EAD3 vs EAD2002?

Which of the two suggestions should we do? Awaiting more info

2. Close ticket. Randy will comment with info re: plug in and aligning with standards.

3. Awaiting more info

Daniel Michelson

1. https://archivesspace.atlassian.net/browse/ANW-531

2. https://archivesspace.atlassian.net/browse/ANW-333

3. https://archivesspace.atlassian.net/browse/ANW-320

1. While this remains a problem, it does not currently cause any issues with the use of ArchivesSpace. Recommend reducing priority to minor and changing to Ready for Implementation.

2. Change to Ready for Implementation

3. There are some possible solutions to this problem, but they are not specifically laid out in either the ticket or the comments. I’m not clear on whether it is the role of this subteam to do that work.

1. Awaiting more info, change priority to minor

2. Pass with priority of minor

3. Awaiting more info (keep), keep priority, pass to metadata team.

Maggie Hughes

1. https://archivesspace.atlassian.net/browse/ANW-381

2. https://archivesspace.atlassian.net/browse/ANW-424

3. https://archivesspace.atlassian.net/browse/ANW-161

1. v2.6.0 appears to export valid EAD 3 parallel extents. Uses attribute @physdescstructuredtype but the value doesn’t seem configurable (automatically set to “spaceoccupied”?). Does not use <physdescset> to bind multiple <physdescstructed> together (EAD3 does not require this). Not sure about parsing and migrating existing data, and the priority level.

Right now ~10 tickets open tagged EAD3. Would we want to ask MS sub-team to comment?

2. Confirmed in v2.6.0. Text box for descriptions allows and holds paragraph breaks in edit mode but view mode only shows raw, not formatted, text.

Rec: pass.

3. Not able to replicate in v2.6.0. A user was was repo manager in one repository was not able to edit the repository preferences in a second repo. Had no access to Global preferences. Has anyone else heard of this issue coming up recently?

Rec: close.

1. Awaiting more info and suggest that the final statement be parsed into a separate ticket.

2.

3.