Page Comparison

Roll call and announcements

Tickets

Ticket theme for today’s meeting: mostly bugs and usability tickets

Lori Dedeyan (Unlicensed)

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

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

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

1.

2.

3.

Alicia Detelich

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

2. https://archivesspace.atlassian.net/browse/ANW-926 3. https://archivesspace.atlassian.net/browse/ANW-803

1.

2.

3.

Lydia Tang (Unlicensed)

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

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

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

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

5. https://archivesspace.atlassian.net/browse/ANW-769

1. Usability looked at this and felt it was useful for both staff and PUI, to maximize the ability of dynamically generated finding aids.

2. Usability felt this was a useful feature. I forget if we discussed this and said the programming architecture is too complex to fix?

3. This is a new “bug” that would be nice to fix soon. Endorsed by Usability

4. Also endorsed by Usability

5. Also endorsed by Usability

Randy Kuehn

1. https://archivesspace.atlassian.net/browse/ANW-936 2. https://archivesspace.atlassian.net/browse/ANW-903

1. Confirmed typeahead does not accommodate hyphenated entries (v2.7.0)
   Recommend: pass

2. Confirmed controlaccess title tags are skipped during EAD import (v2.7.0)
   Recommend: pass

Daniel Michelson

1. https://archivesspace.atlassian.net/browse/ANW-951 2. https://archivesspace.atlassian.net/browse/ANW-958 3. https://archivesspace.atlassian.net/browse/ANW-946

1. Issue exists in 2.7. Solution requires changing the logic used to generate agents from user records. The simplest method would be to name the agent after the username, since that already has to be unique. Recommend changing priority to minor, adding the solution, and changing to ready for implementation.

2. Could not reproduce, submitter confirmed that this is not a problem anymore. Close as done.

3. Not clear this behavior is incorrect, commented asking for clarification.

Maggie Hughes

1. https://archivesspace.atlassian.net/browse/ANW-555 2. https://archivesspace.atlassian.net/browse/ANW-894 3. https://archivesspace.atlassian.net/browse/ANW-851

Edgar Garcia (Unlicensed)

1. https://archivesspace.atlassian.net/browse/ANW-890 2. https://archivesspace.atlassian.net/browse/ANW-842 3. https://archivesspace.atlassian.net/browse/ANW-224

1. Jira Legacy
   server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-736

   fixed the reorder issue.

   1. Github issue to investigate removal of parent_name exists

   2. Depending on Dev response, wait or abandon?

2. Cannot reproduce this issue, I have asked the reporter for reproduction steps.

   1. Recommend we wait for more information.

3. From Christine: “For the 2.7.0 release we’ve now added a configuration option to the end of the Config file - AppConfig[:limit_csv_fields] . By default this is set to true, to limit the fields in those CSVs to selected columns on the screen. If you set it to false it will work the way it did previously”

   1. Does 2.7.0 technically resolve this issue by allowing to revert to “old way”? If the case, I move to close this ticket for now.

Laney McGlohon (Unlicensed)

Lora Woodford

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