Topic/Who | Tickets | | Decision |
---|
Daniel Michelson | https://archivesspace.atlassian.net/browse/ANW-1168 https://archivesspace.atlassian.net/browse/ANW-1244 https://archivesspace.atlassian.net/browse/ANW-690 | It’s specifically the “Repository Short Name” that has this issue, since the confirmation for deleting requires typing the short name and for whatever reason it isn’t recognizing an apostrophe as a match. Pass to development. Clearly not the intended result, pass to development. Close as duplicate of ANW-1206 (currently pending Usability review)
| |
Tom Steele | https://archivesspace.atlassian.net/browse/ANW-1242 https://archivesspace.atlassian.net/browse/ANW-1345 https://archivesspace.atlassian.net/browse/ANW-1258 | Was able to replicate the problem, but am using 2.8.1 as well. Aesthetic problem only, but would aid user readability. Low Priority. ID numbers like barcodes should be unique. This needs to be implemented. I can’t replicate the problem because I don’t create locations at my institution, so my account lacks permissions. My institution doesn’t assign barcodes to locations either so I can’t even verify there’s a barcode field. Is this one resolved? Ready for Implementation seems to imply it is. If it isn’t ,Recommend check by barcode when linking since it’s a unique identifier.
| |
Matthew Neely | https://archivesspace.atlassian.net/browse/ANW-1268 https://archivesspace.atlassian.net/browse/ANW-1276 https://archivesspace.atlassian.net/browse/ANW-703 | This ticket is requesting that ‘Container Type’ in the Top Container record is made a required field. If not is not completed then the EAD export has a blank attribute for type in the container field. Replicated in the sandbox: <container id="aspace_02b5bd760a514658d9b84535f5f9bfb7" label="Text" type="">1-7, 10</container>. Recommend either make it a required field or setting export to not included a blank attribute.
2. This ticket relates to unpublished agents not exporting in the EAD when ‘include unpublished’ option is selection. Recommend passing the proposed solution for persname/famname/corpname in the controlaccess section for archival objects should get an audience="internal" attribute when they are unpublished, the way they do for resources. 3. This ticket is seeking a progress bar or spinning wheel to indicate the progress of a search in the PUI. The ticket was created in 2018 but my experience based on my institutional instance (8627 collection resource records with file levels) is that the search is very fast and this would not be required. Might be necessary if local infrastucture or accessing via slower Internet speeds? | |
Angela White | https://archivesspace.atlassian.net/browse/ANW-1243 https://archivesspace.atlassian.net/browse/ANW-1299 https://archivesspace.atlassian.net/browse/ANW-1344 | | |
Althea Topek | | | |
Randy Kuehn | https://archivesspace.atlassian.net/browse/ANW-1285 https://archivesspace.atlassian.net/browse/ANW-1288 https://archivesspace.atlassian.net/browse/ANW-1290 | Recommend asking Usability for input Although I wasn’t able to replicate the problem in v3.0.2, I believe a Solr is scheduled to be upgraded in an upcoming 2021 release. Solr 5.5 will correct the problem. Will the upgraded version of Solr be 5.5 or greater? Recommend including display_string in trim whitespace background job Confirmed white space remains in display_string unless object is resaved after running background job (v3.0.2)
| |
saron tran | https://archivesspace.atlassian.net/browse/ANW-1220 https://archivesspace.atlassian.net/browse/ANW-1377 https://archivesspace.atlassian.net/browse/ANW-701 | pass
| |