You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 25 Next »

Active

The Open VIVO task force is active, and looking for additional help. If you'd like to help, please contact Mike Conlon or Graham Triggs

 

Context

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. More detail can be found in the Overview on Google Docs.

 

Objectives

  1. Produce the OpenVIVO system in time for demonstration at Force16
  2. Promote the system at Force16 and beyond
  3. Identify desirable future features
  4. Identify sustainability model

Features

  1. Demonstration of a hosted VIVO that anyone can join
  2. Sign on via an ORCiD identifier and password
  3. Automatic ingest of publications from ORCiD
  4. Ingest of material from the Force16 collection at Figshare (extensible to any collection on Figshare)
  5. Real-time addition of publications to a faculty profile by specifying a DOI or PubMed ID
  6. Standard RDF for journals, dates, and organizations
  7. Use of FAST as a standard vocabulary for research areas
  8. Publication of Open VIVO data to GitHub
  9. Consumption of Open VIVO data in CTSA Search
  10. Demonstration of a controlled vocabulary for attribution  and contribution to scholarly works

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 VIVO.

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.

Items in Green are sub projects that proceed in parallel.  Items in Red are major deadlines.  Other items are in Black.

 

TasksDurationStartEndStatus/Notes

Develop charter, requirements, resource feasibility, solicit participation, approval of steering, project infrastructure, launch sub projects

3 weeks

2016-01-24

2016-02-13Done. All in place. See Open VIVO Google Drive folder https://goo.gl/ofspSz

Domain name, infrastructure hosting, branding/theme, stand up platform, three tier build, branding

4 weeks

2016-02-02

2016-3-13

Domain, hosting, system in place. See http://openvivo.org Branding nearing completion

See https://goo.gl/MWsVNv

ORCiD authentication, Profile creation, ORCiD hook for DOI

6 days

TBA

TBAJim Blake will work on this
RDF generation for Journals (CrossRef and NLM)4 weeks2016-02-132016-03-13

Muhammad Javed and Violeta Ilik will work with Mike Conlon on Journals. Data model proposed. Data in hand. On track.

RDF generation for Organizations (Grid)4 weeks2016-02-132016-03-13Mike Conlon and Dave Eichmann will created RDF from the GRID data (http://grid.ac). Data in hand, repository created, data inspector created. See https://github.com/openvivo/grid-rdf.
Figshare Collection Ingest4 weeks2016-02-132016-03-13Ted Lawless, Mike Conlon and Simon Porter will work on this. Figshare now producing VIVO RDF. On track.
Identify and represent attribution/contribution4 weeks2016-02-132016-03-13Melissa Haendel, Kristi Holmes, Violeta Ilik and Alexandre Rademaker will work on this.
Publication Ingest from CrossRef with Attribution from user-entered DOI5 weeks2016-02-072016-03-13Substantially complete. Users can enter one or more DOI and/or one or more Pubmed IDs. VIVO fetches the metadata, presents to user for confirmation and association of role. Graham Triggs is working on this. On track.
Full assembly – all features in place. Begin testing, begin remediation, begin data export1 week2016-03-132016-03-19Tight coordination among team members needed here.
Remediation or additional features2 weeks2016-03-202016-04-02If 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 CTSAsearch2 weeks2015-03-202015-04-02Dave Eichmann will work on this

Final acceptance testing, refinement, communications, presentation materials

2 weeks

2015-04-03

2015-04-15Stop adding things. Keep fixing things. Keep smoothing things.

Workshops and Visualizations Hackathon at Force 11 Conference

1 day2016-04-172016-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 days2016-04-182016-04-19Conference attendees: Mike Conlon, Melissa Haendel, Kristi Holmes, Violeta Ilik, Dave Eichmann

 

Contributors

Mike Conlon task force lead, project manager, Orgs, Journals, Figshare

Graham Triggs technical lead, platform, DOI ingest, hosting, platform support

Ted Lawless Figshare ingest

Muhammad Javed RDF for journals

Simon Porter will work on Figshare ingest

Violeta Ilik will work on ontology and RDF

Dave Eichmann RDF for orgs, reuse of data in CTSAsearch

Paul Friedman will work on UI/Design issues

Alexandre Rademaker Ontology work

Melissa Haendel Ontology work

Kristi Holmes Attribution ontology

Jim Blake ORCiD sign on, profile creation, DOI from ORCiD

Meeting Times

Every Tuesday at 1 PM eastern on WebEx

Communication Channels

  • 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


  • No labels