2020-11-03 Meeting notes

@Matthew Neely

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

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

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

1.  This ticket is seeking the functionality to bulk select and move multiple records in reorder mode using the shift key. Attempting this in a Mac opens a new browser window. The functionality to move multiple records already exists and is documented in the Help Center - using ctrl + click. As the functionality already exists I’m not sure this should be prioritized for development.

2. This ticket is seeking the ability to import multiple digital objects and associate them to an archival record using the Harvard Digital Object spreadsheet . It’s currently only to import one and further digital objects then need to be linked manually. I agree that this functionality would be useful. Would this be suitable for community development?

3. This ticket, as far as I can understand, is seeking functionality to link existing box descriptions in Resources to locations and containers using a bulk functionality. At present box descriptions can only be linked one at a time via Instances. I think this would be very useful for collection and location management.

1. Close ticket as fixed, add comment saying that we’ll reopen if comment recurs.

2. Pass

3.  Pass

@Angela White

1.  This ticket wants to rename “Repository Processing Note” to “Internal Repository Note,” make it indexable, and be able to run reports for repository notes. This would certainly add some functionality, but I’m not sure that this is a high-priority set of changes. I’m unclear how other institutions use this note--at mine, we don’t really use it at all.

2. This ticket seeks to have a “suppressed” indicator in the record tree in the staff interface. Currently, this is only visible within the resource record when you’ve clicked on a suppressed record (or through search results). This seems like an easy fix to make complex collections more easy to navigate in the staff interface.

3. This ticket asks for visible deaccession records in the PUI in the same way that accessions can appear. I imagine it would be fairly simple to add a “publish” checkbox to the deaccession part of the accession record? If so, this is worthwhile to consider. I’m not sure that this deserves high priority unless it’s truly simple to accomplish. Most institutions I know using ASpace don’t display their accessions in the PUI; though my institution does, I don’t think I’d want the deaccessions to display.

@Althea Topek

1.  Agents, Subjects, and Top Containers are the only functions that allow Browse and Create. If a Create option was added to Related Accession, should it also be added to: related resources, classification, and location?

2. I don’t think Extent Dimension should be a controlled value but there should be a way to set Width as a default

3. Usability discussed this ticket at our last meeting and recommend the publish_partial_tress plug-in be added to the core code.

1.  Close and add comment saying if it is highly desired it can be reopened.

2.  Add comment to clarify that this should be changed to a non-editable controlled value and pass.

3.  Pass

@saron tran

1.  I like the idea and seems like low hanging fruit. I think the suggested place to put the link to a static page is a decent place (compared to the ‘browse’ or ‘create’ drop down menus. I wonder if another good place might be on the import page itself (and maybe less work)?

2. I checked the cog wheel > manage groups > create group and did not see existing user group management configurability of ‘publish’. I could see how it would be good to have certain groups of users who do the initial draft and then have someone like an editor be the one to actually publish the resource.

3. I’m not sure on this one but is this request attainable with the AppConfig[solr_params] configuration?

1.  Pass

2.  Close, add comment recommending pursuing a plugin

3.  Close, add comment with search suggestions and ask to reopen if issue persists.

@Maggie Hughes

1. Ticket was created earlier this year, good screenshots. Bootstrap gives ASpace responsiveness, generally? Link to ANW-1041 (mobile for SUI). Rec: pass.

2. Created in 2017, no new comments or watchers. Main question is, how user-specific is this preference? Rec: Awaiting More Info or Close.

3. Columns currently configurable are accession browse, resource browse, digital object browse, and search. Rec: pass, keep priority minor.

1. Pass along with 1041 with comments about type of phone.

2. Close, comment that it’s too specific other work is coming.

3. Pass

@Randy Kuehn

1.  I was unable to reproduce the error in v2.8.0 on Windows 10 using the directions provided (https://archivesspace.github.io/tech-docs/administration/windows.html). However, the error did occur when not running against MySQL and setting the jetty shutdown parameters
   Replied to ticket asking for clarification on procedure
   Update: Others have experienced this issue.
   I’ll try a few more scenarios.
   Status: ongoing
   Any advice is more than welcome :)

2. Need Lora’s advice
   I can ask Joshua for some test data and try to reproduce the error if it would be helpful

3. I didn’t realize merging agents across repositories could cause data loss.
   Recommend preventing data loss by requiring agent merge permission include access to all necessary fields (permission dependancies) such as contact info

4. I was unable to reproduce the error in v2.8.0
   I have run into a somewhat similar problem where objects disappear from totals after an upgrade...reindexing didn't help...resaving individual objects seems to correct issue (not ideal)

1.  No change, Randy will continue examining for next time

2. Close (non-standard migration)

3. Pass, if agent contact details will be lost in merger and user does not have permissions to view, block the merger.

@Daniel Michelson

1. This ticket notes that when you browse subjects in the PUI and then filter by repository, the linked results are direct links to the subject page, which doesn’t retain the filter. It’s not clear to me whether this is intended behavior, but since it is not possible to filter an individual subject page’s results by repository, I think this ticket needs to be addressed.

2. Ticket is vague and appears to be at least partially inaccurate. Left a comment asking for more details, but did not receive a response. Can either change to awaiting more information or close.

3. They’re looking for a specific new report. Seems reasonable to pass for community development, but I wonder if we should have a different process for handling requests for new reports.

@Lora Woodford

@Mark Cooper (Unlicensed)

Dev Pri needs additional input from Development regarding feasibility

Notes: This ticket is requesting bulk edit functionality to manage controlled lists. Currently list values can be merged but only one term at a time. The ability to merge multiple terms concurrently would be very beneficial for institutions undertaking large scale migration and data cleaning projects. The ticket also requests two changes to the delete functionality for managing controlled lists. The first is for the ability to select and delete multiple values at the same time and this does seem a worthwhile improvement. The second is to be able to delete suppressed terms without having to unsuppress them. Would require the delete option to remain visible when a term has been suppressed and this would seem a good idea, especially if it could be combined with the ability to delete multiple values concurrently.