Our primary work will continue to be reviewing and prioritizing tickets for development. What else? A few possibilities from last year’s workplan and ideas for discussion from the retrospective:
Share agendas with TAC and UAC and extend an open invitation to council members to join if there are any tickets they are interested in commenting on.
Improve documentation of the process of consulting with other subteams on certain tickets.
Present at 2023 ArchivesSpace online forum about the work of the group.
Select a few “Awaiting More Information” tickets of particular value and seek additional community feedback or otherwise attempt to resolve them.
Create a running list of tickets that require additional community feedback and share list with broader community.
Ticket is requesting a change to EAD generation from resource records. Ticket suggesting this should be a background job as experiencing time out issues. Not been able to replicate this in the sandbox but have been able to successfuly export a resource with 5000+ archival objects from own institution’s instance. Could the time out issue just be fixed by a config change?
This ticket is requesting a resource spawn functionality to create a duplicate. Use case is for editing a duplicate whilst maintaining access to a published version. Can see advantages for this but unclear how much development work this might require as ticket is requesting ability for the duplicated resource to mainting links to associated digital objects, top containers and agents etc.