...
...
Link to ArchivesSpace sandbox: http://test.archivesspace.org/
Discussion topics
Who/What | Tickets | Notes | Decision |
---|
Roll call/ Announcements | | | |
Daniel Michelson
| https://archivesspace.atlassian.net/browse/ANW-504 Note: the following subtasks were associated with this ticket that is already ready for implementation. Should they get passed, closed, or spec’d out? https://archivesspace.atlassian.net/browse/ANW-400 https://archivesspace.atlassian.net/browse/ANW-403 https://archivesspace.atlassian.net/browse/ANW-402 https://archivesspace.atlassian.net/browse/ANW-401 https://archivesspace.atlassian.net/browse/ANW-404
| 1. I had a very long explanation about how this ticket could modified to make it ready for implementing, but at the end I realized it still wasn’t acceptable (to me anyways). Here’s a summary of the issues:
The ticket wants to be able to identify any linked agent as primary. Since there was no explanation of why this feature was requested in the ticket, it’s not clear if there is a use case beyond importing and exporting MARC records without a 1XX field. That use case could be addressed by changing the behavior of the importer and exporter, without changing the underlying data model. The 2019 discussion in the comments focused on identifying creator agents as primary. This does not address the issue that was (presumably) the reason for the ticket. I’m not convinced that having agents flagged as primary is the appropriate way to address any of the issues identified in the ticket. Supporting MARC import and export is important, but I’m leery of changing the underlying data model due to the idiosyncrasies of MARC.
2-5. These relate to the agents module revision that is under development. Recommend leaving as is. | 1. Leave comment that Dev Pri recommends an optional checkbox on the link, and this needs a specification to detail the different combinations (no checks, 1 check, 2 or more checks) and what their outputs are before moving forward. Move to Awaiting More Info.
2-5. Leave as is. Email James. |
Lydia Tang (Unlicensed) | https://archivesspace.atlassian.net/browse/ANW-
|
6087755033125. 350868
| Usability looked at this and feel it should pass with the cataloger’s comments. Ok?
|
From last meeting: Add to add a limitation that this would require Come back to this one!I suggest to pass this revised version. What do others think?Can this pass? I think this should pass! 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.)Action items
Decisions