Page History

...

ORCiD API

This release includes an updated improvement to the 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.

streamlines the process of connecting a VIVO profile with the associated ORCiD profile based on whether the VIVO installation is using the 'public' or 'member' ORCiD API.

The following elements have been added to the runtime.properties configurationThe required properties are:

orcid.clientIdapiLevel = 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

...

public | member

Docker

In conjunction with the effort to modularize and decouple VIVO components, this release also demonstrates that modularization by establishing Docker infrastructure for deploying the following modules as separate containers:

• Solr
• MariaDB
• VIVO webapp

The vivo-docker2 can be cloned and deployed with custom configuration.

$ docker-compose up

Additional Error Checking During Builds

...