Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Who

Topic

Notes

Decision

Matt Strauss /all

Welcome

Matt Strauss /all

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

https://archivesspace.atlassian.net/wiki/pages/resumedraft.action?draftId=3927080974&draftShareId=4886868f-d061-4dd8-9da0-0de572f94a99

  1. Community Feedback Tickets schedule

Alexander Duryee

1.

Jira Legacy
serverSystem Jira
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-1787

2.

Jira Legacy
serverSystem Jira
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-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.

Keli Schmid

1.

Jira Legacy
serverSystem Jira
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-1788

2.

Jira Legacy
serverSystem Jira
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-1912

  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.

Jira Legacy
serverSystem Jira
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-1867

2.

Jira Legacy
serverSystem Jira
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-1889

  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.

David Krah

Jira Legacy
serverSystem Jira
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-1753

Regine Heberlein

Jira Legacy
serverSystem Jira
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-1876

Elizabeth Peters

Jira Legacy
serverSystem Jira
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-628

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

Dalton Alves

Jira Legacy
serverSystem Jira
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-1828

Dustin Stokes

Jira Legacy
serverSystem Jira
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-1802

Bonnie Gordon

Jira Legacy
serverSystem Jira
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-1839

Brianna McLaughlin

Jira Legacy
serverSystem Jira
serverId36c489e2-4fb0-353a-985b-64038401be2f
keyANW-630

Matt Strauss

  1. Jira Legacy
    serverSystem Jira
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-1852

  2. Jira Legacy
    serverSystem Jira
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-1792

  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)?