2024-08-06 Meeting notes

Aug 6, 2024

12-1:30pm ET

Zoom link

 

 Participants

  • @Matt Strauss

  • @Keli Schmid

  • @Alexander Duryee

  • @Christine Di Bella

  • @Mattie Clear - regrets

  • @Brianna McLaughlin

  • @Donald Smith

  • @Bonnie Gordon

  • @David Krah

  • @Regine Heberlein

  • @Elizabeth Peters

  • @Dalton Alves

  • @Dustin Stokes

  • @Thimios Dimopulos

  • @Jen Cwiok

 Goals

  • Prioritize new and awaiting more information tickets.

Links

Kanban boards:

Link to ArchivesSpace sandbox: http://test.archivesspace.org/

 Discussion topics

Who

Topic

Notes

Decision

 

Who

Topic

Notes

Decision

 

@Matt Strauss /all

Welcome to new members and introductions

Will probably follow suit from the last few years and skip January 2025 meeting.

 

 

@Matt Strauss

Discuss Dev/Pri Work plan for 2024-2025

 

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.

    • 1 per month so we don’t inundate the AS community.

  • Formalize and document process for Dev Pri to edit Jira tickets.

    • Thimios created plan and requested Dev Pri feedback throughout the last year. We can talk more about permanent solutions next month.

  • Community Q&A sessions or office hours to help with tickets.

    • Seems like we’re on the right path with asynchronous videos on YouTube.

    • Office hours could be a good idea, though we would have to be careful that it is not an undue burden on a small portion of this group.

    • Coordinating with the next Virtual Forum could get traction going. Office hours take some time to gain traction. However, that would be near the end of the year for us. The momentum could get lost a bit.

    • Maybe a more 1:1 schedulable meeting would work. Dev Pri members would rotate hosting office hours.

 

 

All

https://archivesspace.atlassian.net/browse/ANW-1749

Discuss community input for this ticket that was sent to the email list in February.

Responses were more so about the desire for more flexibility in what information is carried over rather than the specific request of this ticket.

 

Recommend passing ticket as is and recommend that people submit a separate ticket if they want additional/different capabilities.

 

@Matt Strauss

https://archivesspace.atlassian.net/browse/ANW-1785

https://archivesspace.atlassian.net/browse/ANW-1816

  1. Confirmed bug and recommend this pass.

  2. There are few different requests tied into this ticket about the PUI and SUI Advanced Search.

    1. Add the inventory field to the search: field might be solved by the Extended Advanced Search plugin developed by Yale. 

    2. Ability to limit advanced search by record type: I think this achievable by using facets to narrow results.

    3. 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.  

  1. Pass

  2. Recommend the reporter explore the Extended Advanced Search plugin.

 

@Brianna McLaughlin

https://archivesspace.atlassian.net/browse/ANW-1832

https://archivesspace.atlassian.net/browse/ANW-1908

  1. I agree this is confusing. I think a warning that the box is not checked or vice versa is a good idea. Recommend passing.

  2. 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.

  1. recommend suggesting local documentation for the reporter and their institution.

  2. Pass

 

@Bonnie Gordon

https://archivesspace.atlassian.net/browse/ANW-1804

https://archivesspace.atlassian.net/browse/ANW-1850

  1. Bug is undesirable. Pass.

  2. Use case is reasonable. Should work be bundled with ANW-1863?

  1. Recommend passing if a preference change does not resolve issues.

  2. Pass and link issue to ANW-1863

 

@Alexander Duryee

https://archivesspace.atlassian.net/browse/ANW-1787

https://archivesspace.atlassian.net/browse/ANW-1845

  1. 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.

  2. Tested on sandbox and confirmed the error. This appears to be an oversight from ASpace 3.0 development. Recommend passing.

 

 

@Keli Schmid

1.https://archivesspace.atlassian.net/browse/ANW-1788

https://archivesspace.atlassian.net/browse/ANW-1912

  1. Anne Marie Lyons has commented that the user’s request can be accomplished through a custom report: “Search on recently created accessions that are Gifts and display the Content Description box. Also include and display linked Agents.” Recommend informing end user and closing ticket

  2. I believe this user may be confusing the purpose of inclusive v. bulk dates: “Inclusive Dates” indicates the earliest and latest dates included in the collection. Sometimes, there will be a “Bulk Dates” listed as well, which means a large portion of the materials covers this more specific span of time. If present, this will be found under the inclusive dates. I do not see a bug or error here.

 

 

@Mattie Clear

1.https://archivesspace.atlassian.net/browse/ANW-1867

https://archivesspace.atlassian.net/browse/ANW-1889

 

  1. Confirmed that it is an issue. Updating to allow the cancel functionality would align with what other similar functionalities allow. Recommend Passing.

  2. Confirmed that it is an issue/bug that should be resolved to allow for ease of updating events with the proper agents. Recommend passing.