Steve: Difference between Nurax and Hyrax repos has to do with testing. Nurax is used for release testing, candidate code is uploaded to this domain. Reported issues and bugs are put into Nurax. This makes it clear which issues are for pending release, as opposed to general issues that folks place in Hyrax.
Might be good to normalize labels across Hyrax/Nurax repos.
Two labels for accessibility: blocker and concern.
Might also be good to have more specific labels: still a constrained number, but more detail about types of UI/UX issues
This group might be a good one to propose new labels.
We also need a framework for assigning labels consistently.
15min
Who are our users, and what are their goals? For image-based resources we have "photographers, catalogers, curators". What are roles/goals for users that are managing non-image-based resources (i.e., datasets, geo-resources, a/v)?
(Shaun will share some draft personas/roles from Figgy.)
Shaun/All
What kind of interest is there in general community personas?
HyBox personas were targeted at paper/document-based collections, but Hyku collapsed these distinctions in order to incorporate image-based.
Dave M. has talked about doing user research for the new version of Oregon Digital. Might be good to coordinate this with UXIG.
For Figgy, they need to determine whether the UI will be able to accomodate non-image materials, or if it will need a separate UI.
Regardless of transferability, knowing the process for creating them would also be helpful.
We should touch base with Hannah F. on HyBox personas, perhaps getting them into a format that's easier to manipulate.
15min
Pattern/template library for re-usable UI components. A 'go to' repository of code templates. Say if one were to create a new "cancel" button, or a modal window, or a text input, they could reference this shared repository for starter markup.
Adam/All
5min
Interest in organizing working group for usability testing
Adam/All
Action items
Start a list of proposed Github labels for UI/UX issues