Page Comparison

Randy Kuehn

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

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

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

1. Recommend: Community Development

saron tran

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

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

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

1. pass but could also use a little more additional info or a little more explicit spec

2. pass agree with Blake that multiple creators should show up in the PUI and not just one- would be curious to see points made for the opposing view

3. pass, i clicked on a digital works to see the list-- and then clicked search and used one of the titles from the digital works and it was not found during a search

1. Pass, minor. Not allow admins to lock preferences

2. Pass, all creators above the fold

3. Pass, include resources and archival objects in keyword search?

Daniel Michelson

https://archivesspace.atlassian.net/browse/ANW-1362https://archivesspace.atlassian.net/browse/ANW-1363

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

1. This shouldn’t happen, pass for development.

2. Digital objects can import with the file version NULL, which is treated as internal by the EAD export and labeled as publish = true in the staff interface (reporter did not state what happens with the PUI). Obviously this should not be inconsistent. It’s not clear to me why NULL values are allowed by the importer, so rather than changing the handling of them, it may be better to have the importer changed and a database migration for existing data (presumably to internal).

3. Global preferences set by one admin are not reflected in the global preferences for other admins. My (admittedly tentative) understanding of global preferences is that a single set is supposed to be shared by all users, that’s why only admins can set them. If that is the case, this needs to be fixed and I suggest increasing the priority to major.
   

1. Pass

2. Pass, NULL should be “false”

3. Pass. Should be documented more clearly: global preferences (user name) instead of global preferences; repository preferences (user name) instead of user preferences? No restriction on global preferences to admin [+ new feature request for truly global preferences]

Tom Steele

https://archivesspace.atlassian.net/browse/ANW-1385
https://archivesspace.atlassian.net/browse/ANW-1393

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

1. This will take some discussion, because I'm not sure how this is a problem. Shouldn't the user preferences take priority? (in fact, it says in user preferences these values can not be overridden) I suppose if so, then the pre populate records should either be removed as an option, or it should pre-populate in all instances. Trivial priority.

2. I actually was complaining about this to colleagues as soon as I noticed the change. As far as I can tell this is because the columns now have more than one possible field. In the case of agents imported from the LC name authority file, these records have a LC and a OCLC record identifier, and NACO and Local sources. I suggest the best solution is to ignore the other IDs besides the primary ID for the purposes of browse, search, faceting, etc. Pass.

3. Can confirm doesn't display in the PUI. Pass.

1. Link to ANW-1396

2. Pass.

3. Pass.

Matthew Neely

https://archivesspace.atlassian.net/browse/ANW-1419https://archivesspace.atlassian.net/browse/ANW-1422

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

Angela White

https://archivesspace.atlassian.net/browse/ANW-1428 https://archivesspace.atlassian.net/browse/ANW-1430

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

1. This ticket asks for the ability to download a partially completed spreadsheet for digital objects. I like this and would like this option for all spreadsheets, but I’m unsure what kind of effort this would require from our programmers.

2. This is an obvious bug that I think we should fix. The only issue is that there is a small configuration change that enables the search to be there in the Collection Organization tab at all, which might kick it to a lower priority.

3. I’ve verified this bug report and noticed that it is also true for Linked Records via Rights Statement. Pass with Trivial prioritization?

1. Pass, trivial

2. Pass

3. Pass, trivial

Althea Topek

https://archivesspace.atlassian.net/browse/ANW-1440https://archivesspace.atlassian.net/browse/ANW-1442

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

1. Pass

2. Where should this link go? To the other subject record?

3. An AS version would not be identical so there would need to be a plan for what information this report would actually produce. I think this would be redundant with custom reports.