...
Topic / Who | Tickets | Notes | Decision | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Matthew Neely / All | 2023-2024 work plan sign off. | ||||||||||||||||||
| This user is asking for a link at the top of each page allowing keyboard-only users to jump to the main content, bypassing the need to tab through multiple steps to get there. This feature is recommended by W3C. I recommend passing this ticket | ||||||||||||||||||
|
| ||||||||||||||||||
| 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. In the PUI, the default labels are “Subjects” and “Collection organization.” Currently for EAD exports these <head> elements need to be added to 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. | ||||||||||||||||||
| Given the specifics of this issue, was not able to reproduce this. This issue appears to require a very specific scenario to happen and has a workaround when it does happen. | ||||||||||||||||||
| |||||||||||||||||||
Dillon Thomas |
| Was only able to reproduce the issue once, and not exactly as described. The agent relationship dates were auto-populated incorrectly, but were easily edited and those edits were retained. This hopefully means this will be a low-occurrence issue with an easy work around if it is considered a lower priority. | |||||||||||||||||
| |||||||||||||||||||
| Confirmed and was able to replicate that this is the issue. The information that is currently being imported into this column is only included if folks input the information - often this column includes the LCNAF/LCSH identifier if that is included in the input of an agent. I believe this issue and the root of this ticket relates to the use of the “authority_id” that is needed for the spreadsheet importer. This authority id is unique to each ArchivesSpace instance and related to when an agent is created. The description for this column in the spreadsheet is “(The numeric suffix on the URL of the Agent record, e.g., 9921 for https://arstaffqa.hul.harvard.edu/agents/agent_person/9921.”
I’m not sure if this is an easy fix, but it would also be helpful for the subjects as there is a similar issue. An easy fix to this issue would be to select the “URI” as a column type that will have that identifier number present. Recommendation: Pass | ||||||||||||||||||
| 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. |