Item/Who | Tickets | Recommendations | Decisions |
|---|
Roll call and announcements | | Welcome, Mark Cooper (Unlicensed) ! Any volunteers for selecting tickets for next month? Anything else?
| |
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
| and 2. Both ask for ability to add more agents and subjects in accessions imports, either via the CSV importer or implementing XML import for accessions. Current import template is unwieldy. Issue should be pursued, but needs more info.
3. No movement on ticket since 2016; looks like it has been resolved re: collection management fields. | Would need an XML schema, already exists to some extent because there is a MARCXML Accessions importer. Lori Dedeyan (Unlicensed) will leave comment and tag Ed to ask for more info about their institutions process. Seems more feasible to expand, similar to the excel import. Move to Awaiting More Info. Seems to be resolved. Close.
|
Alicia Detelich | https://archivesspace.atlassian.net/browse/ANW-213 https://archivesspace.atlassian.net/browse/ANW-218 https://archivesspace.atlassian.net/browse/ANW-491
| | Leave comment that not very feasible because it would require re-indexing when changing. Close. Could potentially be resolved through a local plug-in? Is the point to retain this info for an actionable purpose in ASpace proper or is it export the data to be actionable (in which case the exporter could be customized)? Add Metadata tag. Change priority to minor. Move to Awaiting More Info. Seems like a lot of work without a lot of value add. Close for now, create a new ticket if want to re-open.
|
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
| Commented for Mark to clarify “search help.” Otherwise, recommend closing the ticket because the original context/intent is lost. Seems to be asking for a different workflow from the existing LCNAF import plug-in, though it doesn’t specify the vocabulary/authority file. No comments or ticket creator to ask. Options: community developer (and edit the ticket to clarify a new workflow is desired related to existing plug-in) or close. New DACS element 8.1 "Rights Statement for Archival Description" isn’t on live DACS site yet. <rightsdeclaration> has been added to EAD3 (child under <control>). Anything needed from MS sub-team? Rec: pass.
| Close, unless Mark has additional info. Close Pass w/ Metadata standards commenting on where in the finding aid data section. Corresponds to DACS 8.2 and would want a higher priority once SAA Council approves. What type of data should go in there. Does it need to be unique? Does any validation need to happen? What would the export look like in EAD3? Rights declaration tag under control tag. We could link to the draft DACS guidelines on GitHub.
|
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 | ANW-392: Add comment to recommend a WYSIWYG mixed-content editor be developed as a plug-in, which needs to produce valid markup. Move to Community Developer and all sub-tasks (except ANW-395). ANW-395: Close.
|
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 vastly improve the functionality of subject headings. It probably needs more detail before a developer can work on it though. 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
| Comment that this needs to be a part of a comprehensive subjects overhaul. Ready for implementation. Leave comment to classify subject types by the first term in a subject string. Add what it would look like and what word to call the list of agents-as-subjects in comment. Link to Agent ticket. Pass. Close. Close. Close.
|
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-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? Isn’t this a duplicate of the already Ready for Implementation ticket:? Can we just close it? 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. (Notes from our December meeting: Lydia Tang (Unlicensed) comment to focus only on PUI (not SUI) and that it needs more specification. Lora Woodford comment on what this work might look like (and that it can’t be done with infinite scroll). Lydia Tang (Unlicensed) to draft a ticket to get rid of infinite scroll. Move to Awaiting More Information.)
| didn’t discuss yet Comment that bulk top container creation would happen within the context of a specific Resource. Pass. Add a comment to add a limitation that this would require barcodes. Come back to this one!
|