The VIVO Apps and Tools Working Group meets every four weeks via teleconference to discuss applications, tools, and practices relevant to sites working with VIVO and related technologies. All are welcome to attend. Agendas are posted to the VIVO mailing lists. See the VIVO calendar for the next meeting.
Participate
- Twitter: #hackvivo
- Sign up to give a 5-7 minute talks on an upcoming call: http://goo.gl/Cjx0qK.
- Mailing List Signup (vivo-dev-all): http://goo.gl/KIkarh
- Leadership
- Chris Barnes, Working Group Chair (@senrabc on twitter)
- Ted Lawless, Working Group Co-Chair (@tedlawless on twitter )
Catalog of tools and maintainers
Please help make this catalog better. Add any apps or tools and links and contacts for the maintainers.
Tool Name | Description | Contact |
---|---|---|
VIVO Vagrant | a virtual machine for development that can load an empty vivo. Can be stored in git or other source control repository. Allows the use of scripting to configure and load with data with automation. Open issues on Github or submit pull requests to request features or ask questions. https://github.com/lawlesst/vivo-vagrant | Ted Lawless from Brown |
VIVO Docker | This project contains code for dockerizing VIVO. In particular, it supports creating the containers to compile and deploy the VIVO application; to extend the application with GWU specific configuration, including a local ontology, for use as an example for extending the app image for local setting; to instantiate a MySQL db; to instantiate an instance of Tomcat for the app to run in; and to provide an environment for loading VIVO. | Justin Littman from George Washington University (justinlittman at gmail.com) |
multisite VIVO search | Brian Caruso (bdc34@cornell.edu) and Jim Blake (jeb228@cornell.edu) | |
VIVO Searchlight | browser bookmarklet for finding people across VIVO sites based on the content of the page you are on. uses search index from vivosearch.org | Miles Worthington (mw542@cornell.edu) |
Wordpress plugin for VIVO | allow data from VIVO to be used with Wordpress | Mike Conlon (mconlon@ufl.edu) |
Linked Data Import | Drupal 7 module for importing linked data into Drupal. Works nicely with VIVO data, no SPARQL endpoint necessary. | Miles Worthington (mw542@cornell.edu) |
CTSASearch | multisite CTSA search that includes VIVO and other profiling systems | Dave Eichmann (email: tbd) |
VIVO Harvester | Data ingest tool for VIVO | John Fereira from Cornell and Eliza Chan from WCMC |
Exhibit 3.0 | Publishing Framework for Large Scale Data-Rich Interactive Web Pages | Mackenzie Smith |
R toolkit | Tools for making VIVO visualizations with R | Mike Conlon (mconlon@ufl.edu) |
Open Refine | Data tools for VIVO based on Google Refine | Eliza Chan from WCMC,Chris Westling from Cornell |
Python Tools | Creating RDF for VIVO; interacting with the VIVO web application from scripts. | Ted Lawless from Brown |
Karma | A data integration tool | Pedro Szekely from USC, Violeta Ilik |
Elements | Elements automatically collects and de-duplicates research outputs and other CV data which can be harvested and displayed as a VIVO profile. Check out our VIVO open source connector at https://github.com/Symplectic/vivo which supports VIVO-ISF. | Alex Viggio (alex@symplectic.co.uk) |
SciVal | < help fill me in > | < help fill me in >, Elsevier |
CKAN data repository | http://ckan.org open data publisher | Patrick West from RPI |
VIVO Widgets | Produces JSON and JSONP feeds for organizations and individual people. Does this quickly using a dedicated Solr index. Provides a user interface with auto-generated code that can be copied quickly into a webpage in order to show formatted data from Vivo instance. | Jim Wood (jim.wood@duke.edu) & Richard Outten (richard.outten@duke.edu) |
Digital Vita Docs (DV Docs) for VIVO | The development of DV Docs described in this proposal has three goals: (1) develop a method to output personal profile data stored in VIVO as structured, well-formatted documents in rtf or pdf format; (2) provide a generalized, template-based approach for developers to modify the format and/or content of generated documents in order to allow them to create new documents based on the VIVO data model; and (3) provide a basic, standalone Web application to edit and generate full NIH biosketches based on functionality currently implemented in DV. | |
ORNG (OpenSocial) Gadgets | Cross-platform plugins for VIVO and Profiles RNS, used at several institutions. Apps library includes free apps written by Baylor, UCSF, Knode Inc., etc. More info at http://www.orng.info/ | Eric Meeks at UCSF (eric.meeks at ucsf.edu) |
UCSF developer portal | Standalone website for on-campus developers documents and evangelizes reuse of RNS data. For example, take a look at documentation for UCSF-internal simplified JSON API. | Anirvan Chatterjee at UCSF (anirvan.chatterjee at ucsf.edu)
|
For retrieving data from the ORCID API and crosswalking to VIVO-ISF. | Justin Littman |