2025-11-04 meeting notes

2025-11-04 meeting notes

Nov 4, 2025

Noon-1:30 PM EST

Zoom link

 Participants

  • @Alexander Duryee

  • @Christine Di Bella

  • @Mattie Clear (regrets)

  • @Brianna McLaughlin

  • @Donald Smith (Unlicensed)

  • @Bonnie Gordon (regrets)

  • @David Krah (regrets)

  • @Regine Heberlein(regrets)

  • @Elizabeth Peters

  • @Dalton Alves

  • @Dustin Stokes (regrets)

  • @Thimios Dimopulos

  • @Jen Cwiok

  • @Beth.Mawhinney (regrets)

  • @Evalyn Stow

  • @Donna Harnish (regrets)

 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 /all

  1. Welcomes and hellos

  2. How to address dead tickets?

 

 

 

@Dustin Stokes

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

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

  1.  

 

 

@Mattie Clear

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

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

  1. ANW-2450 - Confirmed issue. It seems like certain Date types trigger additional text, while others do not. It would make sense that all date types trigger additional text (Particularly if multiple dates are present). ie Inclusive and Single Date do not have additional text, but bulk includes “Majority of material found within.” Recommend passing

  2. ANW-2492: Confirmed many of the issues though honestly was overwhelmed by this query (so many acronyms!). Below are my responses to their three bullet points:

    1. Re: Reflow - I’m not entirely sure how to confirm their test of reflow that is their first and most adamant bullet point.

    2. Re: Langauge - In the test instance of 4.1.1 there is a label for language.

    3. Re: page numbers and screen readers - I was unsure of the best way to test this

    4. Re: Issue with Filter and Screen Reader - I was again unsure of the best way to test this.

This ticket is relatively new and given the importance of accessibility to LOC, I feel like we should try to address their recommendations given they were found with the most recent version?

 

 

@Alexander Duryee

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

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

  1. I’m concerned that this will break multilingual imports. I do agree with the reporter that there should be a way for users to add importable extent types, but I believe the proposed solution will cause other issues.

  2. Recommend passing.

  1. Send to metadata for further consideration.

  2. Pass.

 

@Regine Heberlein

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

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

 

 

@David Krah

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

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

 

 

 

@Dalton Alves

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

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

  1. I agree that searching for location is an unpleasant experience – especially in how results are ordered. Exact searching is possible though and I had a hard time recreating some of the behavior described. Would need to define desired behavior better to make this more actionable.

  2. The functionality of exporting a spreadsheet with AOs ordered via hierarchy/arrangement is possible w/ the Bulk AO Spreadsheet. Would be possible to extend to Top Container Template. I’m somewhat unfamiliar with the purpose of the TC template spreadsheet though. Has it been superseded by the Bulk AO spreadsheet?

  1. Get more info from requestor & clarify exact search ability (awaiting more info). Dalton will update top container documentation to include info about exact searching for record.

  2. Recommend the bulk AO spreadsheet. See if that satisfies whatever the use-case is here. Mark as awaiting more info.

 

@Evalyn Stow

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

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

  3. https://archivesspace.atlassian.net/browse/ANW-2413

  1. Confirmed issue on sandbox (4.1). I believe the proposed fix makes sense and should be passed.

  2. Confirmed issue on sandbox (4.1). I agree with these changes, I think this is important information to keep with finding aids when they are exported to pdfs, either through the staff interface or PUI.

  1. Pass

  2. Pass

  3. Pass as simple alphabetical sorting to remove complexity.

 

@Brianna McLaughlin

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

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

  3. https://archivesspace.atlassian.net/browse/ANW-1245

  1. Looks like this bug has been resolved in one of several ways, whether updating the number of results in the config or something else baked into a more recent release. Regardless, this can be closed.

  2. This ticket is no longer relevant as written. There is no longer a publish checkbox for the Rights Statement module. I don’t think there is a need to have any information in the Rights module published in the PUI, either. Any public information could be put in a Conditions Governing Use/Access note. Recommend closing.

  3. I’d like some feedback about this one. Would adding extent information in search results clutter the display? My institution requested adding extent information to our search results on our Arclight/ASpace integration. I’m leaning towards pass, but I’d like to hear more from the group.

  1. Close (already addressed in new releases)

  2. Close (addressed in new release)

  3. Will send out community feedback request.

 

@Elizabeth Peters

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

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

  1. Confirmed on Android Chrome browser, both in sandbox and on my current (somewhat customized) 4.1 instance. Not just incorrect, but completely garbled.

  2. Three (really four) related requests, already discussed in 2018 and 2022. Need to be mindful of a wide variety of uses of CUIs across repositories.

    1. Covered in ANW-816

    2. Recommend passing. Does create issues for some as-is, and wouldn't impose too much of a burden on those for whom it doesn't cause issues. Would require clear documentation.

    3. I would be curious why the order is the way it is, since it doesn't seem like it has a structural reason to be that way, and there hasn't been anyone arguing for it to be that way. Tentatively recommend passing.

    4. There seems to be an implied request here that the CUI be separated from the Top Containers, which was intended to help institutions which repeat box numbering with each series. We would need to make sure this change would not negatively impact those scenarios, but it is irksome to institutions who don't repeat box numbers. Could this be configurable?

  1. Pass

  2. Will break into individual tickets and close the original. New tickets: ANW-816, ANW-2532, ANW-2533, ANW-2534.

 

Everyone

Add new comments to tickets