Topic/Who | Tickets | Notes | Decision |
---|
Maggie Hughes | https://archivesspace.atlassian.net/browse/ANW-765 https://archivesspace.atlassian.net/browse/ANW-768 https://archivesspace.atlassian.net/browse/ANW-746
| Would need a final specification. Suggest review by Usability sub-team. What work is going on PUI right now (anything related to Yale’s PUI)? Is there a comprehensive review of PUI going on or planned? Yale’s does not repeat the hierarchy on the right side (https://archives.yale.edu/repositories/5/resources/351/collection_organization) while the out-of-the-box ASpace PUI does (http://sandbox.archivesspace.org/public/repositories/2/resources/1/collection_organization).
| Waiting more info - pui will be changing - need to evaluate put
|
Matthew Neely | https://archivesspace.atlassian.net/browse/ANW-1110 https://archivesspace.atlassian.net/browse/ANW-773 https://archivesspace.atlassian.net/browse/ANW-338
| This ticket was first reviewed at the Dec 1 2020 Dev/Pri meeting. The requestor has now provided further information and a mock-up of the RDE templates which they would like to be made repository specifc and only users with access to the specified repository would have permissions to view and use them. I can see this being useful to institutions using multiple repositories where metadata standards may vary. This ticket is requesting that the PDF generator button be deployed at all levels of a finding aid. I think this is a good idea and would be useful for users. We have implemented this at my institution and an example is here: https://archives.bodleian.ox.ac.uk/repositories/2/archival_objects/88988 . Yale have also implemented this: https://archives.yale.edu/repositories/15/archival_objects/2820102 . This ticket is requesting that a print button be added to the PUI which would trigger a browser’s built in print functionality, to enable users to print a cleaned version of a page. I think the PDF generator already provides a printer friendly output for the full Resource so I’m not convinced this is needed. It has been suggested in the comments that the alternative is to deploy a CSS print style sheet for the PUI.
|
|
Angela White | https://archivesspace.atlassian.net/browse/ANW-813 https://archivesspace.atlassian.net/browse/ANW-379 https://archivesspace.atlassian.net/browse/ANW-998
|
|
|
Althea Topek | https://archivesspace.atlassian.net/browse/ANW-1122 https://archivesspace.atlassian.net/browse/ANW-1208 https://archivesspace.atlassian.net/browse/ANW-939
| I think this happens because the DO unique identifier doesn’t export in the xml so duplicate DOs can be created when importing.
| Hold - discuss with Matthew
|
Randy Kuehn | https://archivesspace.atlassian.net/browse/ANW-1162 https://archivesspace.atlassian.net/browse/ANW-877 https://archivesspace.atlassian.net/browse/ANW-923
|
|
|
Daniel Michelson | https://archivesspace.atlassian.net/browse/ANW-343 https://archivesspace.atlassian.net/browse/ANW-1175 https://archivesspace.atlassian.net/browse/ANW-1169
| This was approved for implementation at a minor priority one year ago, with the agreement that the priority should be increased once SAA Council approved the new required element. This has now happened, so I recommend increasing this to critical.
| Dan will investigate (critical issue)
|
saron tran | https://archivesspace.atlassian.net/browse/ANW-885 https://archivesspace.atlassian.net/browse/ANW-1107 https://archivesspace.atlassian.net/browse/ANW-1170
|
|
|