...
Provide a bulleted list of deliverables.
Suggested schedule
Schedule
This is a community-driven project. Schedules are subject to change as people are available. Open VIVO is a demonstration schedule for first appearance at the Force16 conference in Portland, Sunday April 17-Tuesday April 19. To demonstrate Open VIVO at the conference, the schedule below is proposed.
Requirements are in place. Additional features could be added if time and resources permit, and if the feature(s) are consistent with the nature and purpose of Open VIVO.
| Tasks | Duration | Start | End | Status |
Develop charter, requirements, resource feasibility, solicit participation, | 3 weeks | 2016-01-24 | 2016-02-13 | All complete except infrastructure, which is on track |
Domain name, infrastructure hosting, stand up platform, three tier build, |
| 2016-02-02 | 2016-3-06 | Domain openvivo.org obtained. Infrastructure provider identified. On track. |
Develop charter | 1.5 weeks | 2015-XX-XX | |||||
Solicit members and schedule first meeting | 1 week | 2015-XX-XX||||||
Develop action items, assign to team members | 2 4 weeks | 2015-XX-XX | |||||
Accomplish deliverables, preliminary review | 3 weeks | 2015-XX-XX | |||||
Acceptance testing, refinement, communications, presentation materials | 2 weeks | 2015-04-03 | 2015-04-15 | ||||
Workshops and Visualizations Hackathon at Force 11 Conference | 1 day | 2016-04-17 | 2016-04-17 | ||||
| Additional Force11 demonstrations, continuous update of open VIVO from Figshare and ORCiD, continuous export of data to GitHub, continuous import of data to Iowa repositories and tools. | 2 days | 2016-04-18 | 2016-04-19 | Revise deliverables, final review | 2 weeks | 2015-XX-XX
Members
Name and Affiliation - task force lead
...