2021-02-02 Meeting notes

Angela White

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

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

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

Matthew Neely

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

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

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

1.  This ticket is seeking to add deaccession sub records to Digital Objects. This would mirror Resource records which already have this. It seems a logical request but I do wonder if this is already handled by accessions and resource record worflows where deaccessions can already be recorded?

2. This ticket is seeking classifications to be added to Digital Objects. The ticket was created to identify a means of mapping legacy digital object metadata into ArchivesSpace with their preference being to use classifications rather than convert to subjects. I think we could request further information on why subjects could not be used.

3. This ticket is seeking a solution to display in linked resources within Agents all resources associated with that agent together with resources linked to any parent or child agents related to the agent being viewed. Comments in the ticket show that this could be cumbersome for some repositories. Options to search for keywords in SUI also might make this unnecessary to take forward for implementation?

Althea Topek

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

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

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

1. List: all “notes” (except “preferred citation”), linked agents, linked subjects, and published external documents

2. Published, related accessions should display in the PUI as “related unprocessed material” (similar to published related resources as “related collections”)

3. Needs more information? No comments since 2015; is this still an issue?

1.  Althea Topek will compile a list of notes - will revisit at the next meeting.

2.  

3.  

Randy Kuehn

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

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

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

Daniel Michelson

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

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

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

4. https://archivesspace.atlassian.net/browse/ANW-1119

saron tran

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

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

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

1. I think this is okay. I am curious to know how ArchivesSpace has dealt with translations in the past. I wonder if something like this could be done with a team providing support to people who are willing to translate to other languages (like a hack-a-thon / transcribe-a-thon).

2. Bug report. I really like how they reported this one (with the description and the screenshots to go along with it). I think this should be fixed.

3. I like this one. In the PUI archival objects show the hierarchy up to the different series and then to the collection (resource) and then to the repository-- and I think digital objects should function the same.

Maggie Hughes

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

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

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