Date
Attendees
Discussion items
- Generating and managing UX tickets
- Waffle?
- Nurax vs Hyrax
- How soon to spin up usability testing WG
- What to test? Review guidelines for establishing a WG.
- Documenting a UX style guide
- Create a dead simple style guide for starters. This will bring up a lot of questions regarding Bootstrap dependencies/versions/future.
- Create a shared repo of small HTML modules (ie. form input element, button, label, modals, radio buttons, multi-select dropdown, etc.)
- Ideas on how to get buy-in from our managers for Samvera UX community time.
Notes
Good to put faces to names, meet UX community
We have established some momentum
UX advisors Github team
Interest in documentation
Jeremy + LaRita - Notre Dame’s workflows are not presently focusing on UX/UI
Lynette - Interested in a distinction between general and specialized UX issues.
Gary Geisler did mockups for collections extensions, but there was not user testing. Would be good to follow through on this.
Usability testing - good to have an ongoing conversation, UX efforts throughout
UI developers - trying to understand how broader UX research relates to coding work
Collections extensions - mockups were an entire working group, lots of feedback for Gary (who did design work)
Hyku had a lot of user feedback - some of this was carried into Hyrax.
Perhaps individual pages are getting improved, but perspective is not holistic.
Blacklight generated views and Samvera views are sometimes inconsistent.
Northwestern - has not just a style guide, but also template and SaaS modules from marketing dept.
Maybe this group could create a repository of shared components (past - would help those working from back end.
Currently, Hyrax is on Bootstrap 3x. How strong should the dependency be? Can we use a timeline to dictate this?
Consistency among subcomponents would help overall consistency in UI.
Blacklight 7 release is being held for Bootstrap 4 release.
What do we want to solve? Workflow issues (UX advisors group on Github)
UX group can be disorienting. Current process not amenable to thorough UX feedback.
Decisions about what needs testing (DURT?) vs. low-hanging fruit that just needs design attention.
Testing - make sure that we are addressing defaults.