VIVO & Eagle-i @ IU Workshop

Feedback from experience at IU creating and populating a research instance

• Improving manual data entry
• Rolling out self editing at IU – authentication, permissions, policies
• Data provenance and update policies/workflow
• Features and schedules for upcoming releases

VIVO Visualizations

• How can VIVO visualization tools become more general so that they can be adopted for other projects, using other LOD data?
• How should we interact with other semantic web programmers?

Ontology team preparation for meetings with Eagle-i

•  Review of Eagle-i ontology
• Compiling a list of classes and properties we would like to import
• Preparing for discussions on future directions, expertise, and interoperability

VIVO & Eagle-i development overviews (once Daniela Bourges arrives)

•  Overview of VIVO including current visualizations, theming at different sites, and the research instance at IU
• Discussions of technology choices and how they reflect the respective project goals, data sources, and support models
• Discussion of commonalities based on use of ontologies and triple stores

Search in Eagle-i and VIVO

• Overall requirements and goals at the individual institution and national level
• Opportunities for semantic search leveraging controlled vocabularies and other classes and properties in our respective ontologies
• Exploration of development perspectives on using ontologies for application configuration and/or search interface contextualization

Development directions focusing on visualization and interoperability

• Most likely areas of collaboration
• Considering how to engage wider communities – a hackathon event?

Introduction of new participants, and current status of the ontology development for two projects)

Brainstorming with development and ontology teams on goals and means for interoperability among VIVO, Eagle-i, and M-Cores

• At the data modeling/ontology level
• At the search level
• At the core facility level – how can VIVO and Eagle-i provide tools for both researcher and resource networking without requiring duplicated effort?

•  Ontology alignment and interoperability through direct imports of classes and properties in both directions
• eagle-i and Vivo usage of OWL axioms. similarities, differences, best practices (usage of equivalent classes, class restrictions etc)
• referencing external taxonomies and ontologies such as genes
• resolving person URIs and interoperabilty between eagle-i and vivo
•  Common points of intersection and overlap with other ontologies
• Design of ontologies for application configuration and search interfaces
•  Opportunities for sharing data and exploring direct interoperability between VIVO and Eagle-i installation at OHSU
•  Referencing individuals across triple stores -- approaches for sharing and/or linking instance data
• Possible collaborations on visualization and data analysis

Topics and outline generation for a joint paper on Eagle-i and VIVO ontologies

• How the goals and requirements of the two projects have influenced the two ontologies – how are they similar and how are they different
• Common principles and best practices
• Establishing intereoperability
• What this will mean for sustainability

Approaches to discovering expertise

• Discussion of use cases and examples of the type of inferencing that we'd like to be able to do (homework prior to the meeting)
• Approaches -- textual, network and semantic analysis, composites of both
• Usage of text/data mining to validate ontology (could also go elsewhere in agenda)
• Relationships to controlled vocabularies

Representing expertise

• Existing tools and relevant projects (e.g., OpenCalais, OpenAmplify, Gridworks Suggest)
• What would be different about a semantic approach?