Info | ||
---|---|---|
| ||
The Open VIVO task force is active, and looking for additional help in Graphics/UI, Java development and RDF generation and management. If you'd like to help, please contact Mike Conlon or Graham Triggs |
Context
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.
Objectives
Provide a bulleted list of the Task Force objectives.
Deliverables
Open VIVO will be a demonstration of VIVO at the Force11 Conference in Portland, April 17-19. The demonstration is expected to run through the VIVO Conference in August
Objectives
- Provide a hosted Open VIVO platform that anyone with an ORCiD can join
- Develop attribution ontology for use with Open VIVO
- Import content from GRID (orgs), CrossRef (journals), Dates, Concepts. Import data for attendees from Figshare. Import content for users from ORCID.
- Provide a capability for a user to enter a DOI and the contribution they made to the work, and have that work added to Open VIVO
- Export all the data nightly to GitHub under FAIR data principles for reuse by the community.
- Demonstrate the system and support its use throughout the demonstration period.
Many elements of Open VIVO will find their way into future releases of VIVO. Sign on procedures, RDF data, attribution ontology, interactive addition of works via DOI and others will be added to VIVO for all sites to use. An export utility is planned for extracted data from Open VIVO regarding a particular institution. Using this tool, local data stewards will be able to extract data from Open VIVO pertaining to their organization, and add it to their local VIVOProvide a bulleted list of deliverables.
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.
...
Tasks | Duration | Start | End | Status/Notes |
Develop charter, requirements, resource feasibility, solicit participation, approval of steering, project infrastructure, launch sub projects | 3 weeks | 2016-01-24 | 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 | 4 weeks | 2016-02-02 | 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 | 6 days | TBA | 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 | Muhammad Javed will work with Mike Conlon on Journals. David Eichmann will work with Mike Conlon on Organizations. Alexandre Rademaker will also help. |
Figshare Ingest | 4 weeks | 2016-02-13 | 2016-03-13 | Ted Lawless will work with Mike Conlon on this. |
Identify and represent attribution/contribution | 4 weeks | 2016-02-13 | 2016-03-13 | Melissa Haendel, Kristi Holmes, Alexandre Rademaker will work 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, begin data export | 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. |
Harvest data from Open VIVO to CTSAsearch | 2 weeks | 2015-03-20 | 2015-04-02 | Dave Eichmann will work on this |
Final acceptance testing, refinement, communications, presentation materials | 2 weeks | 2015-04-03 | 2015-04-15 | Stop adding things. Keep fixing things. Keep smoothing things. |
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 |
Members
Contributors
Mike Conlon Name and Affiliation - task force lead
Name and Affiliation - facilitator
Name and Affiliation - member
Name and Affiliation - member
, project manager, RDF production
Graham Triggs technical lead, platform, DOI ingest, hosting, platform support
Ted Lawless RDF production
Muhammad Javed RDF for journals
Dave Eichmann RDF for orgs, reuse of data in CTSAsearch
Alexandre Rademaker Ontology work
Melissa Haendel Ontology work
Kristi Holmes Attribution ontology
Jim Blake ORCiD sign on, profile creation, DOI from ORCiD
TBA Graphic design/UIothers to be solicited from the VIVO Community
Meeting Times
TBD
Communication Channels
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
The status elements above will be updated each week and via VIVO Updates
- Notes of meetings will appear below
- vivo-tech and vivo-community will be used to support project communication
Agendas and Notes
Use standard meeting agenda and notes format (see VIVO wiki Task Force Agenda Template (click --> here for example). Children Display