Location: https://oregonstate.webex.com/meet/vantuylsoregonstate.edu
...
Note that following current best practices within HydraSamvera, Working and Interest groups should use an existing channel unless and until it becomes clear that a dedicated channel is needed. This section should specify which existing channel(s) will be used: e.g., hydrasamvera-tech, hydrasamvera-partners, hydrasamvera-community@googlegroups.com. When using a shared channel, individual working groups should start the subject line with their name in []s, such as [archives] for the Archives Working Group. If and when a dedicated channel is needed, the new channel should be well publicized and open to any interested subscribers/participants in the community.
...
The call for participation will be sent to hydra-partners@googlegroups.com, hydra-samvera-community@googlegroups.com, and hydrasamvera-tech@googlegroups.com.
Regular meetings will be held on Tuesdays at 10AM Pacific at https://oregonstate.webex.com/meet/vantuylsoregonstate.edu
Meetings, meeting minutes, deliverables, and milestones will be announced on hydra-partners@googlegroups.com, hydrasamvera-community@googlegroups.com, and hydrasamvera-tech@googlegroups.com.
We will set up a dedicated (not private, but topic-specific) Slack channel in the Project Hydra Samvera team for asynchronous communication (#analytics). This should help us keep discussions focused and on topic.
Meeting notes recording action items and provisional decisions will be in the Hydra Samvera wiki.
Members
Note that Working Groups must have participants from three different Partners. All members of a working group producing software must be licensed Hydra contributors Samvera contributors covered by the appropriate CLAs. Other types of contributions such as requirements, design, best practices, documentation, etc. - do not require CLAs but particpants should accept that the materials to which they contribute may be released under a Creative Commons Attribution 4.0 International License..
- Steve Van Tuyl, facilitator (Oregon State University)*
- Ellen Ramsey (University of Virginia)*
- Hannah Frost (Stanford University)*
- Gabriela Montoya (University of California, San Diego)*
- Chris Awre University of Hull)*
- James Tuttle (Duke University)*
- Nabeela Jaffer (University of Michigan)*
- nik.dragovic (Emory University)
- cam156 (Pennsylvania State University)*
- Hui Zhang (Oregon State University)*
- Weiwei Shi (University of Alberta)*
- Leah (University of Alberta)*
- sally.rumsey (University of Oxford)
- Don Brower (University of Notre Dame)*
- Aaron Collier (California State University)
- Jonathan McGlone (University of Michigan)
Resources
- Hyrax Analytics User Stories
- Hyrax Analytics Use Cases
- Hyrax Analytics Prioritization Spreadsheet
- Hyrax Analytics Requirements Tables
- Definitions
- Documentation Expectations
- Milestone 1 Prioritization Spreadsheet
- Notes from initial assessment for design
- Final UI Mockups [zip]
Meeting Notes
- Hyrax Analytics Working Group Meeting - Friday, June 2, 2017 -06-02(Kick-off)
- Hyrax Analytics Working Group Meeting - Tuesday June 13, 2017
- Hyrax Analytics Working Group Meeting - Tuesday June 20, 2017
- Hyrax Analytics Working Group Meeting - Tuesday June 27, 2017
- Hyrax Analytics Working Group Meeting - Tuesday July 11, 2017
- Hyrax Analytics Working Group Meeting - Tuesday July 25, 2017
- Hyrax Analytics Working Group Meeting - Tuesday August 1, 2017
- Hyrax Analytics Working Group Meeting - Tuesday August 15, 2017
- Hyrax Analytics Working Group Meeting - Tuesday August 22, 2017
- Hyrax Analytics Working Group Meeting - Tuesday September 5, 2017
- Hyrax Analytics Working Group Meeting - Tuesday September 12, 2017
- Hyrax Analytics Working Group Meeting - Tuesday September 19, 2017
- Hyrax Analytics Working Group Meeting - Tuesday October 10, 2017
- Hyrax Analytics Working Group Meeting - Tuesday October 17, 2017
- Hyrax Analytics Working Group Meeting - Tuesday October 31, 2017
- Hyrax Analytics Working Group Meeting - Tuesday November 14, 2017
- Hyrax Analytics Working Group Meeting - Tuesday December 5, 2017
- Hyrax Analytics Working Group Meeting - Tuesday December 19, 2017