Topic / Who | Tickets | Notes | Decision |
|---|
Matthew Neely / All | 2023-2024 work plan sign off. | Dev Pri 2023-2024 workplan | |
Keli Schmid | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
|---|
| key | ANW-1682 |
|---|
|
| | |
Matthew Neely | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
|---|
| key | ANW-1730 |
|---|
|
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
|---|
| key | ANW-1757 |
|---|
|
| 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. Reviewed at August meeting. Draft Community input sent for discussion and decision needed on most appropiate appropriate channel to communicate this via.
| |
Cory Nimer | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
|---|
| key | ANW-1761 |
|---|
|
| 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. | |
Bonnie Gordon | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
|---|
| key | ANW-1736 |
|---|
|
| | |
Brianna McLaughlin | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
|---|
| key | ANW-1782 |
|---|
|
| | |
Dillon Thomas | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
|---|
| key | ANW-1774 |
|---|
|
| | |
Alexander Duryee (Unlicensed) | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
|---|
| key | ANW-1740 |
|---|
|
| | |
Mattie Clear | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
|---|
| key | ANW-1741 |
|---|
|
| | |
Matt Strauss | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
|---|
| key | ANW-1745 |
|---|
|
| 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 | | Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
|---|
| key | ANW-1760 |
|---|
|
| 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. | |