Page Comparison

Tom Steele

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

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

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

1. I can see the advantages to import several subjects at once, so I think this should probably pass. 

2. Another straight forward request. Of course this would require new tags such as subject_1_source_1, etc. so I don't know how hard it would be to implement. Not sure if it is major priority. pass.

3. Seems reasonable, Pass.

Keli Schmid

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

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

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

Matt Strauss

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

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

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

Daniel Michelson

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

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

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

1. Previous discussion of this issue stalled over the issue of how to deal with existing non-unique data. Joshua’s Shaw’s suggestion to add warnings about duplicate barcodes is a good interim step. These warnings would be in the log (for location record imports) or as an additional yellow “banner” message (for creating or modifying location records in the staff interface).

2. This ticket gives a bunch of suggestions about the custom reports functionality, but it predates the actual release of that module, so items 1 and 2 have already been implemented.

   1. Item 3 is partially resolved, but the complaint about having to select the Custom Report button which is in the alphabetical list of canned reports to get to the reports is understandable. Depending on how the list of reports is actually created (is it hard-coded or generated?), we should follow the suggestion of just having all the custom reports automatically added to the alphabetical list or we should have the Custom Reports button placed more prominently (at the top?).

   2. Item 4 is concerned about the potential for the drop-down selection box in the interface for running custom reports to become hard to use if dozens of reports are created. A ready list and/or a type-ahead is suggested as an alternative. I don’t know what a ready list is, but I’m not in favor of a type-ahead, since that requires remembering what the title of the report is.

3. Notes cannot currently be included in custom reports. I can see lots of potential uses for being able to create a report of all the (for example) Conditions Governing Access notes on resource records. My thinking is that it could follow the pattern of the Linked Records section and have all of the possible notes be included as checkboxes.

Matthew Neely

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

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

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

Randy Kuehn

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

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

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

1. Unable to reproduce in v3.2.0

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

3. Recommend waiting on implementation of

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

Althea Topek

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

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

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

Brian Hoffman (Unlicensed)

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