...

• Make the About page and Home page HTML content editable through admin interface – this relates to display model changes
• (Largely complete) Offering improved options for content on the home page, including a set of SPARQL queries to highlight research areas, international focus, or most recent publications
• (Complete) Offering additional individual page template options
• (Complete) Offering the ability to embed SPARQL query results in individual pages on a per-class basis – for example, to show all research areas represented in an academic department
• (Complete) Cornell is working on new individual page templates that include screen-captured versions of related websites for people and organizations, so that in addition to the link to the website we show either a small or large version of a thumbnail of the page. This is done through a commercial image capture service that other sites may not want to use, and will have to become configurable. Another service might not provide the same API or resultant image size, however. In any case, the new individual page templates will have to be optional, since sites may have done a lot of customization work.
  
  • Could put the service-specific aspects in a sub-template that gets imported and could be default not attempt to capture and cache images at all
  • are free services out there, but they may not be there in 6 months

Content Curation

Support for sameAs statements

When 2 URIs are declared to be the same in VIVO, all the statements about both will be displayed for either (e.g., Israel and Israel). Improvements are needed, however:

• there is no way via the current UI to add or remove owl:sameAs assertions – they have to be added as tiny RDF files via the add/remove RDF command
• sameAs in the subject position
  
  • It will adversely affect performance to require VIVO to detect that two or more URIs for an individual have been declared to be sameAs each other and then retrieve and blend all the data for each URI for rendering on a single page
    
    • This becomes more complicated when the 2nd or higher URI is not in the local VIVO
  • It may be a first step to simply show a link to the equivalent URI, with some form of "see also" label
• sameAs in the object position
  
  • when another VIVO individual is linked to one or the other of these Israels, the application is not yet smart enough to show only one object property statement to one instance of Israel, and it looks to users like a duplicate of both the country and the relationship
• Colorado has a use case to assert sameAs relationships between people's profiles in their university-wide VIVO and the separate implementation at the Laboratory for Atmospheric and Space Physics, where additional information about research projects, equipment, and facilities will be stored behind a firewall. They would like to pull data from the CU VIVO into the LASP VIVO dynamically, and pull any publicly visible data from LASP VIVO to supplement the CU VIVO content about a person.
• Colorado also has a need to pull data from the Harvard Profiles system used by the University of Colorado Medical School in Denver to the CU VIVO without replicating more than is necessary. This is a similar use case to the connections needed between VIVO on the Cornell Ithaca campus and the Weill Cornell VIVO.

URI Tool

The URI Tool is a simple application designed to facilitate data cleanup in VIVO following ingest, often from multiple sources. The tool can be configured to run one of four or five pre-defined queries to identify journals, people, organizations, or articles with very similar names. A bare-bones editing interface allows a relatively untrained user to step through lists of paired or grouped candidates for merging, identify which existing properties to keep, and confirm that the candidates should be merged. Links to the actual entry in VIVO facilitate verification. When the review process is complete, the URI Tool application writes out both retraction and addition files, which can then be removed from or added to VIVO using commands on the ingest menu.

This tool does not replace the need for author disambiguation and other cleanup work prior to ingest, for which the Google Refine extensions for VIVO and the Harvester tool have been developed. However, it does have the potential to become a considerable time saver for cleaning data once loaded into VIVO.

• further generalization and documentation of Joe McEnerney's URITool, including support for finding and removing/correcting data in only one named graph
• improvements to the interface

Editing

Web service for the RDF API

• Implementing a web service interface (with authentication) to the VIVO RDF API, to allow the Harvester and other tools to add/remove data from VIVO and trigger appropriate search indexing and recomputing of inferences.
• This would also enable
• VIVOIMPL-15 improve the permissions scheme for editing and make its functions more transparent to users
• implement round-trip editing of VIVO content from Drupal or another tool external to VIVO via the SPARQL update capability of the RDF api introduced in VIVO 1.5

Editing

• VIVOIMPL-15 improve the permissions scheme for editing and make its functions more transparent to users
• improve editing of roles data held in context nodes from the organization, event, or other entity that the role is related entity, principally via relationships like authorships or positions or via roles realized in or contributes toassess implications for the application of moving to fewer classes and properties and shifting the current differentiation of property groups to be based on a combination of a property and its related range class(es)processes or events – most custom forms support entry and editing only from the person

Other candidate issues relating to content editing

...

• Integrating Mummi Thorisson's Ruby-based CrossRef lookup tool for searching and loading publications into VIVO, on GitHub along with OAuth work for retrieving information from a VIVO profile in another application
• Improving and documenting the Harvester scoring and matching functionsImplementing a web service interface (with authentication) to the VIVO RDF API, to allow the Harvester and other tools to add/remove data from VIVO and trigger appropriate search indexing and recomputing of inferences.

Internationalization

• Moving text strings from controllers and templates to Java resource bundles so that other languages can be substituted for English
• Internationalization for ontology labels – important because much of the text on a VIVO page comes directly from the ontology
• Improving the VIVO editing interface(s) to support specification of language tags. Note that VIVO 1.5 will respect a user's browser language preference setting and filter labels and data property text strings to only display values matching that language setting whenever versions in multiple languages are available – but there has not yet been a way to specify language tags on text strings.

...

• Yin's alternate search approach at NYU that indexes everything in the context of connections to people and displays results only for people could be of interest to others but would require modularity in search indexing code as well as other ways that the search index integrates with VIVO

URI Tool

The URI Tool is a separate, simple application designed to facilitate data cleanup in VIVO following ingest, often from multiple sources. The tool can be configured to run one of four or five pre-defined queries to identify journals, people, organizations, or articles with very similar names. A bare-bones editing interface allows a relatively untrained user to step through lists of paired or grouped candidates for merging, identify which existing properties to keep, and confirm that the candidates should be merged. Links to the actual entry in VIVO facilitate verification. When the review process is complete, the URI Tool application writes out both retraction and addition files, which can then be removed from or added to VIVO using commands on the ingest menu.

This tool does not replace the need for author disambiguation and other cleanup work prior to ingest, for which the Google Refine extensions for VIVO and the Harvester tool have been developed. However, it does have the potential to become a considerable time saver for cleaning data once loaded into VIVO.

• further generalization and documentation of Joe McEnerney's URITool, including support for finding and removing/correcting data in only one named graph
• improvements to the interface