Versions Compared

Key

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

Samvera community packages run the gamut from Ruby gems, to generators, to Rails and Elixir applications, Node modules, JavaScript UI components and more. Thinking about a meaningful purpose the UX Interest Group could serve the community in 2021, the following questions have surfaced.

...

  • Backend Developers (current & future)

  • Front End Developers (current & future)

  • Administrative Users

  • End Users / Patrons (students, faculty, research, general public, etc.)

***We want to put in questions with each principle we settle on to help people think thru how they are/arent' reaching those principles. **

Samvera Design Principles (working draft)

...

  • Transparent

    • Q: Is the app’s codebase open source (for ease of Adoption & Integration)

    • Q: Is the app Community driven/managed

    • Q: Does the app have a visible public policy around User Data Collection and Analysis?

  • Mindful of trends and unintended favouritism thru integration choices (ie. FB, Google+ integrations)

    • Q: Does the app rely heavily on 3rd party modules (FB/Google/etc)?

  • Safety

    • Q: Does the app prioritize security in code

  • Ease of Adoption for all communities

  • Prioritise Design choices that favour all communities.

Drafting notes below

Human-Centered

Points: 

  • Inclusive

  • Accessible, Accommodating

    • Be approachable, uncluttered and give people room to maneuver.

    • Make sure that your website is unobtrusive and can be accessed by different devices of all shapes and sizes.maintain device independence

  • Universal

  • Equitable

    • Be welcoming, don’t discriminate.

    • Engage with people.

    • Aesthetics matter.

  • Be welcoming, don’t discriminate, and engage with people. Create different user experiences and make certain they have equally valuable outcomes. 

Flexible:

  • 

Provide options.

  • Modular Application development

  • Think who, how, why, what, where & when people will be using your website.

  • Make sure there is choice for diverse users and .

Straightforward:

  • Be obvious and not ambiguous.

  • Make sure your website’s features add value, not complexity.

  • Good design is as little design as possible.

Title: Efficient

Points: 

  • Minimal latency

  • Easy to understand and follow

  • Make it easy for users to avoid and correct errors 

Good Documentation

Development happens with efficiency of entire application in mind, not individual needs

Perceptible:

  • 

Don’t assume anything.

  • Make sure the application’s purpose is clear, and its content, structure and sequence are meaningful.

Informative:

  • Be timely, predictable, uncomplicated and precise.

 (breadcrumbs & buttons placement, etc. Best practice wireframes)

  • Make sure people know where they are in your application/component. navigation

  • Provide different ways for them to find what they’re looking for.

  • Modular

Preventative:

  • Intuitive to use, minimize need to have instructions

  • Provide easy to follow instructions and gently guide users in interacting with your application.

  • Help users minimize errors when submitting data, through well considered form design.

Tolerant (with Feedback):

  • Open to change (should we go here with principles)

  • 

Handle errors respectfully and indicate precisely what the error is, where it is and how to fix it.

  • Remember to let people know the outcome.

Effortless:

  • Balance flexibility with friction.

  • 

Don’t make demands or place restrictions on your users.

  • People should not have to work or think hard to find what they want in your application (intuitive).

  • Ensure the app can be used efficiently and effectively.

Title: Sustainable

One of the main reasons community uses Samvera products is sustainablility.

Points: 

  • Maintenance demands should match organizational commitment to a resource.

  • Design (visual, technical, etc.) should be forward-looking, taking into account likely future scenarios, and avoid short-term trends.

  • Project design should consider costs, both human (such as labor for creation and upkeep) and financial.

Security of using Open Source

Consistent:

  • Follow standards, guidelines, conventions and best practices.

  • Provide a familiar environment with memorable functionality.

Title: Unified 

Points: 

  • Be consistent, not uniform

  • Follow standards, guidelines, conventions, and best practices

  • Consistent behavior patterns and functionality

...

Source: Contribution Acknowledgements for the Samvera Design Principles:

Source:

...

  • University of Virginia Library Design Principles

People/Members: