Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

11:30am-1pm ET

Zoom link

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

  • Finalise 2023-2024 workplan.

  • Prioritize new and awaiting more information tickets.

Links

\uD83D\uDDE3 Discussion topics

Topic / Who

Tickets

Notes

Decision

Matthew Neely / All

2023-2024 work plan sign off.

Dev Pri 2023-2024 workplan

Keli Schmid

ANW-1682 - Getting issue details... STATUS

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

Matthew Neely

ANW-1730 - Getting issue details... STATUS

ANW-1757 - Getting issue details... STATUS

  1. This ticket is seeking an additional filter for PUI search results to highlight associated digital objects. I think this could be of use to researchers and Dev Pri have previously reviewed tickets requesting greater visibility of resource records with digital objects. Recommend passing but we may need further input on the ticket.

  2. Reviewed at August meeting. Draft Community input sent for discussion and decision needed on most appropriate channel to communicate this via.

Cory Nimer

ANW-1761 - Getting issue details... STATUS

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.

Bonnie Gordon

ANW-1736 - Getting issue details... STATUS

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.

Brianna McLaughlin

ANW-1782 - Getting issue details... STATUS

Dillon Thomas

ANW-1774 - Getting issue details... STATUS

Alexander Duryee (Unlicensed)

ANW-1740 - Getting issue details... STATUS

Mattie Clear

ANW-1741 - Getting issue details... STATUS

Matt Strauss

ANW-1745 - Getting issue details... STATUS

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.  

Tom Steele

ANW-1760 - Getting issue details... STATUS

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.

  • No labels