Tuesday August 15, 2017 - 10:00 AM Pacific Time
- Note Taker: Hui
- Analytics Requirements Tables (DRAFT) - have a lot of questions that arose in the document - need to walk through these for clarification
- "Access" in the comment column: It means access to the collection, not aggregate of the views of works in that collection.
- There is an opinion that we should make the assumption more flexible, for example the access to collection could make sense in some cases when it is an aggregation of work views or can drill down to views/downloads by work.
- The statistics should preserved at the most granular level: like at each file, work, and collection level (instead of merely aggregating).
- Don, Carolyn volunteer to work with Steve to finalize the Requirements by next meeting.
- Definitions document - volunteers to work on and clarify definitions
- It is in good shape.
- Fileset: should Analytics provide granularity at bitstream level (e.g., images with different resolutions)? The challenge is that fileset can be modeled differently by different users (e.g., libraries or archives) or single assumption of use case may not work.
- It is in the phase now to collect broader feedbacks from the community.
- Need a volunteer to start drafting documentation expectations (Leah)
- Design and UI Update
- Set deadline for Requirements, Definitions, and Documentation Expectations to be sent to Community for feedback
- Will decide in the next meeting, but the intended date will be by the end of August (in two weeks)!
- Mike Giarlo will participate the conversation to finalize the requirement tables after we get the community feedbacks.
- Reference Documents:
- 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)