Versions Compared

Key

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

...

Topic / Who

Tickets

Notes

Decision

Randy Kuehn

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

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

  3. Jira Legacy
    serverSystem JIRA
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-698

  1. Confirmed: improperly formatted archival object title tag can lead to title not displaying in folder tree (v3.2.0)

  2. Recommend waiting on implementation of

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

Matt Strauss

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

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

  3. Jira Legacy
    serverSystem JIRA
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-426

Althea Topek

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

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

  3. Jira Legacy
    serverSystem JIRA
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-1544

  1. link spawning specification in comment and close

  2. who owns the accession import template?

  3. is Anne’s comment from July enough of a specification?

Brian Hoffman (Unlicensed)

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

Tom Steele

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

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

  3. Jira Legacy
    serverSystem JIRA
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-531

Keli Schmid

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

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

  3. Jira Legacy
    serverSystem JIRA
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-31

Daniel Michelson

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

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

  3. Jira Legacy
    serverSystem JIRA
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-346

Matthew Neely

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

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

  3. Jira Legacy
    serverSystem JIRA
    serverId36c489e2-4fb0-353a-985b-64038401be2f
    keyANW-195

  1. Ticket requesting functionality for admin user to be able to suppress fields in the SUI not included in an institution’s metadata schema. This ticket was previously discussed at Dev Pri in 2020. I think there is merit in this but I recall that discussions at the time suggested that this could be addressed by training and metadata documentation. I do think there would be usability benefits in being able to customise fields to only those required by an institution.

✅ Action items

  •  

⤴ Decisions

...