Mozilla Open Science Hackathon. On June 2 and June 3, Mozilla will host a global open science hackathon. VIVO participated last year, working on ORCID2VIVO, and generating ideas that led to features in OpenVIVO. Interested in participating? Have ideas for the hackathon? Just curious about what a hackathon is, and how it might help VIVO and open science? See 2016 Mozilla Science Lab Global Sprint in the wiki and contact Alex Viggio with questions, ideas, interest.
Apps and Tools Call. The Apps and Tools Interest Group will have its call this Thursday at 1 PM US Eastern time. Apps and Tools features short presentations by VIVO implementors and developers regarding tools they have created for use with VIVO. Many of these tools are available in the Community Projects catalog. These tools may help you with your implementation, with improving your VIVO services, or give you ideas about how you might use VIVO.
Force16. The Force16 conference in Portland was fabulous in no small part due to the incredible leadership and vision of the conference chair, and VIVO Steering Committee member, Melissa Haendel of Oregon Health and Sciences University. The "Force" idea grew out of a small meeting at UCSD called "Beyond the PDF" – an eclectic group of people seeking to create new forms of scholarly communication, going beyond the published paper to include all forms of scholarly work, and making room for data, visualizations, software, and other contributions that the current scholarly ecosystem currently finds difficult to support. Force11 is the name of the organization. You can find them here: http://force11.org. OpenVIVO debuted at Force16, demonstrating a contribution ontology by which people could indicate their non-author roles in scholarly works. It was very well-received. You can find the poster on Figshare and in OpenVIVO (imagine that).
OpenVIVO. A VIVO anyone can join. Have you tried OpenVIVO? It's easy. Get an ORCiD at http://orcid.org and sign on to OpenVIVO at http://openvivo.org OpenVIVO received many positive comments and tweets at its debut at Force16. Force16 used OpenVIVO to represent its scholarship – attendees registered with their ORCiD and provided their work to Figshare, tagging the work "force16." Using the public Figshare API, the OpenVIVO Task Force developed software to identify tagged works in Figshare, gather their metadata, and create RDF for VIVO. The RDF was then loaded to VIVO. You can find the Figshare ingest software on GitHub: https://github.com/openvivo/figshare-rdf The result is an event page in OpenVIVO that contains a roster of attendees and a roster of works, creating a record of the conference. See http://openvivo.org/display/eventFORCE2016. The VIVO Conference (August 17-19, Denver) plans to use the same approach.
VIVO User Group Meeting, May 5-6, Chicago. It's 10 days or so until the first VIVO User Group meeting in Chicago. Still time to register and attend. http://vivousergroup.eventbrite.com The meeting will provide an important opportunity to discuss directions for the future of VIVO. Many ideas for VIVO have been generated through the roadmap process, the "I wish I could use VIVO to ..." survey, steering and leadership calls, and community participation on VIVO email lists. You can find a synthesis of ideas, open for comment here. The ideas are not presented in any order.
VIVO Project Director