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.
What does such a wide variety of Samvera code have in common, besides serving the digital repository needs of the Library/cultural heritage community?
What does it mean to be a “Samvera application”?
What if general criteria existed which Samverians (developers, product owners, managers, designers), could reference when designing and developing an app or module?
The UX Interest Group proposes crafting a set of Design Principles, which reflect the values and goals of the Samvera Community. In addition, perhaps these Design Principles could:
Serve as a guide for application design before development begins.
For example, when creating wire-frames for a new feature, does the wire-framed content meet Design Principles standards?
Act as a reference point for applications in active development.
Be a tool to evaluate existing Samvera applications, such as:
Identify areas which might fall short of meeting Samvera Design Principles, thus becoming opportunities for improvement.
Interpreting these Principles from Different Audience Perspectives
Do we consider all or specific audiences for these principles? Let’s debate!
Backend Developers (current & future)
Front End Developers (current & future)
Administrative Users
End Users / Patrons (students, faculty, research, general public, etc.)
Samvera is a vibrant and welcoming community of information and technology professionals who share challenges, build expertise, and create sustainable, best-in-class solutions, making the world’s digital collections accessible now and into the future.
Human-Centered. Efficient. Unified. Sustainable. Ethical.
Inclusive & Equitable | Accessible & Universal | Engaging & Unambiguous |
---|---|---|
|
For Developers:
|
|
Modular while functioning as a whole | Minimal (in design & latency) | Intuitive & Predictable | Controlled Flexibility |
---|---|---|---|
|
|
|
|
Standards & Best-Practices | Consistent behavior patterns & functionality | Clearly documented (for designers and users) |
---|---|---|
|
|
|
Mindful of Trends | Maintenance Demands Match Resourcing Realities | Forward Thinking |
---|---|---|
|
|
|
Transparent | Mindful of Unintended Favouritism | Digital Safety & Wellbeing |
---|---|---|
|
|
|
Source:
https://principles.design/examples/the-ten-principles-of-inclusive-design
University of Virginia Library Design Principles
…
People/Members:
UX Interest Group
@Christina Chortaria
Norm Orstad
Dananji Withana
April Rieger