2020-12-01 Meeting notes

@Angela White

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

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

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

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.

@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. 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)

3. Since a resource can have restrictions without its accessions having restrictions, would it be more accurate and possible to provide a parent restrictions apply response for child records?

1. Will do more testing

2. More information needed

3. More information needed (reply w/alternate solution)

@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.

1. Pass with clarification

2. Close (more info not provided)

3. Close (custom reports will be available in a future release - timeframe unknown)

@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.

Split into 2 separate tickets

1. Pass - higher priority

2. Pass Unsuppress ticket - trivial

@Matthew Neely

1.  This ticket is seeking functionality to ensure that RDE template are repository specific and only visible to the specific respository to which it is attached. This seems a useful feature for institutions using multiple repositories and would help to ensure consistency.

2. This ticket is to make the ability to create locations as a specific permission in user group settings in order to separate from the repository-managers group. This would enable admin accounts to have a greater degree of control over user groups and assigned system permissions.

3. This ticket is seeking to add a symbol to the Collections view in the PUI to distinguish between resources which only have a collection level description and resources comprised of a an inventory. Suggestion is to add a symbol to help differientiate. Might something for usability to test?

1. More info needed - How should it appear? Should it apply to other templates?

2. Pass

3. Close - will not do (recommend local plugin)

@Althea Topek

1. Usability recommends to change the default in the config file to display all notes associated with an archival object in the collection organization view; should not display inherited information (display unique information only). Create new ticket to address “additional description” issue (collection overview, archival object view). Is it possible to add this type of preference to repository preferences rather than needing to edit the config file?

2. Usability added a mock-up and recommends this pass.

3. Usability added mock-ups and recommends this pass

4. Usability recommends passing - added new comment.

1. @Althea Topek will compile a list of notes - will revisit at the next meeting

2. @Christine Di Bella will discuss other options with @Althea Topek
   @Althea Topek will bring back to Usability to review

3. Recommend plugin for community development

4. Pass w/ character limit

@saron tran

1. I agree related agents list should be paginated. Are there other places that need this? This issue remarked on the linked records which are paginated (and somewhat configurable #AppConfig[:default_page_size] = 10).

2. This request is to add the static plugin to the core code and enhance it’s functionality.

3. There should be something in place to deter a brute force attack against the staff interface login. Possibly need more details or just copy something standard in regards to login and locking out or recaptcha.

1.  Pass-- probably review other lists to make sure they are paginated as well

2. existing plugin-- can contribute to it for the requested enhancements

3.  

@Maggie Hughes

1. Kevin in comments added solution: $e for relator term AND $4 for relator code. Create companion ticket to request that role attribute in EAD2002 has the relator term.

2. Seems like it would be useful for archivists. Can we use rules from existing sorting functionality or would we need a spec/new standard (NISO?)? Keep priority as major or change to minor?

3. <daoset> in EAD3 is “An element for binding together two or more links to digital archival objects.” Should be a subtask of or linked to ANW-472. Could have Metadata Standards sub-team weigh in.