Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

...

Goals

  • Determine where to document and prioritize UX issues.

...

TimeItemWhoNotes
15minGithub labels/teams/issuesJenn/Steve/All
  • A few UI/UX tags are in use. Some notify advisors, some don't. Some tags are improperly deployed.
  • Some links to issues:
  • 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.
  • Nurax public demo: https://nurax.curationexperts.com/
  • 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
15minPattern/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
5minInterest in organizing working group for usability testingAdam/All

Action items

  •  Start a list of proposed Github labels for UI/UX issues