11:30am-1pm ET
\uD83D\uDC65 Participants
Dillon Thomas
\uD83E\uDD45 Goals
Finalise 2023-2024 workplan.
Prioritize new and awaiting more information tickets.
Links
Kanban boards:
New bug reports: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=15
New feature requests: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=16
Link to ArchivesSpace sandbox: http://test.archivesspace.org/
\uD83D\uDDE3 Discussion topics
Topic / Who | Tickets | Notes | Decision |
---|---|---|---|
Matthew Neely / All | 2023-2024 work plan sign off. | ||
| |||
Ticket requests additional fields for recording a label (<head> element) value for EAD exports, though consulting with the reporter it was indicated that these might also be used in PUI display. Currently these <head> elements need to be added to the EAD file after export. In the PUI the headings can be modified using YML files, but the request is to allow custom labels for each Resource record. Decisions would need to be made about where to record these values in the staff interface. Recommend gathering additional community feedback about interest in this level of display customization. | |||
Dillon Thomas | |||
This ticket requests that specific information be provided in the error log when an EAD import fails. Currently, the error messages can be vague and might not point to exactly where within the EAD file the issue is. Implementing this feature request would make resolving problematic EAD a lot easier. Recommend passing this. | |||
From personal experience I know importing related subjects involves a bit of clean up it does seem reasonable to me the default should be the one that involves the least work. As long as people know they can turn on the option. Merits discussion. |