Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Version 1.9.3

Improvements

ORCiD API v2

This release includes an updated ORCiD integration that can use the ORCiD v2 API. Note that ORCiD are planning to shut down the v1.x API endpoints.

Note that the configuration options have been changed, and you will need to update your runtime.properties.

The only options that are required now are:


# orcid.clientId = 0000-0000-0000-000X
# orcid.clientPassword = 00000000-0000-0000-0000-000000000000
# orcid.webappBaseUrl = http://localhost:8080/vivo
# orcid.externalIdCommonName = VIVO Cornell Identifier
# orcid.apiVersion = 2.0
# orcid.api = sandbox


orcid.apiVersion is simply the version value (e.g. 1.2, 2.0), and orcid.api is just "release" (for the production API), and "sandbox" for the sandbox.

Search Results Performance

Retrieval of Person information has been improved so that any search that returns people is faster.

Direct2Experts Endpoint

For any sites wishing to participate in the Direct2Experts federated site - http://direct2experts.org/ - VIVO now includes the necessary endpoints. Please see the Direct2Experts websites for more information on how to participate.


Improved handling for TDB triple stores

Isomorphic tests for TDB now handle all of the specialized integer types (NonNegative, Positive, etc) that TDB maps to an internal structure.

Performance for TDB triple stores is improved as the Graph URIs are now cached in the RDF Service.


Version 1.9.2

Improvements

Upgraded GEMET integration to use SSL web service

Upgraded LCSH integration to use current web service

Bug Fixes

Problem with creating new items

Add dependencies for ORCID integration

Spaces in prefix definitions

Resolved Issues

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyVIVO-1289

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyVIVO-1306

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyVIVO-1313

Version 1.9.1

Improvements

Responsiveness of Capability Map

Add Turtle support to file graph loader

Bug Fixes

schema.org errors on profile pages

Maven character set issues on Windows

Maven correctly sets Java 1.7 version

Use background RDFService correctly

Resolved Issues

Improvements

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyVIVO-1261

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyVIVO-1271

Bug Fixes

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyVIVO-1262

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyVIVO-1263

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyVIVO-1268

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyVIVO-1269

Version 1.9.0

What's New

Capability Map

To address the desire for improved expert finding features in VIVO, we are pleased to introduce a capability map. This feature allows you to search for research areas, and see the relationship between them and the researchers.

...

Note
titleNotes for Upgrading

The capability map is only linked to from the menu bar. As this is configured through the triple store, and the initial definitions are in a file that only gets loaded the first time VIVO is run, upgrading applications will not have the link present.

To access the capability map in an upgraded VIVO, you need to browse to the following url path:

<vivo>/vis/capabilitymap

This can be added to an existing application's menu bar via the Site Admin pages. See 'Upgrading VIVO' for details.

Initial implementation provided by: Simon Porter, Matěj Korvas, Martin Kwok, and Melissa Makin; University of Melbourne.

...

Note

When upgrading, you will need to update you your applicationSetup.n3 in order to use the new Image Processor.

...

The YASQE highlighting editor for SPARQL has been incorporated into the SPARQL Query page, thanks to a contribution from Ted Lawless.

Contributors

Ariel D Moya Sequoia David Moya Sequeira, IT Alkaid Consulting S.A.

...

Melissa Makin, University of Melbourne

Resolved Issues

Features

Jira
serverDuraSpace JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyVIVO-1082

...