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)
Was able to replicate the problem on test server. Aesthetic problem only, but would aid user readability. Low Priority. Pass.
ID numbers like barcodes should be unique. This needs to be implemented. Replicated on test server. Pass.
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.
Pass, minor
Recommend a plugin for this issue, since the field is working as designed , community input
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?
Pass for setting export to not include a blank attribute
Custom note labels don’t display in staff version of the PDF export, particularly Abstract. I have verified this and recommend pass, trivial prioritization.
Digital Objects attached at the Resource level do not export in either staff or PUI PDFs. Pass, trivial prioritization.
Changing the standard note order in Global Preferences doesn’t “stick.” I have verified this bug and recommend a pass, with a minor prioritization.
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)
pass - for my own reference: https://gitlab.ku.edu/library/archivesspace/-/issues/109 – occurred for us with lora’s batch language update plugin and a really old barcoder plugin – i think we ended up deleting it out of the database as i have since removed those plugins from the config and system. JSONModel not found for barcoder_job uri:classloader:/jsonmodel.rb:64:in `JSONModel' also, agree with valerie in that we noticed slowness because of it
pass - reproduced and agree that logging should be improved
pass – agree that digital_object_components would be easier to work with if there were ancestors to work off of