Tuesday September 5, 2017 - 10:00 AM Pacific Time
- Note Taker: Gabriela A. Montoya
- Review of feedback on Requirements Table and Definitions
- It should be noted that we didn't get a lot of feedback. Most embedded comments were internal.
- Julie Rudder had a question about visibility (internal vs. world-wide access).
- Sally Ramsey thought that in-link and out-link reporting would be useful.
- Oxford is interested in seeing where people are coming from (Facebook, Twitter), but we have not adequately captured this.
- Outlinks should be added to a later milestone, but incoming links is pretty standard.
- Decision: Incoming links get set to Milestone 1 and outgoing links to Milestone 2.
- Chris Awre asked if this group is aware of a CLIR/DLF initiative to explore the use of the IRUS statistics service across a selection of CLIR members (this is a UK-based service). IRUS generates COUNTER-compliant statistics across repositories, which most UK sites make use of. CLIR is exploring whether this is of interest to the US.
- UvA ia participating but just started looking into it last week.
- IRUS-USA: "The portal enables you to access COUNTER compliant and comparable usage statistics."
Demo site: https://jusp.jisc.ac.uk/irus-usa/
- Per Chris: IRUS doesn't go as far as the use cases and functionality described in the group's work, as its focus is on gathering statistics outside the repository itself and providing reporting back in through its portal, but it is easy to set up (we use a gem, irus-analytics (https://github.com/uohull/irus_analytics) that our developer wrote a couple of years ago).
- With limited feedback we are ready to think about next steps with regards to this document:
- Start to discuss for Milestone 1 whether we need more clarity and to engage with design folks.
- Documentation subgroup needed
Suggest that 2-3 people put in an hour or so over the next week to outline documentation needs?
- Hannah and Hui think that this isn't super pressing. They recommend that we hold off on this for now.
- Could potentially be somewhat of a guideline and something that we should take into account here.
Ellen will demo once they get COUNTER up and running, but the Ruby gem needs to be fixed first.
- RAMP is a service for counting downloads and has the potential to aggregate metrics across institutions, but is is not necessarily related to COUNTER.
Making Hyrax analytics COUNTER compliant: where does this fit in terms of our development. It seems like we don't know enough yet. We need to do some investigation to better understand what that means. As a minimum we should make sure we measure things in the same way in case we later want to be COUNTER compliant.
We may want to follow the SUSHI protocol. We need another subgroup to dig in on what exactly we mean by SUSHI, IRUS, RAMP compliant.
- Decision: Nik Dragovic Ellen Ramsey will form the COUNTER subgroup with Steve.
- Next Steps:
- Documentation: steve van tuyl will contact Leah to share what Alberta has done.
- UI design: steve van tuyl will contact Gary.
- COUNTER subgroup will get together over the next two weeks to pull info. together.
- Milestone ranking: steve van tuyl create a spreadsheet for us to rank Milestone 1 (low, med, high).
- Example of what we're trying to build at this stage: Use Cases for Display Sets in Hydra
- Example of what we're trying to arrive at: Requirements - Display Sets
- HAWG Prioritization Spreadsheet
- HAWG Landing and Charter Page
- HAWG Use Cases
- HAWG Requirements Tables (DRAFT)