2021-09-07 Meeting notes

@saron tran

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

2. ANW-1161

3. ANW-1193

1. does not need prio’d it has been fixed in 3.0.0 and need more details

2. couldn’t reproduce-- tried by spinning up dev environment-- exporting a couple of production ead xml and then importing it to one of two repos (as you can’t delete a repo unless there are more than one repo)-- and then deleting the repo where i was importing as the indexer was indexing those imported records-- but i would lean towards accepting the PR because I think Andrew understands the situation more than me – did not get around to testing with his changes in my dev env

3. leaning towards should be prioritized as – this info is not displayed on the page of the specific background job – however it is somewhat displayed in the background job page

1. Pass for notification of dropping barcodes

2. Close, can reopen it if replicated

3. Pass to community development, trivial

@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. Pass, find JSON Jira ticket, Minor

2. Fixed in 3.0, Close

3. Close. RefID not meant to be edited. If there’s a broader use case for this, submit a ticket for this. Consider using a ComponentID

@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. Pass (bug), major

2. Awaiting more information, can’t replicate until Jira ANW-1182 is resolved (@Daniel Michelson comment on date type)

3. Need to fix ANW-1182 first; awaiting more information: need specification

@Tom Steele

@Althea Topek

@Randy Kuehn

1. ANW-1178

2. ANW-1182

3. ANW-1203

1. Problem: Non-Roman Scripts searching support
   Recommend improving Chinese character support (search & sort)

2. Problem: Date span calculator tool cannot save the date elements to the resource record
   Tested in v3.0.2: Received “Date is invalid” error with 4 digit dates
   Recommend allowing 4 digit dates

3. Problem: Date calculator hangs with many components
   I assume this is accurate but was unable to reproduce in v3.0.2 due to “Date is invalid” error
   Recommend developer testing and improved data processing

1. Pass - Note: Need assistance working with Chinese characters. Please let us know if you know of any experts in the field that would be willing to assist.

2.

3.

@Daniel Michelson

1. ANW-1150

2. ANW-1161

3. ANW-1201

1. This ticket identifies several idiosyncrasies in the container labels export and I identified some others while doing testing. It appears to be attempting to provide data sufficient for both top container labels and sub container (e.g. folder) labels. However, it fails to export data for more than the first subcontainer in a top container, which makes it unsuitable for subcontainer labels. It also assumes a certain type of arrangement (series level at top and file level at bottom), which is common, but by no means the only reasonable arrangement.

I suggest having the container label export be limited to creating top container labels (a separate functional subcontainer label export could be implemented later if desired), so it should ignore subcontainers. It should also look for the first level of archival objects, rather than series level archival objects.

2. The necessary testing for this ticket greatly exceeds my (mostly non-existent) coding skills.

3. PUI slugs choke on “smart” quotes. I assume the desired behavior is for them to be converted to standard quotes, but we’ve previously agreed that ASpace does not provide support for non-UTF-8 encoding (not sure if that’s relevant).

1. Awaiting more information, need specification, can override with a plugin

2. (repeat)

3. Pass