2024-09-03 Meeting notes

@Matt Strauss /all

Welcome

@Matt Strauss /all

1. Finalize Dev/Pri Work plan for 2024-2025:

Dev Pri 2024-2025 workplan

2. Community Feedback Tickets schedule

1. Thimios has a webinar coming up on October 3 at 12 PM EST about how to write successful feature requests for ArchivesSpace: https://lyrasis.zoom.us/webinar/register/WN_Q0kysyCaSIuO1lZJXa3wfw 

2. Matt sending our his ticket this month. Continuing at a monthly pace from there. Will add to list as needed.

3. Reminder: Ticket reviewer is in charge of commenting decision on Jira ticket. Sample format:
   ”The Development Prioritization subteam reviewed this ticket during its meeting on [date]. The team recommend passing this ticket for development.”

@Alexander Duryee

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

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

1. Tested this on sandbox and found the same issue - the MARC included in OAI exports is incomplete. In addition to the leader and 008 fields, the 040 is also exporting as a blank node, despite having information in the non-OAI MARC. Recommend passing.

2. Tested on sandbox and confirmed the error. This appears to be an oversight from ASpace 3.0 development. Recommend passing.

1. Pass

2. Pass

@Keli Schmid

1.

2.

1. Anne Marie Lyons has commented that the user’s request can be accomplished through a custom report: “Search on recently created accessions that are Gifts and display the Content Description box. Also include and display linked Agents.” Recommend informing end user and closing ticket

2. I believe this user may be confusing the purpose of inclusive v. bulk dates: “Inclusive Dates” indicates the earliest and latest dates included in the collection. Sometimes, there will be a “Bulk Dates” listed as well, which means a large portion of the materials covers this more specific span of time. If present, this will be found under the inclusive dates. I do not see a bug or error here.

@Mattie Clear

1.

2.

1. Confirmed that it is an issue. Updating to allow the cancel functionality would align with what other similar functionalities allow. Recommend Passing.

2. Confirmed that it is an issue/bug that should be resolved to allow for ease of updating events with the proper agents. Recommend passing.

1. Pass and investigate further within Dev Pri (Dustin and Thimios)

2. Pass

@David Krah

Can’t reproduce - needs API interaction I think, which I am not able to do; but error readout may indicate that ‘agenttype_narrow’ may be misformatted? Could 'agent_type_narrow' work?

Need more information--Donald reaching out to OP to ask if this is still an issue on current release

@Regine Heberlein

We discussed this during the meeting and decided to pass it based on the very thorough testing already done by the submitter, Valerie Addonizio.

Pass

@Elizabeth Peters

Confirmed in general but not in specific. May need further clarification. Remaining questions:
-Difficulty of coding hover text within dropdown menus
-Desirability in dropdowns with customizable vs non-customizable controlled value lists

Close and refer to user docs subteam

@Dalton Alves

The user-story of this request makes a lot sense. As requested, this feature would be limited to only top container instances, but it also seems relevant to all linked instances of an accession record (including digital object instances). I'm unsure of the value in terms of prioritization – it depends on how users within the community are using accession records and linked instances. This use-case could probably be fulfilled via the API, but from a practical standpoint it does make sense as an enhancement of the spawning feature. I think this would benefit from additional community feedback to better refine the scope and gauge the development value.

Defer to next meeting--Dalton will draft a rewritten version of this ticket and comment to send for community feedback.

@Dustin Stokes

Including enums in this subreport will make it more complex but it does make sense to add them. I’m aware of several large institutions that use enum user defined fields to store data that would make sense to include in reports. A couple of known examples in use are “Curatorial Department” and “Fund name”.

Pass

@Bonnie Gordon

In the bulk import template, different types of agents are broken out into different columns. E.g., the column names for the ID field are people_agent_record_id_1, families_agent_record_id_1, and corporate_entities_agent_record_id_1. This ticket is requesting that these different types of agents are collapses, and that the agent type is determined a different way. If this is a small amount of development work it should be passed.

Request more information, specifically for some example scenarios and a mock up of the desired solution.

@Brianna McLaughlin

I have strong feelings about this one, and I think anyone managing more than one repository would as well. This ticket is self explanatory--the reporter would like to be able to set a default repository. I can confirm that the default repository is whichever repository is first numerically based on repository ID, not the most recently used repository. I don’t think setting one default for all users would be as helpful as the ability to set a default per user whether that’s the sysadmin setting the default or allowing users to set their own default. Recommend passing.

Pass

@Matt Strauss

1. I know earlier Dev Pri attempts to replicate this bug were not successful, but I’ve confirmed the described behavior in the ticket and attached videos in both the testing server and my organization’s installation. I think the bug could be more widespread than just this field - I’ve replicated the behavior with other controlled value defaults that aren’t required fields, such as Finding Aid Status and Description Rules. Recommend passing.

2. I agree that searching by a person’s actual name would be more a bit more straightforward than searching by username. However, I’m wondering about the development time required for a minor improvement.  Also, would this even work as described (is the “created by” and “last modified” information even connected to staff agent records)?