Date
11:30 ET / 10:30 CT / 9:30 MT / 8:30 PT
Call-info
Join from PC, Mac, Linux, iOS or Android using the link provided in the meeting invitation.
Or iPhone one-tap: US: +13126266799 (95479392806#) or +19292056099 (95479392806#)
Or Telephone：
Dial(for higher quality, dial a number based on your current location):
+1 312 626 6799 US (Chicago)
+1 929 205 6099 US (New York)
+1 301 715 8592 US (Germantown)
+1 346 248 7799 US (Houston)
+1 669 900 6833 US (San Jose)
+1 253 215 8782 US (Tacoma)
877 853 5257 US Toll-free
888 475 4499 US Toll-free
Meeting ID: 954 7939 2806
International numbers available: https://lyrasis.zoom.us/u/ahUXQvjfH
Participants
Goals
Prioritize new and awaiting more info tickets
Links
Kanban boards:
New bug reports: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=15
New feature requests: https://archivesspace.atlassian.net/secure/RapidBoard.jspa?rapidView=16
Link to ArchivesSpace sandbox: http://test.archivesspace.org/
Discussion topics
Topic/Who | Tickets | Notes | Decision |
|---|---|---|---|
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. | |||
| |||