...
Venue
Location:
The Ver Steeg Faculty Lounge, Room 3770 (see map -> Main Library, Third Floor, South Tower)
Northwestern University Main Library
1970 Campus Drive, Northwestern University
Evanston, IL 60208-2300
EvanstonPhone: 847 847.491.7658 Fax: 847.491.8306 Email: library@northwestern.edu
Time
...
The meeting will begin promptly at 12:00 noon, Monday December 1. Lunch will be available and we'll begin working over lunch. The meeting will end ~ 5:00 p.m. on Monday to allow attendees to check in to their hotel before dinner.
A Group Dinner is planned for Monday evening . Details to follow.at 7:00 p.m. at the The Stained Glass, 1735 Benson Ave, Evanston, IL 60201 +1-847-864-8600
We will resume the meeting at 8:00 30 a.m., Tuesday December 2. Breakfast will be available and we'll begin working during our meal. The meeting will end at 12:00 noonpm.
Transport from O'Hare Airport
...
Evanston is about 15 miles from O'Hare. Taxis are in abundance at the airport. Expect about a half-hour ride (give or take, highly dependent on traffic).
Maps
...
Interactive Google Map with Key Meeting Locations (Library, Hotels, Restaurant), addresses, step-by-step walking or driving directions. Access here or via mobile (link distributed by email). Especially handy on mobile devices.
Static Evanston Area Map with Key Locations.
Evanston Campus and Parking Map - Deering Library Location
Northwestern University Library, Deering Library Map (1970 Campus Drive, Northwestern University, Evanston, IL)
Ver Steeg Faculty Lounge, Room 3770 (South Tower)
Hotel Information
- The Hilton on Orrington in Evanston. http://www.hotelorrington.com/
1710 Orrington Avenue, Evanston, Illinois, 60201, USA +1-847-866-8700
1625 Hinman Avenue, Evanston, IL 60201 +1-847-475-3300
Dinner
7:00 pm, Monday, December 1, 2014
The Stained Glass, 1735 Benson Ave, Evanston, IL 60201 +1-847-864-8600
Meeting Goals
- Monday, December 1, 2014
- Review and Agree Upon Shared Understanding VIVO's Value Proposition & Mission
- The Homestead is also a hotel that the university also uses.
Meeting Goals:
- (Develop Shared Understanding of the Value Proposition of VIVO)?
- Identify and Discuss Key VIVO Goals & Issues
- Prioritize Key VIVO Goals
- & Issues
- Tuesday, December 2, 2014Brainstorm and
- Develop High Level
- Action Plans for Prioritized VIVO Goals & Issues
- Identify Key Means for Communicating and Vetting the Strategic
Agenda:
To be added.
Attendees:
| First Name | Last Name | Email Address | Affiliation | Comments | |
| Paul | Albert | paa2013 at med.cornell.edu | Weill Cornell Medical Library | Remote 12/1. Conflict 12/2. | |
| Amy | Brand | a.brand at digital-science.com | Digital Science | ||
| Mike | Conlon | mconlon at ufl.edu | University of Florida | ||
| Jon | Corson-Rikert | jc55 at cornell.edu | Cornell University | ||
| Don | Elsborg | elsborg at colorado.edu | University of Colorado Boulder | ||
| Shahim | Essaid | essaids at ohsu.edu | Oregon Health & Science University | ||
| Melissa | Haendel | haendel at ohsu.edu | Oregon Health & Science University | Remote | |
| Kristi | Holmes | kristi.holmes at northwestern.edu | Northwestern University | Local Host & Contact | |
| Layne | Johnson | ljohnson at duraspace.org | DuraSpace.org | Facilitator, Contact | |
| Michele | Kimpton | mkimpton at duraspace.org | DuraSpace.org | Facilitator | |
| Jonathan | Markow | jjmarkow at duraspace.org | DuraSpace.org | Facilitator | |
| Robert | McDonald | rhmcdona at indiana.edu | Indiana University | ||
| Liz | Tomich | tomich at colorado.edu | University of Colorado Boulder | Remote | |
| Julia | Trimmer | julia.trimmer at duke.edu | Duke University | ||
| Michael | Winkler | winkler4 at upenn.edu | University of Pennsylvania | ||
| Mike | Wright | mwright at ucar.edu | UCAR - University Corporation for Atmospheric Research | Facilitator |
Survey Results
...
:
A brief survey was sent to 41 recipients representing the VIVO Leadership Group, the VIVO Steering Group, the VIVO Management Team and the VIVO Strategy Group. Nineteen of 41 (46%) survey participants responded to the survey. Recipients were asked to provide bullet point answers to the following questions:
- What do you think the value proposition is for VIVO? Click here to view raw data.
- What do you see as VIVO’s top goals in the next 2-3 years? Click here to view raw data.
- What do you think are the key issues and challenges for VIVO that need to addressed in the next 2-3 years?
The raw results are presented in the three tables that follow.
What do you think the value proposition is for VIVO?
| Quality, curated, structured data vetted by institutions and researchers/scholars that can support attribution, contribution, and collaboration across diverse organizations and disciplines. | Partnership with journals, funders, and institutions, can support a more quality and fair research enterprise. | The ability to curate and link data about academic output and academic networks (ex. pubs, grants, mentorships) that do not normally exist anywhere else in an institution. | |
I don’t know. | VIVO provides a way for researchers to connect with each other, and each others “research” beyond institutional boundaries. It allows researchers/users to identify other researchers working in a particular domain or area of expertise and therefore make a connection that otherwise may have been difficult to find. | Ontology designed around roles and activities to anticipate and encourage a future where traditional publications and citation counts are not the only metrics of scholarship | |
| Software platform designed for flexibility and integration of diverse types of data | Focus on promotion of networking and discovery | VIVO provides a research networking platform using semantic web technology and an ontology that is shared by other platforms and tools, as well as a community of experienced, engaged members | |
Increased discoverability for the scholarly outputs and expertise of institution's faculty and researchers by providing search engine optimized web pages, engaging visualizations that summarize this information and encourage exploration, and innovative browsing and search capabilities in the web site. | To raise the quality of data related to the above, by making this information public and encouraging institutions to curate and identify best sources and systems of record. High quality data is valuable. | Enabling re-use of this high quality data, such as data syndication of VIVO data on other institution web sites, in a variety of public and internal reports, etc. | |
Embracing and supporting Linked Open Data and the related network effect, to offer a viable open alternative to "closed platform" research tools like ResearchGate. | VIVO offers value as a tool for building networks of structured, semantic data within universities and other research-oriented organizations and connecting people and research across those organizations through search and direct harvesting or linking | The VIVO-ISF ontology offers a coherent set of classes and properties for relating people, organizations, and the activities of research in a way that captures relationships and roles over time and can be shared across institutions. The modular design of the VIVO-ISF ontology allows flexibility in focusing on one domain or adding new extensions to support additional disciplines or new domains | |
The Vitro software offers a basic ontology editor, content entry and editing facilities, public-facing web display, and linked data services in a single, open source platform suitable for rapid prototyping of new semantic applications, especially for developing or testing a new ontology by populating it with data and sharing with domain users for evaluation and testing | Continual development and expansion of the product | Expanding the VIVO community and customer base to further achieve product benefits and sharing of knowledge | |
| VIVO as a stand-alone packaged semantic web suite. E.g. VIVO eliminates (or at least reduces) the need to cobble together numerous independent tools when deploying semantic web technologies. | Structured, linked open data | Platform for coordinated management of academic information and interoperability of systems that consume that information | |
Enabler of cross-institutional research networking^^^ | |||
What do you see as VIVO’s top goals in the next 2-3 years?
| Data integration and standardization across multiple systems - Cerif, ORCID, ScienCV, Profiles, LOKI, etc. | Key partnerships with outside communitie | Aligning each VIVO instance's extensions, data across the consortium, and its reuse in other applications | |
| Having a closer partnership with each VIVO instance | Quality ontology/standards management and development for a better integration into the software stack (or for other applications as well). | Ingest – select (or develop) an entry-level ingest tool and thoroughly support its use with tutorials, examples, and workshops. | |
Core – continue to improve modularity, with plug-and-play triple-stores and reasoners. | Core – lower the bar to entry with a binary distribution; no database, no Ant, no Tomcat, no Vagrant, just a Java runtime required. | Outreach – convey usability, maturity, and coherence in all aspects of web presence. Crowdsourcing will not accomplish this. | |
| A stable community built and supported ontology. VIVO needs to build a larger and more stable ontology community that is in sync with downstream consumers of VIVO data. For example, Profiles RNS sites still exist emitting data in 1.4 ontology. What is the future of their data? | More data out. The community needs to give more effort into producing ( or facilitating the production of ) secondary data sets that are useable by administrative folks (aka donors, funders) and academics alike. Dave Eichmann at IOWA is doing a great job of this using harvested VIVO data. | More developers. VIVO needs more developers. VIVO needs to work on getting in tune with the preferred working methods of the cohort of probable developers in the communities that seem to be attracting themselves to VIVO. This may require surveying or reaching out to this group about this particular topic. | |
Make and easy to install, default configuration, application- reduce flexibility and increase simplicity Increase the number of adopters worldwide, including lead institutions that can set an example for others and contribute to the project | Expand the community to be more inclusive, democratic, and diversified so can start building a robust community source project | Clearer articulation of the value proposition to the academic community | |
| Better marketing and branding, not only of the product(s) but of the community's vision | More complete and accessible documentation | Streamlined web presence; straightforward, timely communications that can be easily understood by prospective users or contributors | |
| A software release process that's driven not by incremental improvements desired by existing users but by exciting and useful new features that can capture the imagination and energy of new adopters | To develop a VIVO search tool, to expand our capabilities to support new VIVO implementations and to add/improve features like CVs, visualizations, embedded content and other cool "gadgets" | Increased open source commiter activity on the Vitro and VIVO projects, e.g. coordination of more code sprints and hackathons. | |
Releasing VIVO Search or supporting a similar solution like DIRECT2Experts. | Providing input for use case driven evolution of the VIVO-ISF data standard. | Increased adoption by universities and research institutions, e.g. having more than 100 active VIVO implementations in production. | |
Transforming an informal network of committed individuals into a sustainable community offering transparent governance, the capability to deliver production-quality software and ontology, and an openness to new ideas and directions | Communicating where we are as a community, what we offer, and how we can partner with other organizations and movements to achieve goals such as shared identifiers and data interoperability | Attracting new contributors (financial and in-kind) to the community by broadening VIVO’s reach in the sciences and biomedicine, in the humanities, and in libraries through closer integration with DuraSpace’s other communities supporting research data and repository technologies | |
| Achieving performance optimisations | A more modular software structure where user developed functionality could more easily be plugged into the software build | Strengthen the open technical community and provide more training and "VIVO in the wild" showcases (e.g. it seems hard still to find out who is running instances at their institutions, which increases the difficulty of understanding who is doing what and who to ask to come out and play) | |
| A key strength of the technology is the distribution (federation) of data ... this needs more attention in the beginning with stronger and more compelling demonstrations of that strength (this is particularly a problem when you don't know who is running VIVO) | Expanding the core services beyond the university faculty/staff information use case. | Increased adoption | |
Progress on VIVO search^^^ | |||
What do you think are the key issues and challenges for VIVO that need to addressed in the next 2-3 years?
...
...
Ontology developers must become user-oriented, and with an eye toward practical performance levels.
...
To grow our community and strengthen the options for providing help and support to members.
...
To avoid being fractured into too many initiatives and directions and to stick to our core missions.
...
To solicit new leadership and find ways to get feedback from all of our member institutions.
...
Best supporting backwards compatibility and data migration for older VIVO implementations as the VIVO-ISF ontology evolves.
...
Encouraging more VIVO implementers to share their extensions as open source.
...
Increased clarity on the Vitro project, i.e. will it be promoted to other user bases or remain focused as a tool for the current faculty/researcher user base? Should it be renamed to amplify the VIVO brand, e.g. VIVO Core?
...
Addressing performance issues in the application and its software dependencies.
...
Identifying or providing more linked open data sources for commonly referenced individuals such as institutions, journals, and concepts (ex. MeSH).
...
Explaining what we do, why we do it, and how newcomers (and even some long-timers) can effectively participate, meet their own goals, and contribute going forward
...
Transitioning from reliance on a passive “build it and they will come” approach for data, ontology, and software to delivering coherent and robust tools and visualizations that show the significance of the data we have collectively gathered and how it can be applied to emerging information needs
...
Establishing a evolving road map definition and evaluation process that reflects the best ideas in our community, makes those ideas more tangible, and points out where the biggest challenges remain
...
Building confidence within our community that we can survive changes in personnel and even changes in partnerships as institutions, movements, and priorities change over time
...
Complexity of implementation
...
Commercial profile solutions
...
Survey respondents articulated a wide-range of statements regarding the Value Proposition for VIVO.
Goals were created by analyzing the raw survey data and were categorized by 3 Strategic Themes, including:
- Community
- Sustainability
- Technology
Click here to view Strategic Theme Goals generated from aggregated survey data.
Click to view Attendees:
...