Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info
titleFormingHiatus
The Membership task force is forming, and looking for additional help. If you'd like to help, please contact Jonathan Markow or Mike Conlon

 

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.

 

...

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

...

3 weeks

...

2016-01-24

...

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

...

4 weeks

...

2016-02-02

...

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

...

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

...

Final acceptance testing, refinement, communications, presentation materials

...

2 weeks

...

2015-04-03

...

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.

...

has finished its work for 2016 and will restart in the spring of 2017. If you are interested in helping, please contact Mike Conlon

Purpose

The Membership Task Force will organize all effort related to the 2016 VIVO Membership Drive.  The Membership Drive is an annual activity to enroll new members and to renew existing members.  VIVO is a member-supported project.  Membership is the key mechanism for raising funds for VIVO.

Objectives

  1. Double the number of VIVO members
  2. Maintain at least 100% revenue from current members
  3. Develop and execute a plan of action to recruit new members and retain current ones

Deliverables

  • "Decision Maker" and "Advocate" contacts for new prospects
  • Plan for soliciting membership prospects
  • Plan for retaining current members at current levels or higher
  • Achieve task force objectives by Oct 31, 2016

Resource

Task Force Members

Meeting Times

The task force will meet bi-weekly during the early period of the campaign, beginning the week of April 4, 2016, meeting times TBD.  The task force will run concurrently with the DuraSpace annual membership campaign, April to October, 2016.  The meeting schedule will decline in frequency during the campaign.

Communication Channels

  • Task force members will share a Google Sheet with campaign data; task force will communicate through teleconferences and emails

  • Notes of meetings will appear below
  • Steering and Leadership groups will review status of membership drive on a regular basis; remainder of the community will be kept up to date through VIVO Updates

 

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

Children Display