2020-09-01 Meeting notes

Date

Sep 1, 2020 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

  • @Maggie Hughes - regrets

  • @Randy Kuehn

  • @Daniel Michelson

  • @Matthew Neely

  • @Althea Topek

  • @saron tran

  • Angela White

  • @Mark Cooper (Unlicensed)

  • @Lora Woodford

  • @Christine Di Bella

Goals

  • Prioritize new and awaiting more info tickets

Kanban boards:

Link to ArchivesSpace sandbox: http://test.archivesspace.org/

Discussion topics

Topic/Who

Tickets

Notes

Decision

Topic/Who

Tickets

Notes

Decision

  • Introductions

  • Code of conduct

  • Dev Pri meeting structure

  • Advice on approaching tickets

  • How to prepare for upcoming meetings

  • What should you to do after meetings

  • Questions

 

https://archivesspace.atlassian.net/wiki/x/HoBLAg

 

 

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

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

  1.  

  2.  

  1.  

  2.  

@Maggie Hughes

  1.  

  2.  

  1.  

  2.  

@Randy Kuehn

  1. It looks like this CSV export/import might be a good plugin candidate
    Recommend: Perhaps we could push the location import/update/export to Community Development

  2. I think a reset default preferences option would be a useful UI upgrade
    Recommend: If Usability doesn't need to weigh in, either push to Development or Community Development

  1. Passed for community developer as plugin.

  2. Passed for community developer to add to each level of preferences.

@Daniel Michelson

  1. The submitter is correct that it is inconsistent for the PUI to omit date labels for creation dates. I do not see any downside to this proposal and recommend moving it forward for implementation

  2. I agree that this is a desirable feature and incorporating it into the global/repository/user preferences system would be logical from the user perspective (as suggested in the broader SIEWG recommendations referred to in the comments). Aside from the Finding Aid Data section of resource records, the ticket does not specify which parts of which records or sub-records should be able to be hidden. That would need to be determined before moving the ticket forward.

  1. Push to development

  2. Dev Pri will be investigating the possibility this type of feature

Action items