2021-06-01 Meeting notes

Date

Jun 1, 2021 3:30 GMT / 11:30 ET / 10:30 CT / 9:30 MT / 8:30 PT

https://lyrasis.zoom.us/j/95479392806?pwd=S0FwbmpCbWVXT2RaTWhjUXhkMVFrZz09

Meeting ID: 954 7939 2806
Passcode: 965674
One tap mobile
+13126266799,,95479392806#,,,,,,0#,,965674# US (Chicago)
+19292056099,,95479392806#,,,,,,0#,,965674# US (New York)

Dial by your location
+1 312 626 6799 US (Chicago)
+1 929 205 6099 US (New York)
+1 301 715 8592 US (Germantown)
+1 346 248 7799 US (Houston)
+1 669 900 6833 US (San Jose)
+1 253 215 8782 US (Tacoma)
877 853 5257 US Toll-free
888 475 4499 US Toll-free
Meeting ID: 954 7939 2806
Passcode: 965674
Find your local number: https://lyrasis.zoom.us/u/ahUXQvjfH

Participants

  • @Maggie Hughes

  • @Randy Kuehn

  • @Daniel Michelson

  • @Matthew Neely

  • @Althea Topek

  • @saron tran

  • @Angela White

  • @Brian Hoffman

  • @Lora Woodford

  • @Christine Di Bella

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

