2021-11-30 Meeting notes
Nov 30, 2021 12 PM ET/ 11 AM CT/ 10 AM MT/ 9 AM PT
Call-in Information:
Join Zoom Meeting
https://lyrasis.zoom.us/j/88159748924?pwd=a2R1U2kvY3ZhYk1TM2hXdVRXOVR4dz09
Meeting ID: 881 5974 8924
Passcode: 301177
One tap mobile
+13126266799,,88159748924#,,,,*301177# US (Chicago)
+19292056099,,88159748924#,,,,*301177# US (New York)
Dial by your location
+1 929 205 6099 US (New York)
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago)
+1 669 900 6833 US (San Jose)
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
888 475 4499 US Toll-free 877 853 5257 US Toll-free
Meeting ID: 881 5974 8924
Passcode: 301177
Find your local number: https://lyrasis.zoom.us/u/kbKeFBTzm
Participants
Joanne Archer
Elizabeth Beckman
Kate Blalack
Johanna Carll
Kellen Carpenter
Regina Carra (Vice-Chair)
Christine Di Bella (ex-officio)
Bailey Hoffner
Margaret Turman Kidd
Randy Kuehn (ex-officio) (regrets)
Dan Michelson (Chair)
Patrick Milhoan
Matthew Neely
Cory Nimer
Sarah Ponichtera (regrets)
Suzanne Reller
Joshua Shaw
Althea Topek
Angela White
Goals
Update members on UAC activities including activities of sub-teams
Discussion: Dev/Pri Subteam
Notetaker
@Margaret Kidd
Time | Item | Presenter/Facilitator | Notes |
---|---|---|---|
5 mins | Roll Call/Icebreaker | @Daniel Michelson |
|
5 mins | UAC Updates | @Daniel Michelson |
|
5 mins | Program Update | @Christine Di Bella |
|
10 mins | Sub-team Reports |
|
|
| Development Prioritization | @Angela White |
|
| Users Documentation | @Johanna Carll |
|
| Testing | @Joshua Shaw |
|
| Usability | @Joanne Archer (Unlicensed) |
|
| Member Engagement | @Regina Carra |
|
30 mins | Discussion: Dev/Pri | @Angela White | Dev-Pri and what we do? Subteam tasks – Look at Jira tickets for bug fixes and new feature developments. Helps to shape what ASpace looks like in the years to come. Consider becoming part of the subteam!
Discussion – How to seek community feedback about specific issues that come up in Jira tickets? For example: ANW-1345: Location Record Barcodes are not UniqueReady for Implementation, a situation where barcodes should really be unique, but changing this could have serious repercussions for users Challenge – how do you weigh perspectives/use cases when considering potential changes to the application? Ideas for engagement: Community Forum – Does an annual forum give us the broad range of perspective? Make sure that user documentation has accurate information – in regards to example, that the user documentation says that barcodes do not need to be unique |
5 mins | New Business | @Daniel Michelson |
|
| Next Meeting | @Daniel Michelson |
|