Provide a brief description of why the Task Force is being proposed. Include sufficient background information to allow the reader to understand how the work fits into the current context of the current activities of the VIVO project. Only 2-3 bullet points or sentences are necessary.
Provide a bulleted list of the Task Force objectives.
Provide a bulleted list of deliverables.
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.
Develop charter, requirements, resource feasibility, solicit participation, approval of steering, project infrastructure, launch sub projects
|2016-02-13||All complete except infrastructure. Mike Conlon working on this. On track.|
Domain name, infrastructure hosting, stand up platform, three tier build, branding
|2016-3-06||Domain openvivo.org obtained. Infrastructure provider identified. Graham Triggs working on this. On track.|
ORCiD authentication, Profile creation, ORCiD hook for DOI
|TBA||Jim Blake will work on this. On track.|
|RDF generation for Journals (CrossRef) and Organizations (Grid)||4 weeks||2016-02-13||2016-03-13|
|Figshare Ingest||4 weeks||2016-02-13||2016-03-13||Ted Lawless will work with Mike Conlon on this.|
|Publication Ingest from CrossRef with Attribution from user-entered DOI||5 weeks||2016-02-07||2016-03-12||Graham Triggs is working on this. Prompt, fetch, confirm working. On track.|
|Full assembly – all features in place. Begin testing, begin remediation||1 week||2016-03-13||2016-03-19||Tight coordination among team members needed here.|
|Remediation or additional features||2 weeks||2016-03-20||2016-04-02||If things need to be fixed, fix them. If things need to be smoothed, smooth them. If things can be added, add them.|
Final acceptance testing, refinement, communications, presentation materials
Workshops and Visualizations Hackathon at Force 11 Conference
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.
Name and Affiliation - task force lead
Name and Affiliation - facilitator
Name and Affiliation - member
Name and Affiliation - member
others to be solicited from the VIVO Community
Distribute proposed charter and solicit participation from community via appropriate mailing list
Announce task force creation and progress on relevant Working Group calls.
Create a page in the VIVO wiki (wiki.duraspace.org), with child pages for agenda, notes, and additional information
Agendas and Notes
Solicit agenda items from task force members 3 days before meeting
Prepare agenda and distribute no less than 24 hours before meeting
Use standard meeting agenda and notes format (see VIVO wiki Task Force Agenda Template (click --> here for example).