@Randy Kuehn

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

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

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

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

  1. Metadata Standards subcommittee approved - Recommend: move to development

  2. Recommend: local plugin or community development

  3. Summary: Notifications when...
    a new user profile is created and needs permissions assigned
    review a completed Assessment
    end dates for restrictions arrive
    end dates for copyright arrive
    I would also like to be able to create customizable reports
    - Where do we stand on notifications within AS?

  4. Would it be possible to copy relationships?
    (“changing the relationship from one of subject/resource to agent/resource”)
    It seems like this type of bulk modification would need an update plugin, no?

  1. Pass

  2. Yale plugin may resolve the issue (https://github.com/YaleArchivesSpace/yale_pui_pdf )

  3. Ticket should be broken down into separate tickets for each component

  4. Dan will add Smith script link

@Daniel Michelson

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

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

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

  1. This ticket wants the contents of a note preserved when changing the note type (language in the ticket is inconsistent, but this is what they mean). I interpret this as wanting subnotes (specifically text) to remain when changing types. If this is feasible from a development perspective, I recommend passing.

  2. I cannot think of any reason why a user would intentionally import a file with no records in it, so I agree that it should be considered a failed job. It’s a very minor issue, so changing the priority to trivial seems appropriate.

  3. This ticket is requesting that the default setting for whether to include unpublished records and subrecords when generating a PDF on the staff side be customizable. While the justification is workflow specific, it seems reasonable to make that a setting in the config file and passing as trivial.

  1. Pass

  2. Pass - Warning No Changes/No Data Found

  3. Pass - User Preferences (Trivial)

@saron tran

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

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

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

  1. does not need prioritization as ArchivesSpace can already accomplish this first part via “Download Container Labels”. They also ideally want ArchivesSpace to be integrated with the catalog which would need more details in regards to scope and specifications.

  2. does not need prioritization – I could see how they plan to use something like this but not sure how useful it would be for all users of ArchivesSpace. If the consensus is this would be super useful to many then I would vote for prioritization. Miloche suggests using an outside authority control system e.g. LCNAF or SNAC for the master record and adding appropriate information in the ArchivesSpace record to ‘link’ out to these resources i.e. the Record Control Information section.

  3. needs prioritized – enhancing the validator – also there might be a bug / not working as expected – see example in the Jira issue. Additional notes from Miloche: The instructions (https://archivesspace.atlassian.net/wiki/spaces/ArchivesSpaceUserManual/pages/1173913646) for the container fields says: 

    the ingester will try to find an already-created Top Container in the database.

If you have defined a barcode:

If there's a match for the barcode for that resource, that Top Container will be used without further checking.Otherwise, a new Top Container will be created.

If you have not defined a barcode:

The type and indicator will be used to search the database for a Top Container that is already associated with the resource;Otherwise, a new Top Container will be created.

Which to me means if there's a Box 1 and Box 2 without a barcode in the record AND a Box 1 and Box 2 with barcodes are in the spreadsheet, new top containers should be added, i.e. the box 1 without a barcode is different from the one with a barcode.

In this scenario, you should be able to add multiple box 1's, each with different barcodes and new containers would be added for each.

So if this isn't how the importer is supposed to work, the instructions need to be updated.

  1. The Download Container Labels option should suffice - Integrating with catalogs is out of scope

  2. More Information - needs spec

@Maggie Hughes

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

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

  1. Tried to replicate this issue in the sandbox in version 3.0 on Chrome and Firefox (screen captures attached). I had the same results on both browsers: It displayed the first 10 search results and I did not get the scroll bar on the right-hand side to indicate that there were more search results. Keying down the list didn’t bring lower options into view either. Appears to be the same or similar issue as https://archivesspace.atlassian.net/browse/ANW-897

    Re: Pass.

  2.  

  3. Tried to replicate in sandbox v3.0 and the relator terms terms did import back into ASpace. Think this issue has been fixed in recent updates. Rec: Close.

  1. Pass

  2.  

  3. Close - Issue resolved in 3.0

@Angela White

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

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

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

  1. There are two distinct issues in this ticket: the note type, label, and content do not populate in RDE templates--this is a problem and I think we should pass this for dev. Top containers also do not populate in RDE templates, but I’m not sure that they should. Do we really want to be able to specify specific top containers in templates? What happens if that top container is deleted or modified? I think being able to chose top containers and then use the fill down function suffices for any use case I can think of.

  2. Resizing columns in RDE resets column visibility. This is a problem in v. 2.7, but I wasn’t able to replicate it in v. 3.0. Close?

  3. This ticket asks to be able to set the Ref ID in RDE. I’m not sure how helpful this functionality would be for the average institution. If it’s easy to accomplish, maybe we should pass with minor priority?

  1.  

  2.  

  3.  

@Matthew Neely

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

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

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

  1. The date span calculator is producing the relevant date span but when attempting to save the result, an ‘date is invalid and could not be created’ error is returned. YYYY, YYYY-MM, and YYYY-MM-DD are are rejected. This is error is affecting v. 2.8.01 and 3.0.0

  2. This issue is reporting that the date calculator hangs when calculating dates for larger resources with lots of dates attached. I’ve tested this in 2.8.01 with some larger catalogues (3000, 4000, 18000 archival objects) but not encountered this problem. I’ve not been able to replicate this in the 3.0.0 test instance. Hudson Molonglo have developed a possible fix but it relies on dates being expressed in iso8601 and are MySQL-specific.

  3. This ticket is seeking a bulk date function to be added to the date calculator. The ticket requests that the bulk date would be derived by determining the first and last date within one standard deviation of the average date and providing these as the bulk date range. The ticket doesn’t seem to be requesting that a bulk date be calculated by using the bulk dates fields in the Resource.

  1.  

  2.  

  3.  

@Althea Topek

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

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

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

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

  1. I would like to see a “more results” option added to the facet

  2. Pass

  3. I’m not opposed to this but I can’t find any EAD tags that describe weight. 

  4. Usability discussed this ticket and we wanted to know if this could be a function in the PUI that could be turned off or on. If not we recommend eliminating.

 

 

  1. Pass - Add “More Results” button to facet list - Include on all facet view pages

  2. Pass

  3. Close - Recommend creating local plugin

  4. Waiting more information - Will review again after recent view enhancements have been implemented - Usability discussed option of toggling on/off or eliminating

Action items

Decisions