...
- Start a document that has definitions - Looking for volunteer Don Brower
- By next week there should be a draft set of definitions - Everyone
- Work towards prioritizing the rest of the requirements (do this based by the number of votes) - Steve Van Tuyl
- Propose categories of documentation and accompanying elements for the group to review nex technical next week (code, infrastructure, design, and user documentation) & User facing documentation - Leah
Notes:
- Analytics Requirements Tables (DRAFT)
- Using the Display Set model for the document
- All of the items that scored 7,8, or 9 or things that are important for each milestone
- Description needs to be added
- Should answer the questions in the comments before we share more broadly
- Need to define top level terms before sharing
- Call out items already implemented in Hyrax
- When we share the list we should ask for examples of how everyone has already made
- Need to scope the work being done by the working group
- Ask focused questions at the top of the list
- We are worried about cricket and then complaints when something is completed
- Don Brower has implemented a small analytics report in their implementation
- Need to include many examples of the reports, since that will influence the design of the work
- Documentation What are the standards?
- code documenting
- design documenting
- user documents
- what documentation do we need to have in place when we close milestone 1? What is required for design documentation?
- Planning for prioritization of Milestone 2 and 3
- This is what we need to do next: Prioritize the rest of the requirements in the list so we can see if anything is missing
- Start working on design, which will include report types
- Doing this based on the straight numbering
...