Page Comparison

Tom Steele

https://archivesspace.atlassian.net/browse/ANW-1197

https://archivesspace.atlassian.net/browse/ANW-1198

https://archivesspace.atlassian.net/browse/ANW-1202

https://archivesspace.atlassian.net/browse/ANW-1209

1. User wants the find in manage top containers in resources to not require so far to drop down to select right resource. I tried in my own collection to find WHC--M--464 by entering "464" and sure enough it was listed  4th. I'm not sure if it's possible to make a drop down selection sort by relevance though. the work around is to enter the resource by the first characters in the resource name instead of keyword. In my example it came back with only 2 results. Maybe the user should use the keyword search instead? Merits discussion before passing.

2. ZoomText is not a free product so I can't really do anything with this one.

3. This request is straight forward. Duplicated on test server, the second file version replaced the URI in the PUI. both versions should display but aren't. Pass.

Althea Topek

https://archivesspace.atlassian.net/browse/ANW-1252

https://archivesspace.atlassian.net/browse/ANW-1273
https://archivesspace.atlassian.net/browse/ANW-1279

https://archivesspace.atlassian.net/browse/ANW-1209

https://archivesspace.atlassian.net/browse/ANW-1206

1. I’m not sure what they are asking for - is it to make the error text in the log red as opposed to green?

2. DACS does say “Expression of dates as all numerals is discouraged due to the differing conventions in the order of information.” but this is what the expression field is for so, close?

3. I’m having a hard time picturing how this would look - request more info?

4. New comment from usability - pass

Randy Kuehn

https://archivesspace.atlassian.net/browse/ANW-1359

https://archivesspace.atlassian.net/browse/ANW-1378

https://archivesspace.atlassian.net/browse/ANW-1270

https://archivesspace.atlassian.net/browse/ANW-1209

Matthew Neely

https://archivesspace.atlassian.net/browse/ANW-1293

https://archivesspace.atlassian.net/browse/ANW-1295

https://archivesspace.atlassian.net/browse/ANW-1386

https://archivesspace.atlassian.net/browse/ANW-1209

saron tran

https://archivesspace.atlassian.net/browse/ANW-1339

https://archivesspace.atlassian.net/browse/ANW-1336

https://archivesspace.atlassian.net/browse/ANW-1397

https://archivesspace.atlassian.net/browse/ANW-1209

Daniel Michelson

https://archivesspace.atlassian.net/browse/ANW-1263

https://archivesspace.atlassian.net/browse/ANW-1356

https://archivesspace.atlassian.net/browse/ANW-1360

https://archivesspace.atlassian.net/browse/ANW-1209

1. This ticket is asking for the pre-populate records setting (used to enable default values) be subdivided into separate settings for each module. The justification seems to be an attempt to turn this functionality into a sort of template. It would be a very awkward and roundabout way of doing it and would require adding dozens of separate options for the various record types and modules. Recommend closing.

2. This is ticket is asking for changes to custom reports, so we should revisit it after that functionality is actually released. These concerns (from July) may already have been resolved.

3. This ticket wants the option to add the agent or subject ID as a browse or search column. The use case is probably a bit institution specific, but it wouldn’t hurt to provide that option. If we do provide the option, it should be included for all other record types (resources, accessions, etc.). Suggest modifying as such and passing as trivial.

Angela White

https://archivesspace.atlassian.net/browse/ANW-1355

https://archivesspace.atlassian.net/browse/ANW-1364

https://archivesspace.atlassian.net/browse/ANW-1399

https://archivesspace.atlassian.net/browse/ANW-1209