Versions Compared

Key

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

...

Topic/Who

Tickets

Notes

Decision


Maggie Hughes

  1. https://archivesspace.atlassian.net/browse/ANW-281

  2. https://archivesspace.atlassian.net/browse/ANW-336

  3. https://archivesspace.atlassian.net/browse/ANW-795

  1.  


  1.  

Randy Kuehn

  1.  https://archivesspace.atlassian.net/browse/ANW-960

  2. https://archivesspace.atlassian.net/browse/ANW-999

  3. https://archivesspace.atlassian.net/browse/ANW-1080

  1.  

  1.  

Angela White

  1.  https://archivesspace.atlassian.net/browse/ANW-1062

  2. https://archivesspace.atlassian.net/browse/ANW-942

  3. https://archivesspace.atlassian.net/browse/ANW-1096

  1.  

  1.  

Daniel Michelson

  1.  https://archivesspace.atlassian.net/browse/ANW-1000

  2. https://archivesspace.atlassian.net/browse/ANW-966

  3. https://archivesspace.atlassian.net/browse/ANW-1064

  4. https://archivesspace.atlassian.net/browse/ANW-271

  5.  

  6.  

1 and 2. Both of these tickets concern spellcheck, a highly popular feature that exists only in a very limited way in ArchivesSpace. The current functionality is to utilize the web browser’s built-in spellcheck.

However, as the second ticket points out, ArchivesSpace does not tell the browser to check spelling in the content field of resource record notes. Correcting that should be simple and I recommend passing as is.

The first ticket is looking for a completely new function, being able to search the entire database or a single resource record to detect spelling errors. At an earlier Dev/Pri meeting we were leaning towards passing this for development as a plugin.

3. This ticket is asking for the order of elements in the collection overview page of the PUI to be customizable via the config file. This would be a nice feature. My only concern is whether this should be dealt with as part of a larger conversation about eliminating (or making optional) the “Additional Description” section.

4. This can be closed as a duplicate of the previous ticket.

Matthew Neely

  1.  https://archivesspace.atlassian.net/browse/ANW-328

  2. https://archivesspace.atlassian.net/browse/ANW-1090

  3. https://archivesspace.atlassian.net/browse/ANW-940

  1.  

  1.  

Althea Topek

  1.  https://archivesspace.atlassian.net/browse/ANW-1092

  2. https://archivesspace.atlassian.net/browse/ANW-1023

  3. https://archivesspace.atlassian.net/browse/ANW-1041

  1.  Agents, Subjects, and Top Containers are the only functions that allow Browse and Create. If a Create option was added to Related Accession, should it also be added to: related resources, classification, and location?

  2. I don’t think Extent Dimension should be a controlled value but there should be a way to set Width as a default

  3. Project for usability subteam?

  1.  

saron tran

  1.  https://archivesspace.atlassian.net/browse/ANW-1059

  2. https://archivesspace.atlassian.net/browse/ANW-1049

  3. https://archivesspace.atlassian.net/browse/ANW-715

  1.  

  1.  

...