2021-11-2 Meeting notes

Date

Nov 2, 2021 3:30 GMT / 11:30 ET / 10:30 CT / 9:30 MT / 8:30 PT

https://lyrasis.zoom.us/j/89240269444?pwd=Mld5cTFSMU9aY3FuY3B2S3liQmRxUT09

Participants

  • @Randy Kuehn

  • @Daniel Michelson

  • @Matthew Neely

  • @Althea Topek

  • @saron tran

  • @Angela White

  • @Brian Hoffman

  • @Lora Woodford

  • @Christine Di Bella

  • @Tom Steele

Goals

  • Prioritize new and awaiting more info tickets

Links

Kanban boards:

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

Discussion topics

Topic/Who

Tickets

Notes

Decision

Topic/Who

Tickets

Notes

Decision

@Daniel Michelson

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

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

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

  1. The requested report is simple and makes sense (although I’m not clear which fields should be included), but given the plan to introduce custom reports, I think it’s best to close it rather than devote developer time to this.

  2. This is a request for functionality to make it easier to enter large amounts of repetitive information in RDE. I understand the impulse, but I personally consider the use case given an example of poor descriptive practices that we should not be encouraging, let alone devoting developer time to. Recommend closing and suggesting either rethinking the purpose of the description they are entering, using the spreadsheet importer, or creating a plugin.

  3. The persistent identifier takes up exactly as much screen real estate as every other field. I can’t imagine we’d want to have varying sizes of fields, so I recommend closing the ticket.

  1. Close (custom reports will allow).

  2. Close (spreadsheet or plugin?)

  3. Close

@Tom Steele

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

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

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

  1. This person wants to enter in Finding Aid Data last, in the resource editor. Request is minor but this feels to me to be trivial. Pass, if it's possible to do without difficulty.

  2. This is a very reasonable request and rather self explanatory. EAD is more granular than ArchivesSpace (at least in this instance). A comment on the bug does point out Subjects and Agents also could have multiple identifiers (OCLC number, LCCN, ARN). Pass. (Feels minor to me, request says major)

  3. This request is for profiles for staff. I think this would only be possible if staff accounts were not Agents in the system. This topic will need discussion with the larger group. Our working group uses Trello to track workflows, and there are many other third party software that does what they want.

  1. Close (plugin? make everything customizable?)

  2. Needs specification! New Agents module already does this; export/import implications; when does the component unique id take precedence? Should they be searchable? Should metadata examine the import/export implications (Y)

  3. Close, plugin?

@Matthew Neely

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

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

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

  1. This ticket is requesting that the full title of a record is displayed in the navigation bar. I think this would be a good enhancement. The comments also raise the possibility of including the date and extent. This might be something for usability to look at?

  2. This ticket is requesting the ability to be able to list repositories in the PUI in whatever manner is required rather than the default alphabetical setting. I agree that this would be a useful feature and we recommend passing this.

  3. The ticket is requesting ability to create dynamic links in related and separated materials notes. The ticket was reviewed by Dev / Pri in 2020 and suggested that community feedback was needed.

  1. Pass, but should we extend to staff-side tree? Length of field?

  2. Pass. (Where should this be set? Probably gear. Admin permissions only)

  3. Close. Not doable. Notes stored as JSON object and aren’t linkable- would require substantial development

@Angela White

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

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

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

  4. https://archivesspace.atlassian.net/browse/ANW-1382

  1. Wants to have the bioghist associated with agents marked as creator or source exported in EAD. I’m not sure if this is a good idea--it could quickly become unwieldy with multiple creators/sources and/or really long bioghist notes attached to agents. Is there an easy way to make this optional?

  2. Wants to embed digital objects into agent records, for the purposes of displaying portrait thumbnails, etc. Again, I’m not sure this is a good idea. Maybe there’s a way to display linked resources and digital objects to agent records (as a list at the end)? This feels like a larger discussion.

  3. Lydia wants chevrons for expandable items in the PUI container inventory, plus expand all. This is related to https://archivesspace.atlassian.net/browse/ANW-868 It seems like we should decide on PUI Container Inventory issues all at once? This seems fine to me but may not make sense without other enhancements.

  4. Pass. This ticket required metadata committee feedback, which was provided.

  1. Close. Not a good idea.

  2. Close. Free floating digital objects seems dangerous

  3. Close, probably buggy and slow and can get to this other ways

  4. Pass, minor.

@Althea Topek

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

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

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

  1. Pass- the PUI should be able to sort any list chronologically, alphabetically, and in this case “smallest-largest”. Is there enough information here?

  2. Is this still an issue?

  3. Pass

  1. Close. Wants a sort, but not a filter. New filters instead?

  2. Close. Update the plugin?

  3. Pass, but would need to have root access to server to make these changes, so these should be separated out of config

@Randy Kuehn

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

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

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

  1. Pass update report descriptions for accuracy

  2. Pass name change "Agent List Report"
    for consistency
    Pass include limit option for agent type
    Questions: Is this report helpful? Why doesn’t the report include all agent types?

  3. Recommend: Community Development

  1. Community development; can use Weblate to rename

  2. Pass the name change to make consistent with the other report. probably can’t pass the rest of it


@saron tran

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

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

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

  1. pass but could also use a little more additional info or a little more explicit spec

  2. pass agree with Blake that multiple creators should show up in the PUI and not just one

  3. pass, i clicked on a digital works to see the list-- and then clicked search and used one of the titles from the digital works and it was not found during the search



Action items

Decisions