/
2026-06-02 meeting notes

2026-06-02 meeting notes

June 2, 2026

12:00-1:30 PM EST

Zoom link

 Participants

  • @Alexander Duryee

  • @Christine Di Bella

  • @Brianna McLaughlin

  • @Bonnie Gordon

  • @David Krah

  • @Regine Heberlein (regrets)

  • @Elizabeth Peters (Deactivated)

  • @Dalton Alves (regrets)

  • @Dustin Stokes

  • @Thimios Dimopulos

  • @Jen Cwiok

  • @Former user (Deleted)

  • @Evalyn Stow

 Goals

  • Prioritize new and awaiting more information tickets.

Links

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

Kanban boards:

Expectations

Before meeting

  • Review assigned ticket and prepare to discuss your recommendation

  • When needed, complete tasks requested at previous Dev/Pri meeting (e.g. suggest comments on Work Plan)

During meeting

  • Present your assigned tickets and recommendation

  • Listen to presentations and recommendations from other Dev/Pri members and provide feedback

After meeting

  • Comment decision on assigned tickets

    • Suggested language for comments: “Dev Pri discussed this ticket at our [insert date] meeting and have decided [insert decision]

  • Rewrite ticket if Dev/Pri determined during meeting that it would be helpful to do so

  • Solicit community feedback if Dev/Pri determined during meeting that it would be helpful to do so

 Discussion topics

Who

Topic

Notes

Decision

Who

Topic

Notes

Decision

@Brianna McLaughlin

  1. Welcomes and hellos

  2. Thank you!

  3. Retrospective

    1. 2025-2026 Retrospective working document

    2. 2025-2026 Work Plan

    3. 2024-2025 Retrospective

The retrospective will remain open for additions for at least a couple weeks. Bri will e-mail the exact closing date.

 

@Regine Heberlein

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

 

@Alexander Duryee

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

This is an extreme edge cases that requires the index being desynchronized to the database, but it does cause a fatal error if triggered. Recommend passing, although maybe it makes more sense to use a different error than a 404.

  1. Pass

@Bonnie Gordon

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

“Viewers” should be able to export records in the SUI, especially since they can do so via the API. Recommend passing.

  1. Pass

@Brianna McLaughlin

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

  1. I think the only issue is that the reporter isn’t manually encoding the ampersand. When I encoded the example in the ticket as the XML & there was no error. I recommend closing and directing the reporter to the relevant documentation: https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/pages/890208354

  1. Close

@Dustin Stokes

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

  2. https://archivesspace.atlassian.net/browse/ANW-2635

  1. Recommend Pass. The parameters should be defined.

  2. Recommend Pass

  1. Pass

  2. Pass

@David Krah

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

  2. https://archivesspace.atlassian.net/browse/ANW-2483

  1. Very confusing ticket but I think I figured out what they are talking about and reproduced a failed merge in the Subject Source controlled value list (latest version sandbox). Agree better error messaging would be useful.

  2. Tested, verified that I cannot get a <emph>tag to render properly when nested within a title tag. Nesting is possible using only the <emph> tags, but breaks when enclosing a title. Tested in 3.3.1 and newest version in sandbox

 

@Elizabeth Peters (Deactivated)

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

  1. Confirmed behavior. Not an issue in the SUI-generated PDF.

  1. Pass

@Evalyn Stow

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

  1. After further review, the phrasing is even more unclear on the PUI than the SUI. Asked the reporter if they had a suggestion for an alternative term.

  1. Awaiting more information

@Former user (Deleted)

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

Recommend pass. The current test instance already allows users to include or exclude URIs when generating PDFs, so this would focus on adding the same type of option for Component IDs/CUIs. 

  1. Pass

Everyone

Add new comments to tickets