2022-11-01 Meeting notes

 Date

Nov 1, 2022

11:30am-1pm ET

Zoom link

 Participants

  • @Randy Kuehn (regrets)

  • @Matthew Neely

  • @Daniel Michelson

  • @Tom Steele

  • @Althea Topek

  • @Christine Di Bella

  • @Brian Hoffman

  • @Matt Strauss

  • @Keli Schmid

  • @Donald Smith

  • Kevin Schlottmann (guest)

  • Kevin Clair (guest)

 Goals

 Discussion topics

Topic / Who

Tickets

Notes

Decision

Topic / Who

Tickets

Notes

Decision

@Keli Schmid

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

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

  1. Aside from accidental deletion when selecting multiple events, I don’t see a reason this request shouldn’t move forward. Perhaps though, the problem lies more with why erroneous events are being created rather than how they can easily be deleted.

  2. It sounds like Benn Joseph has identified the issue (see comment on August 22, 2022 at 12:45 PM). Certain UTF-8 diacritics are not accepted by the import mechanism, even though those UTF-8 diacritics were generated by a database query. However, I am not sure he and Trevor Thornton (March 11, 2022) are experiencing the same problem. It does seem to warrant further testing.

  3. I’m not sure the Repository Profile report (as suggested) would fulfill the original request of Chris Fitzpatrick, but both reports seem useful.

  1. Pass

  2. Set as awaiting more information as have not been able to replicate issue.

  3. Close

@Randy Kuehn

  1. Continue discussion

  2. User expects a preference hierarchy and would like clarification & inconsistencies to be address - Agree, but needs more information

  3. Needs more information

  1.  

  2.  

@Matt Strauss

1.Workaround: increase the amount of search results that will display by modifying the config file.  That said, the ability to increase the search results to different predefined amounts (30, 50, 100, etc.) directly from the staff interface would be useful.

2. Issue seems to be resolved with the updated Bulk Import AO XLSX available through ArchivesSpace 3.3.0

3. Replicated - pass

  1. Pass

  2. Close. Already resolved in v.3.3.0

  3. Pass

@Althea Topek

  1. Can the hover text move up or down? (not obstruct anything)

  2. Could not replicate

  3. Replicated - pass

  4. From Usability - questions:

    1. Can the filing title note take the place of the finding aid title (stated in comment from June 2022)? - looks like a bug (should not replace)

    2. Is it possible to add “publish” options for each element? - not a good idea for usability; issues with publishing sensitive information can be made into another ticket

    3. What fields can be modified in the XSLT stylesheet (staff HTML export)? - not an issue

    4. Send to metadata standards? - EAD display

  5. From Usability for December DevPri meeting

  1. Pass

  2. Pass

  3. Pass

  4. Pass. All fields should be displayed in PUI.

  5. Hold for Decemeber meeting

@Tom Steele

  1. Very detailed request. We can discuss pros and cons of suggestions in meeting. I will fully admit this is not my area of expertise.

2. Tested this one then had to delete what I tested. This is not good. Pass. 

3.seems to be new to 3.3. Pass

  1. Pass

  2. Pass

  3. Pass

@Daniel Michelson

  1. This ticket wants to split the existing date expression field into a date begin expression and a date end expression following the model of agent records, with existing data parsed as was done in the agent record implementation. I’m not clear how that parsing was previously done. It’s also not clear to me how useful having more ways to break out dates in a way that isn’t machine-actionable really is, but that is supported by EAD3, so I don’t object to passing this. I do recommend lowering the priority to minor and explicitly stating that this ticket should not be completed until more important date related tickets (specifically ANW-1475 and ANW-1273) are complete so that we continue to encourage people to use machine-actionable dates over date expressions.

  2. This ticket is requesting the ability to automatically alphabetize components in resource records. The primary use case mentioned in the ticket is to be able to easy add archival objects in an already alphabetized list via the bulk import spreadsheet. I’ve also previously heard from a couple different people that they would like such a feature for when using the bulk import spreadsheet (which inherently supports alphabetization) is, for whatever reason, not appropriate for adding archival objects. I believe the New School plugin could serve as a workaround, but I’ve not used it. I think this is worth passing.

  3. Using the spreadsheet provided by the reporter caused the import to hang without providing any message. I was able to cancel the job and, while the server became unresponsive for a couple minutes (memory issue?), I had no problems using the spreadsheet importer afterwards. So I suggest reducing the priority to trivial and passing, since it shouldn’t be hanging.

  1. Pass. Set priority as minor. ANW-1475 and ANW-1473 should be completed first.

  2. Pass

  3. Pass

@Matthew Neely

  1. This ticket is requesting a spreadsheet import or RDE function to create container profiles. Agree this would be very helpful and save a great deal of time. Suggest this needs a specification and then community development? Ticket is also requesting this for locations but batch location creation functionality already exists in the SUI and CSV import available from ASpace 3.0 onwards.

  2. This ticket is requesting a CSV import function to bulk update top containers and locations across multiple resources. Agree this would be highly useful. Suggest requesting a specification.

  3. This ticket is requesting an update to the Top Container CSV import template so that locations can also be imported and associated with resource and accession records. Recommend this is useful functionality and pass this.

 

 Action items

 Decisions