...
https://oregonstate.webex.com/meet/vantuylsoregonstate.edu
Recording of the Meeting:
Participants:
- Steve Van Tuyl (Oregon State Univ.)
- Hui Hui (Oregon State Univ.)
- cam156 (PSU)
- nik.dragovic (Emory University)
- lfarrell (University of North Carolina)
- Don Brower (Notre Dame)
Agenda:
- Talk with Gary Geisler about design mockups
- Checkin on COUNTER
- Checkin on statistics aggregation
- Steve made this - what do we think? https://docs.google.com/drawings/d/1eKkSeeKmwx6c64QrYwJf5Jw27Yfee-tX0AOa9znjhI4/edit
...
- Gary will continue to work on the UI mockups as he has time
- Steve will ping the collection extension group to see how analytics for collections within collections should aggregate.
- All should share around the initial designs with their institutions.
Notes:
UI Mockups with Gary
- Main goal to see the direction that is being proposed
- Not the items on the correct track and the items that are not in the right direction
...
Drum up support for working on the analytics development effort at samvera connect. Want to start working oworking on it in January 2018
Counter Update - Go with the minimum requirements to be counter compliant. Need to be consistent with how counter defines them. Counter is a standard used by vendors, which is outside of the open source OA comment experience. Allows us to compare the content with computers and bench marking repositories against other institution repositories. IRIS use project - benchmarking across UK repositories. You can install a tool (how does that work in Hyrax). One option would be to build in creating counter reports, but that was out of scope. Ensure the data can be counter compliant. Added definitions to the doc for counter reports. People can then aggregate the data out for counter at a future date.
- Why is there no OAI PMH compliance? Not part of this working group but others in the samvera community are looking at it.
Agregation:
Works & Collections only have page views
Files have works and downloads
Work level stats we report the views and the downloads for all child works and files
We are not certain about how the aggregation should work for views on a hierarchical work. The current definition is that you take the sum of all the views on works and files in the work
For collection we do not roll up the data to the collection. The views of the collection do not contain views of the works.
- People are interested as the collection as an object
- How many people have come to the digital exhibit
May want the aggregated information on all the things in the collection
Collections aggregate only child views from child collections
Downloads include all items, so only showing views for the collection may be counter intuitive
No one on the call has the use case for nested collection so we are uncertain how the collections in collections get aggregated.
Do not include the work counts in the collection counts since the works can be included in many collections.
Document how aggregation is happening and make that available to the user
Allow for either configuration or making it modifiable for the users.