2022-04-05 Meeting notes

@Matthew Neely

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

1. This ticket is requesting that the extent calculator also creates a further extent for digital objects linked to the record. I can see a practical use for this but wonder if it would duplicate extents created in resource records for digital material? Might be useful for users know that there are X number of digital objects linked to a resource record.

2. Usability recommended closing this ticket in April 2020 on the basis that there was not widespread calls for this functionality. Subsequent comments on the ticket have requested this functionality. The main functionality requested in the ticket is the ability to link or copy the Biographical/Historical note for an Agent record into a finding aid. The ticket also request other areas for linking data. I think we may need to consider asking for this ticket to broked down into several tickets. I think there is merit for having a biographical history pulled into a resource from associated Agents but there’s currently no direct mapping and would need to consider how this worked at collection, series, file levels etc.?

3. Metadata standards have reviewed this ticket following request by Dev Pri in May 2021. Metadata standards have suggested changes to SUI to accomodate multiple ref tags. Recommended passing.

1. Would need spec. How would multiple extents work? What about different levels of description?

2. Close. Link to relevant tickets. Wait on spawning specification.

3. Pass.

@Daniel Michelson

1. Metadata Standards just issue a call for feedback on extents for the MARC importer, so I suggest moving this ticket to awaiting more information.

2. Deaccession subrecord publishing is currently an all or nothing affair governed by a config setting. This ticket would like a publish checkbox added to the subrecord in order to selectively publish deaccession subrecords. I support this ticket, but I think the tooltip for the publish checkbox should note that it will only be published if the config option is also enabled.

3. This ticket is asking for four additional features for the Collection Management subrecords:

   1. Implement the download CSV feature from the browse view. Since this capability is already present in most browse views, it seems like it would be straightforward to do.

   2. Enable the Collection Management subrecord on archival objects, as well as resources, accessions, and digital objects. I think this is a great idea, it makes the subrecord much more flexible.

   3. Ability to set a Collection Management subrecord as completed or inactive. This functionality already exists in more flexible manner than suggested by using the “Processing Status” field.

   4. Add a “Supplies Used” field. I don’t see any downside to adding this.

1. Awaiting more info

2. Pass with tooltip.

3. Pass 1, 2, and 4.
   
   

@saron tran

1. indicator is a required (checked by creating a resource-- and adding a container instance-- also tried via rde and similar web form popped up where indicator is required)-- also checked ead import and it threw the appropriate explicit error indicating indicator is required.

2. close-- I think the plugin is sufficient for now

3. see ticket for my comments. kind of leaning towards closing as the functionality where you select and drag with options of insert before / after / as children works well. but the cut and paste buttons don’t work too well from what I saw

1. Close

2. Close, use plugin. Maybe use a honeypot field

3. 1447 already addresses this. Close.

@Angela White

1. I recommend closing this ticket per commentary of the metadata standards subcommittee on .

2. This looks like it’s been taken care of--users are able to set preferences for top container columns and indicate the default sort column. Close.

3. This is a very old ticket that I think is mostly resolved? The new reports feature allows custom reports for classifications. Also, classifications can be assigned to digital objects, which was another issue that came up. Close.

1. Close.

2. Close, easy to sort with a click

3. Close.

@Tom Steele

1. straight forward request. Since one can do it in the spreadsheet importer it should be allowed in the staff interface. Unless the problem is the RefId has to be assigned at creation? Pass.

2. I think the workaround is fine, because it's the same workaround I use to delete records. Though this seems to be a popular workaround showing a demand for such a feature for transfer/delete/edit. Merits discussion before passing.

3. Unless I'm missing something seems a reasonable request. Pass.

1. Component ref-id not editable 1183. Close.

2. Close. The workaround is simple and prevents catastrophe.

3. Pass, important for events to be viewable in edit mode at the least. Not an actual subrecord, but in the list.

@Althea Topek

1. It looks like the extent calculator converts inches (from the container profile) to linear feet.

2. Close - there are other ways to fix this

3. Pass - I like option 3 (Adding a publication checkbox for each of the notes fields in the RDE form). This would make publish options consistent whether working in the record or adding via RDE.

1. See . Close, but need better documentation.

2. Close. New School roundtrip importer might work. Entirely for legacy data.

3. Pass for the 3rd option.

@Randy Kuehn

1. Recommend: Pass
   Comment section includes details.

2. Recommend: Pass Usability recommended closing in 2020 but more recent comments suggest otherwise - treating ticket as reopened

3. Recommend: Pass
   Space Calculator: Previous dev pri discussion is a bit hazy, but I would recommend passing it. Provide calculations with floor data being optional.

1. Plugin. (Image carousel plugin as starting place) Could mess up people’s landing page.

2. Dup (Close. Link to relevant tickets. Wait on spawning specification)

3. Pass, trivial, but need to know how it was done (make floor optional, both floor and room need to pop up)