Adds version-of external ID relationships in work records based on DOI metadata

[codycooperross]

Purpose

Adds external-ids in ORCID work metadata based on relevant relatedIdentifiers in DataCite metadata. See this issue and its parent issue for more context:

• https://github.com/datacite/product-backlog/issues/850

This change needs to be implemented in volpino to take effect for manual claims. Levriero needs to be updated to allow auto-update for the above listed relationTypes to take effect for auto-update claims.

See the generated ORCID work metadata example below, which has been confirmed with ORCID:

<?xml version="1.0" encoding="UTF-8"?>
<work:work xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:common="http://www.orcid.org/ns/common" xmlns:work="http://www.orcid.org/ns/work" visibility="public" xsi:schemaLocation="http://www.orcid.org/ns/work ../work-3.0.xsd">
  <work:title>
    <common:title>Spatial distribution and succession of epiphytes on Coco nucifera in Moorea, French Polynesia</common:title>
  </work:title>
  <work:journal-title>University of California, Berkeley</work:journal-title>
  <work:short-description>Spatial distribution and succession of epiphytes on Coco nucifera in Moorea, French Polynesia. Coconut trees are a conspicuous and characteristic part of the South Pacific Landscape. In the past fifty years, a number of coconut tree plantations have been abandoned. These provide for an excellent study of the succession of the epiphytes that use coconut trees as phorophytes. Seven functional epiphyte groups were studied: Bryophytes, Paint Crustose Lichens, Fat Crustose Lichens, Alectorioid Lichens, Cyanobacterial Lichens, Algae and Ferns. Five types of plots were studied, those that had been abandoned for fourty-five years, thirty-five years, twenty-five years, fifteen years, and zero years. Principle Component Analysis confirmed the grouping of the thirteen plots studied within the aforementioned categories. Eight environmental variables of the plots were examined to determine which one had the largest influence on the change in epiphyte composition throughout time. Surrounding canopy cover and canopy height were the two main influential factors determining epiphyte distribution between the plot types as seen through regression and multivariate analysis. Results also showed that Bryophytes are late-successional species and Paint Crustose Lichens and Alectorioid Lichens are pioneer species on Coco nucifera. Succession does occur and radically changes the distributions of the epiphyte functional groups on the coconut trees over time. Epiphytes were found on all plot types from the 20% coverage level and above. A two-tiered model was created to explain succession of epiphytes on coconut trees.</work:short-description>
  <work:type>other</work:type>
  <common:publication-date>
    <common:year>2000</common:year>
  </common:publication-date>
  <common:external-ids>
    <common:external-id>
      <common:external-id-type>doi</common:external-id-type>
      <common:external-id-value>10.82597/xfzk-pg27</common:external-id-value>
      <common:external-id-relationship>self</common:external-id-relationship>
    </common:external-id>
    <common:external-id>
      <common:external-id-type>doi</common:external-id-type>
      <common:external-id-value>10.60950/xx</common:external-id-value>
      <common:external-id-relationship>version-of</common:external-id-relationship>
    </common:external-id>
    <common:external-id>
      <common:external-id-type>doi</common:external-id-type>
      <common:external-id-value>10.60950/yy</common:external-id-value>
      <common:external-id-relationship>version-of</common:external-id-relationship>
    </common:external-id>
    <common:external-id>
      <common:external-id-type>doi</common:external-id-type>
      <common:external-id-value>10.60950/zz</common:external-id-value>
      <common:external-id-relationship>version-of</common:external-id-relationship>
    </common:external-id>
    <common:external-id>
      <common:external-id-type>doi</common:external-id-type>
      <common:external-id-value>10.60950/ww</common:external-id-value>
      <common:external-id-relationship>version-of</common:external-id-relationship>
    </common:external-id>
    <common:external-id>
      <common:external-id-type>doi</common:external-id-type>
      <common:external-id-value>10.60950/gg</common:external-id-value>
      <common:external-id-relationship>version-of</common:external-id-relationship>
    </common:external-id>
  </common:external-ids>
  <work:contributors>
    <work:contributor>
      <work:credit-name>Aaron Wallace</work:credit-name>
    </work:contributor>
  </work:contributors>
</work:work>

Approach

Open Questions and Pre-Merge TODOs

Learning

Types of changes

• Bug fix (non-breaking change which fixes an issue)

• New feature (non-breaking change which adds functionality)

• Breaking change (fix or feature that would cause existing functionality to change)

Reviewer, please remember our guidelines:

• Be humble in the language and feedback you give, ask don't tell.
• Consider using positive language as opposed to neutral when offering feedback. This is to avoid the negative bias that can occur with neutral language appearing negative.
• Offer suggestions on how to improve code e.g. simplification or expanding clarity.
• Ensure you give reasons for the changes you are proposing.