Page Comparison

Matthew Neely

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1433

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-309

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-768

1. This ticket is requesting that the extent calculator also creates a further extent for digital objects linked to the record. I can see a practical use for this but wonder if it would duplicate extents created in resource records for digital material? Might be useful for users know that there are X number of digital objects linked to a resource record.

Daniel Michelson

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1260

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1417

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1423

1. Metadata Standards just issue a call for feedback on extents for the MARC importer, so I suggest moving this ticket to awaiting more information.

2. Deaccession subrecord publishing is currently an all or nothing affair governed by a config setting. This ticket would like a publish checkbox added to the subrecord in order to selectively publish deaccession subrecords. I support this ticket, but I think the tooltip for the publish checkbox should note that it will only be published if the config option is also enabled.

3. This ticket is asking for four additional features for the Collection Management subrecords:

   1. Implement the download CSV feature from the browse view. Since this capability is already present in most browse views, it seems like it would be straightforward to do.

   2. Enable the Collection Management subrecord on archival objects, as well as resources, accessions, and digital objects. I think this is a great idea, it makes the subrecord much more flexible.

   3. Ability to set a Collection Management subrecord as completed or inactive. This functionality already exists in more flexible manner than suggested by using the “Processing Status” field.

   4. Add a “Supplies Used” field. I don’t see any downside to adding this.

saron tran

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-621

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1462

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-608

1. indicator is a required (checked by creating a resource-- and adding a container instance-- also tried via rde and similar web form popped up where indicator is required)-- also checked ead import and it threw the appropriate explicit error indicating indicator is required.

2. close-- I think the plugin is sufficient for now

3. see ticket for my comments. kind of leaning towards closing as the functionality where you select and drag with options of insert before / after / as children works well. but the cut and paste buttons don’t work too well from what I saw

Angela White

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-666

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-889

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-10

1. I recommend closing this ticket per commentary of the metadata standards subcommittee on

   Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-320

   .

2. This looks like it’s been taken care of--users are able to set preferences for top container columns and indicate the default sort column. Close.

3. This is a very old ticket that I think is mostly resolved? The new reports feature allows custom reports for classifications. Also, classifications can be assigned to digital objects, which was another issue that came up. Close.

Tom Steele

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1458

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-538

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-358

Althea Topek

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-1464

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-562

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-996

Randy Kuehn

1. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-334

2. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-309

3. Jira Legacy
   server System JIRA serverId 36c489e2-4fb0-353a-985b-64038401be2f key ANW-917