DCO-DS

DCO-DS Scrum April 13, 2015

DCO-DS Scrum April 13, 2015

General Meeting Information

  • This Meeting
  • Previous Meeting
  • Next Meeting
  • Sprint Planning
  • Current Sprint
  • Current Backlog

Agenda

  • Around the room (5 minutes each MAX)
  • After Scrum - 30 minutes of discussion if needed

Attendance

  • Patrick
  • John
  • Stephan
  • Marshall
  • Momo
  • Apurva
  • Hao - running late

Ticket Information

  • t-shirt field
    • x-small - 1-2 hours
    • small - up-to 1 day
    • medium - up-to 1 week
    • large - 1-3 weeks
    • x-large - 3+ weeks

Action Items

  • Around the Room
  • What have you worked on since last

DCO-DS April 02-06 2015

DCO-DS Sprint Planning 02-06 April 2015

  • General Meeting Information
  • This Meeting
  • Previous Meeting
  • Next Meeting
  • New Sprint
  • Current Backlog

Agenda

  • DCO-DS
  • Sprint Planning

Attendance

  • Patrick
  • John
  • Stephan <= vacation
  • Marshall
  • Momo
  • Apurva
  • Hao
  • Peter <= "Use only as directed, only as needed..."

  • DCO-DS - Looking Forward

DCO Finished 5 year review of what's been done so far.

  • Did not include Engagement or DCO-DS as they started two years later
  • Next 5 year committee formed to look forward, three major things: 1) cross-community science a

DCO-DS Reporting Year Demo Script

Demonstrate from Sloan point of view

This first part is from the perspective of a funder, someone who wants to see updates on a particular grant.

We'll use the DCO Computer Cluster as an example, Grant: APS: 2013-03-01 (CIW)

  1. Go to the grant browser page “Community Portal” -> “Resources” -> “DCO Grant Browser”
  2. Find the grant, in this case APS: 2013-03-01
  3. I can see that there’s project updates for 2014, so clicking on the 2014 reporting year
  4. And on this grant summary report I see projects, field studies, and the DCO Computer Cluster under instrument
  5. Can select any of the

Functional Requirements Document DCO User Information Flow

Authors:Patrick West

Abstract:

The purpose of these functional requirements is to make sure that we request from the user information to be kept within the system for the user, any and all information the user entered is put into the right places, that there is an individual profile for the person if one does not already exist in the information portal, and that the user is granted any and all permission they need as a new user, and be subscribed to the DCO newsletter.

History

DateCreated ByLink
May 20, 2015
23:38:04
Patrick WestDownload
December 2, 2014
14:31:35
Patrick WestDownload
December 2, 2014
00:40:09
Patrick WestDownload
December 2, 2014
00:36:35
Patrick WestDownload
November 27, 2014
20:57:47
Patrick WestDownload
November 9, 2014
23:59:07
Patrick WestDownload

Related Projects:

DCO-DS LogoDeep Carbon Observatory Data Science (DCO-DS)
Principal Investigator: Peter Fox
Co Investigator: John S. Erickson and Jim Hendler
Description: Given this increasing data deluge, it is clear that each of the Directorates in the Deep Carbon Observatory face diverse data science and data management needs to fulfill both their decadal strategic objectives and their day-to-day tasks. This project will assess in detail the data science and data management needs for each DCO directorate and for the DCO as a whole, using a combination of informatics methods; use case development, requirements analysis, inventories and interviews.
Syndicate content