Item/Who | Tickets | Recommendations | Decisions |
---|
Roll call and announcements | | Welcome, Mark Cooper (Unlicensed) ! | |
Tickets
|
|
|
|
Lori Dedeyan (Unlicensed) | [subtasks of earlier ticket: https://archivesspace.atlassian.net/browse/ANW-408 ] https://archivesspace.atlassian.net/browse/ANW-409 https://archivesspace.atlassian.net/browse/ANW-410 https://archivesspace.atlassian.net/browse/ANW-411
| | |
Alicia Detelich | https://archivesspace.atlassian.net/browse/ANW-213 https://archivesspace.atlassian.net/browse/ANW-218 https://archivesspace.atlassian.net/browse/ANW-491
| | |
Edgar Garcia (Unlicensed) | https://archivesspace.atlassian.net/browse/ANW-509 https://archivesspace.atlassian.net/browse/ANW-622 https://archivesspace.atlassian.net/browse/ANW-84
| | |
Maggie Hughes | https://archivesspace.atlassian.net/browse/ANW-341 https://archivesspace.atlassian.net/browse/ANW-500 https://archivesspace.atlassian.net/browse/ANW-343
| | |
Randy Kuehn | [the subtasks of the earlier ticket: https://archivesspace.atlassian.net/browse/ANW-392 ] https://archivesspace.atlassian.net/browse/ANW-394 https://archivesspace.atlassian.net/browse/ANW-395 https://archivesspace.atlassian.net/browse/ANW-396 https://archivesspace.atlassian.net/browse/ANW-397 https://archivesspace.atlassian.net/browse/ANW-563
| 1. ANW-394: Provide a WYSIWYG editor for wrap-in-tag function for enabling mixed content Assuming the EAD/MARC/PDF exporter can strip invalid tags/errors and there isn't an objection to mixed content, a notes field WYSIWYG would be a helpful addition Recommend: Community Development
2. ANW-395: Wrap and tag should have xlink on various attributes on <extref> 3. ANW-396: As a staff user, I want wrap and tag options for notes that are schema compliant 4. ANW-397: As an archivist I want the wrap in tag editor to supply attribute options Option #1: Expand wrap in tag option to include formatting & secondary value options for render, actuate, etc. - Recommend: Push Option #2: Add wrap in tag options to a WSYWIG See ANW-394 notes above - Recommend: Community Development
5. ANW-563: format text and live hyperlinks for Notes | |
Daniel Michelson | https://archivesspace.atlassian.net/browse/ANW-361 https://archivesspace.atlassian.net/browse/ANW-339
A few really mysteriously empty tickets to possibly close??? 3. https://archivesspace.atlassian.net/browse/ANW-47 4. https://archivesspace.atlassian.net/browse/ANW-42 5. https://archivesspace.atlassian.net/browse/ANW-14 | The improvements suggested here would greatly vastly improve the functionality of subject headings. It probably needs more detail before a developer can work on it though.TBD This is a reasonable suggestion, but along with ANW-629 (linked in the ticket), this raises the broader question of how agents and subjects should be displayed in the PUI. For example, should agents used as subjects come under subjects or related names? Taking this ticket on its own, I’d recommend reducing priority to minor and changing to ready for implementation. The empty tickets are ideas for new reports judging from the linked epic. Did the reports subteam review these? Already closed Same as 3
| |
Lydia Tang (Unlicensed) | https://archivesspace.atlassian.net/browse/ANW-775 https://archivesspace.atlassian.net/browse/ANW-495 https://archivesspace.atlassian.net/browse/ANW-503 https://archivesspace.atlassian.net/browse/ANW-3125. https://archivesspace.atlassian.net/browse/ANW-350
6. https://archivesspace.atlassian.net/browse/ANW-341 7. https://archivesspace.atlassian.net/browse/ANW-477 | Usability looked at this and feel it should pass with the cataloger’s comments. Ok? Use cases such as accessioning a 100+ boxes collection and staff needing to add barcodes to top containers without any additional description. Scary, but might be useful? In my opinion, not a good idea. What do others think? I suggest to pass this revised version. What do others think? Usability wants this! Close ticket. Done. Close ticket. A new ticket is created for reordering in the staff interface (with changes persisting). The PUI use case doesn’t seem strong. This is a confusing ticket.
| |