October 1, 2019 Journal article Open Access

Martin, Paul; Remy, Laurent; Theodoridou, Maria; Jeffery, Keith; Zhao, Zhiming

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="653" ind1=" " ind2=" ">
    <subfield code="a">Virtual research environment</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Science gateway</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Research infrastructure</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Metadata catalogue</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Metadata mapping</subfield>
  </datafield>
  <controlfield tag="005">20200120170418.0</controlfield>
  <controlfield tag="001">3467100</controlfield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">EuroCRIS</subfield>
    <subfield code="a">Remy, Laurent</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">FORCE</subfield>
    <subfield code="a">Theodoridou, Maria</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Keith G Jeffery Consultants</subfield>
    <subfield code="a">Jeffery, Keith</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">University of Amsterdam</subfield>
    <subfield code="0">(orcid)0000-0002-6717-9418</subfield>
    <subfield code="a">Zhao, Zhiming</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">1566952</subfield>
    <subfield code="z">md5:bdfaa2ea29ac7ed09c2398e650634749</subfield>
    <subfield code="u">https://zenodo.org/record/3467100/files/2019.journal.fgcs.semantic-mapping-camera.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2019-10-01</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="o">oai:zenodo.org:3467100</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="4">
    <subfield code="c">1-13</subfield>
    <subfield code="v">101</subfield>
    <subfield code="p">Future Generation Computer System</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">University of Amsterdam</subfield>
    <subfield code="a">Martin, Paul</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Mapping heterogeneous research infrastructure metadata into a unified catalogue for use in a generic virtual research environment</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="c">676247</subfield>
    <subfield code="a">A Europe-wide Interoperable Virtual Research Environment to Empower Multidisciplinary Research Communities and Accelerate Innovation and Collaboration</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="c">654182</subfield>
    <subfield code="a">Environmental Research Infrastructures Providing Shared Solutions for Science and Society</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;Virtual Research Environments (VREs), also known as science gateways or virtual laboratories, assist researchers&lt;/p&gt;

&lt;p&gt;in data science by integrating tools for data discovery, data retrieval, workflow management&lt;/p&gt;

&lt;p&gt;and researcher collaboration, often coupled with a specific computing infrastructure. Recently, the push&lt;/p&gt;

&lt;p&gt;for better open data science has led to the creation of a variety of dedicated research infrastructures&lt;/p&gt;

&lt;p&gt;(RIs) that gather data and provide services to different research communities, all of which can be used&lt;/p&gt;

&lt;p&gt;independently of any specific VRE. There is therefore a need for generic VREs that can be coupled&lt;/p&gt;

&lt;p&gt;with the resources of many different RIs simultaneously, easily customised to the needs of specific&lt;/p&gt;

&lt;p&gt;communities. The resource metadata produced by these RIs rarely all adhere to any one standard&lt;/p&gt;

&lt;p&gt;or vocabulary however, making it difficult to search and discover resources independently of their&lt;/p&gt;

&lt;p&gt;providers without some translation into a common framework. Cross-RI search can be expedited by&lt;/p&gt;

&lt;p&gt;using mapping services that harvest RI-published metadata to build unified resource catalogues, but&lt;/p&gt;

&lt;p&gt;the development and operation of such services pose a number of challenges.&lt;/p&gt;

&lt;p&gt;In this paper, we discuss some of these challenges and look specifically at the VRE4EIC Metadata&lt;/p&gt;

&lt;p&gt;Portal, which uses X3ML mappings to build a single catalogue for describing data products and other&lt;/p&gt;

&lt;p&gt;resources provided by multiple RIs. The Metadata Portal was built in accordance to the e-VRE Reference&lt;/p&gt;

&lt;p&gt;Architecture, a microservice-based architecture for generic modular VREs, and uses the CERIF standard&lt;/p&gt;

&lt;p&gt;to structure its catalogued metadata. We consider the extent to which it addresses the challenges of&lt;/p&gt;

&lt;p&gt;cross-RI search, particularly in the environmental and earth science domain, and how it can be further&lt;/p&gt;

&lt;p&gt;augmented, for example to take advantage of linked vocabularies to provide more intelligent semantic&lt;/p&gt;

&lt;p&gt;search across multiple domains of discourse.&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.1016/j.future.2019.05.076</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">article</subfield>
  </datafield>
</record>