Who | Topic | Notes | | |
---|
Matt Strauss /all | Welcome to new members and introductions | | | |
Matt Strauss | Discuss Dev/Pri Work plan for 2024-2025 https://archivesspace.atlassian.net/wiki/pages/resumedraft.action?draftId=3927080974&draftShareId=4886868f-d061-4dd8-9da0-0de572f94a99 Dev Pri Retrospective 2023-2024 | Dev Pri’s primary work will continue to be reviewing and prioritizing tickets for development. What other activities should we consider? A few possibilities from last year’s work and retrospective: Solicit feedback from ArchivesSpace community on certain tickets to inform Dev Pri discussions. Formalize and document process for Dev Pri to edit Jira tickets. Community Q&A sessions or office hours to help with tickets.
| | |
All | Jira Legacy |
---|
server | System Jira |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1749 |
---|
|
| Discuss community input for this ticket that was sent to the email list in February. | | |
Matt Strauss | Jira Legacy |
---|
server | System Jira |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1785 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1816 |
---|
|
| Confirmed bug and recommend this pass. There are few different requests tied into this ticket about the PUI and SUI Advanced Search. Add the inventory field to the search: field might be solved by the Extended Advanced Search plugin developed by Yale. Ability to limit advanced search by record type: I think this achievable by using facets to narrow results. Make the SUI Advanced Search the same as PUI Advanced Search: I’d like to hear more about the benefits of doing this and perhaps submitting a new ticket following the new template would generate this information.
| | |
Brianna McLaughlin | Jira Legacy |
---|
server | System Jira |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1832 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1908 |
---|
|
| I agree this is confusing. I think a warning that the box is not checked or vice versa is a good idea. Recommend passing. Can confirm local restriction type is not importing. The reporter said that there was not an error indicating that the local restriction type did not import, but I am actually encountering what seems to be an unrelated error. I get the error “[Some system error has occurred [undefined method `title' for nil:NilClass].] when I am importing a local access restriction type with a date. The only difference between successful and unsuccessful imports is a date despite the error pointing to title. Very confusing! Recommend passing.
| | |
Bonnie Gordon | Jira Legacy |
---|
server | System Jira |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1804 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1850 |
---|
|
| Bug is undesirable. Pass. Use case is reasonable. Should work be bundled with ANW-1863?
| | |
Alexander Duryee | Jira Legacy |
---|
server | System Jira |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1787 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1845 |
---|
|
| Tested this on sandbox and found the same issue - the MARC included in OAI exports is incomplete. In addition to the leader and 008 fields, the 040 is also exporting as a blank node, despite having information in the non-OAI MARC. Recommend passing. Tested on sandbox and confirmed the error. This appears to be an oversight from ASpace 3.0 development. Recommend passing.
| | |
Keli Schmid | 1. Jira Legacy |
---|
server | System Jira |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1788 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1912 |
---|
|
| | | |
Mattie Clear | 1. Jira Legacy |
---|
server | System Jira |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1867 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1889 |
---|
|
| Confirmed that it is an issue. Updating to allow the cancel functionality would align with what other similar functionalities allow. Recommend Passing. Confirmed that it is an issue/bug that should be resolved to allow for ease of updating events with the proper agents. Recommend passing.
| | |