Content Comparison

Brianna McLaughlin

Welcome

• Thimios created a Jira board for tickets on the audit functionality feature: https://archivesspace.atlassian.net/jira/software/projects/AF/boards/90

Keli Schmid

1. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1907

Elizabeth Peters

1. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1891

2. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-2116

1. Essentially asking for events to function more similarly to agents and linked resources/accessions. I can see how this could be useful, but the current workflow doesn’t appear to be significantly more arduous than an adjusted one. If passed, low priority. If not passed, I would recommend changing the label “Add event” to “Create event” to better indicate the intended function.

2. Since this is causing validation issues, it seems good to pass. The order is well-defined, so shouldn’t be overly difficult to add to the transformation. It sounds like forcing the order in ASpace instead (i.e. not allowing a form subdivision to be added after a chrono one) would cause issues with legacy data.

David Krah

1. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1892

2. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1978

1. Requested clarification and a use case. No response yet.

2. Documentation seems pretty intentional that Coll. Management records should only be at the collection level. Management information for specific objects can be recorded in the collection level note - a processing plan can be entered in text or a link to local document. One an also make use of the “Repository Processing Note” in each object. The assessments module could also be used at the object level to track specific processing needs and priorities. Recommend not passing.

Mattie Clear

1. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-2150

2. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-2151

Dustin Stokes

1. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-2114

2. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-2205

Regine Heberlein

1. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-2219

2. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-2090

Matt Strauss

1. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-2146

2. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-2132

Brianna McLaughlin

1. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-2109

2. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-2161

Dalton Alves

1. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1958

2. Jira Legacy
   server System Jira serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-2142