2023-03-07 Meeting notes

 Date

Mar 7, 2023

11:30am-1pm ET

Zoom link

 Participants

  • @Randy Kuehn

  • @Matthew Neely

  • @Daniel Michelson

  • @Tom Steele

  • @Christine Di Bella

  • @Brian Hoffman (Unlicensed)

  • @Matt Strauss

  • @Keli Schmid (regrets)

  • @Donald Smith

 Goals

 Discussion topics

Topic / Who

Tickets

Notes

Decision

Topic / Who

Tickets

Notes

Decision

@Daniel Michelson

  1. ANW-1632: Bulk DO Import Spreadsheet: Would like more fields available to describe digital objectsReady for Inclusion in Release Candidate

  2. ANW-1486: Bulk Edit Digital Objects using a template, not a plug inAwaiting More Information

  3. ANW-1204: use date calculator (calculate date feature) to calculate bulk dates for a body of materialsClosed-Will Not Do

  1. This ticket wants the ability to include additional descriptive metadata elements to the bulk digital object importer. We’d previously been unwilling to make changes to the abilities to add descriptive metadata to digital objects, due to the question of whether such data should even be part of the digital object schema. With the recent community meeting on digital objects, are we at the point where we can make a decision?

  2. This ticket is a little confusing. I think it’s basically just asking for the ability to bulk edit the File URI field in the file version subrecord in digital objects. I’ve asked the submitter to clarify on the ticket.

  3. This ticket wants the ability to generate bulk dates via the date calculator “by determining the first and last date within one standard deviation of the average date and providing these as the bulk date range.” This is a very interesting idea, but raises the question of whether this is something that would reliably create accurate bulk dates, given that the number of date subrecords does not necessarily correspond with the extent of material.

  1. Pass

  2. Awaiting more information

  3. Close. Suggest looking at plugin to achieve this.

@Randy Kuehn

  1. ANW-1649: Giving the OAI feed a false token throws an invalid OAI errorReady for Implementation

  2. ANW-1655: LDAP bind password visible as plain text in log file when error occursReady for Implementation

  3. ANW-1668: Scalable logos for Staff Web Page and Public PDFsClosed-Complete

  1. Pass - OAI error response should be in the proper format - example in ticket (submitted by LYRASIS)

  2. Unable to reproduce - Requires LDAP authentication setup - source.inspect appears in authentication_manager.rb (Log.error("Error communicating with authentication source #{source.inspect}: #{$!}")) - Recommend Pass to Development to check current version / redact password

  3. Pass - Confirmed :frontend_branding_img logo does not resize automagically on staff-side - Recommend responsive design

  1. Pass

  2. Pass (unclear if stil an issue in later versions)

  3. Pass

@Matthew Neely

  1. ANW-1665: Browse By Accession From Controlled Value List Shows ALL Accessions Rather Than From The List OnlyReady for Implementation

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

  3. ANW-1157: I want an easy way to understand which materials have been digitized within the context of an archival collectionClosed-Will Not Do

  1. Had difficulty replicating but the ticket is saying that browsing and then filtering from the Controlled Value list - processing status, is not working correctly. Followed the route in the ticket and went from 7 results to 181 results using the same filter. Suggest passing as appears to be a bug.

  2. Identified in testing of ANW-901. Agent contact details are being indexed and impacting on search results. They should not be indexed. Recommend passing.

  3. This ticket also relates to ANW-1206 and is seeking a way for digitized materials to be surfaced in search results and visually in the PUI. Agree that this would be beneficial to researchers but issue of digitized items and resources records having different titles could addressed through metadata workflows. I think this would be good functionality but needs a full specification and discussion with community around use of digital objects.

  1. Pass

  2. Pass

  3. Close. Part of ticket moved to ANW-1206.

@Keli Schmid

  1. ANW-1669: Assessment Attributes - ability to reorder default and custom attributes as one listReady for Implementation

  2. ANW-1670: Assessment Attributes - ability to delete or hide unused default attributesReady for Implementation

  3. ANW-748: change the stylesheet of the Collection Organization to be more clear for hierarchical order.Closed-Will Not Do

  1.  

  1.  

@Matt Strauss

  1. ANW-1654: Add Dark Mode to SUIReady for Implementation

  2. ANW-1293: Update/change Records Link for selected Digital Objects from search results.Awaiting More Information

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

  1. Pass. I could see this being a frequently used feature. The tickets states that this is already a feature in the PUI (though I haven’t been able to independently confirm this).

  2. Discussed previously at the Feb. 2022 Dev/Pri meeting along with ANW-1295.  A spec was requested after that meeting, but it doesn’t look like one has been provided.  At a recent Digital Objects Member Discussion, poll results were shared that suggests that the ability to bulk edit digital objects would be widely used.  I suggest reiterating the need for a spec so that this can move forward.

  3. Discussed previously along with ANW-1293, at which point more information was requested.  I think this request would result in taking a two-click operation down to one.  In terms of development around digital objects, it might make more sense to devote resources towards adding functionality rather making exiting functionality slightly more streamlined.

  1. Pass

  2. Awaiting more information. Specification needed.

  3. Close.

@Tom Steele

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

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

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

  1. This problem is one I have noticed but assumed it was working as intended. The problem is these subjects get their type from the Occupation field. I personally have been merging them with subjects with the same name with type Topic because I feel it is more helpful to have just one entry for Presidents (or whatever the occupation is) instead of 2. Do we need more feedback on this or should Occupation be changed in the LCNAF to Topic to avoid duplicate subject headings? The user assumes it's lack of identifiers but from my experience I'm also positive it's the Occupation type that is making the plugin not see it as a duplicate.

  2. We discussed this before but it's now more clear what the user wants. my question is should it be an exact match of the parallel name or should a keyword search for "Free church" then come up with "search under (display name)"?

  3. I was able to duplicate the problem. recommend pass.

  1. Close

  2. Close

  3. Pass

 Action items

 Decisions