September 30, 2022 Project deliverable Open Access

De Santis, Luca

MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="a">eng</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">SSH</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Data enrichment</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Metdata</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Open Science</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">OPERAS</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">TRIPLE</subfield>
  </datafield>
  <controlfield tag="005">20230417090012.0</controlfield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">The TRIPLE project (https://project.gotriple.eu/), which is financed under the Horizon 2020 framework https://cordis.europa.eu/project/id/863420), under Grant Agreement No. 863420, with approx. 5.6 million Euros for a duration of 42 months (2019-2023). The content of this deliverable reflects only TRIPLE's view and the Commission is not responsible for any use that may be made of the information it contains.
---
At the heart of the project is the development of the GoTriple platform (https://www.gotriple.eu/), an innovative multilingual and multicultural discovery solution.</subfield>
  </datafield>
  <controlfield tag="001">7359654</controlfield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">1541955</subfield>
    <subfield code="z">md5:707161b88c88a3a8a91120eff20d502f</subfield>
    <subfield code="u">https://zenodo.org/record/7359654/files/D2.5-Report on data enrichment-1.0_TRIPLE.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2022-09-30</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="p">user-operaseu</subfield>
    <subfield code="o">oai:zenodo.org:7359654</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">Net7</subfield>
    <subfield code="0">(orcid)0000-0003-0527-840X</subfield>
    <subfield code="a">De Santis, Luca</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">TRIPLE Deliverable: D2.5 - Report on Data Enrichment</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">user-operaseu</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="c">863420</subfield>
    <subfield code="a">Transforming Research through Innovative Practices for Linked interdisciplinary Exploration</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">https://creativecommons.org/licenses/by/4.0/legalcode</subfield>
    <subfield code="a">Creative Commons Attribution 4.0 International</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;In this deliverable, the strategies for data enrichment in TRIPLE are presented. Through the Core&amp;nbsp;Pipeline, named SCRE, metadata regarding publications and projects for the Social Sciences and&amp;nbsp;Humanities are automatically harvested, mapped in the TRIPLE data model, curated, enriched&amp;nbsp;and finally saved in the GoTriple platform&amp;rsquo;s indexes.&lt;br&gt;
The document starts by presenting the ways SCRE imports publications metadata from&amp;nbsp;OAI-PMH endpoints, OpenAIRE and Isidore data dumps. This reflects the strategies for&amp;nbsp;integrating content which was planned in the project. On the one hand, OAI-PMH is a&lt;br&gt;
well-known and established standard for content harvesting: many data providers, especially&amp;nbsp;those of small dimension, support it, facilitating therefore their onboarding in GoTriple. The&amp;nbsp;support for OpenAIRE and Isidore, on the other hand, responds to the wish to also harvest data&amp;nbsp;from large aggregators, a strategy that allowed GoTriple to quickly present a significant amount&lt;br&gt;
of publications in its index (more than 4 million at the time of writing).&lt;br&gt;
Then the normalisation strategies applied to the acquired metadata are described. By analysing&amp;nbsp;the first batches of acquired data, it has been decided to define the rules to normalise and clean&amp;nbsp;the attributes for the following metadata: publication date, language codes, keywords,&amp;nbsp;document types, licences, access rights and authors&amp;rsquo; names. In the document, the definition of&lt;br&gt;
controlled vocabularies for some of these attributes is also presented.&amp;nbsp;&lt;/p&gt;

&lt;p&gt;Then enrichment services are explained, including language recognition, translation, automatic&amp;nbsp;classification and annotation.&lt;br&gt;
The services to detect duplicate publications and to disambiguate authors are also discussed,&amp;nbsp;followed by the presentation of the acquisition and processing of project metadata&amp;nbsp;&lt;/p&gt;

&lt;p&gt;Some final remarks on the data enrichment process, including the difficulties that have been&lt;br&gt;
faced and solved, conclude the document.&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isVersionOf</subfield>
    <subfield code="a">10.5281/zenodo.7359653</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.7359654</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">deliverable</subfield>
  </datafield>
</record>