<?xml version="1.0" encoding="UTF-8"?>
<collection xmlns="http://www.loc.gov/MARC21/slim">
<record>
  <controlfield tag="001">7473</controlfield>
  <controlfield tag="005">20260219160656.0</controlfield>
  <datafield tag="024" ind1="7" ind2=" ">
    <subfield code="a">10.1007/s11207-025-02424-0</subfield>
    <subfield code="2">DOI</subfield>
  </datafield>
  <datafield tag="037" ind1=" " ind2=" ">
    <subfield code="a">SCART-2025-0103</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Mampaey, Benjamin</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">The SOLARNET Virtual Observatory: an effective way to search solar datasets and cross-search with solar events</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2025</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">The volume and diversity of solar physics data have grown exponentially in the last three decades. In view of making solar datasets easily accessible to the scientific community, we have developed the SOLARNET Virtual Observatory (SVO), an IT service that  collects metadata from a large range of solar observational datasets in a common catalog to allow smooth data search and access. It follows the principle of virtual observatories (VO), with a provider layer, a core metadata database, and a user layer. The user layer contains a user friendly web application, Python and IDL libraries, as well as a RESTful API. The SVO allows searching the metadata across all datasets, or within a specific dataset using more precise search conditions.  It also allows to search solar events from the HEK database and to find data that overlap with these events. Data can be previewed from the web application and downloaded. The Python and IDL libraries allow to integrate the SVO data search, and access, to complex data processing pipelines.  On the provider side, datasets are ingested through tailored scripts. Recently, a TAP client layer has been added to the SVO, hence it is possible to populate the SVO automatically with a dataset available as a TAP or EPN-TAP service. We describe the service, user and provider side of the SVO, and illustrate its capabilities with four scientific use-cases. </subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="a">RT/</subfield>
    <subfield code="c">23/</subfield>
    <subfield code="f">SUNRISE</subfield>
  </datafield>
  <datafield tag="594" ind1=" " ind2=" ">
    <subfield code="a">STCE</subfield>
  </datafield>
  <datafield tag="653" ind1="1" ind2=" ">
    <subfield code="a">Data management</subfield>
  </datafield>
  <datafield tag="653" ind1="1" ind2=" ">
    <subfield code="a">Virtual observatories</subfield>
  </datafield>
  <datafield tag="653" ind1="1" ind2=" ">
    <subfield code="a">Open science</subfield>
  </datafield>
  <datafield tag="653" ind1="1" ind2=" ">
    <subfield code="a">FAIR principles</subfield>
  </datafield>
  <datafield tag="653" ind1="1" ind2=" ">
    <subfield code="a">Solar physics</subfield>
  </datafield>
  <datafield tag="653" ind1="1" ind2=" ">
    <subfield code="a">TAP client</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Delouille, Veronique</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Vansintjan, Robbe</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="p">Solar Physics</subfield>
    <subfield code="v">300</subfield>
    <subfield code="n">16</subfield>
  </datafield>
  <datafield tag="856" ind1="0" ind2=" ">
    <subfield code="f">veronique.delouille@ksb-orb.be</subfield>
  </datafield>
  <datafield tag="905" ind1=" " ind2=" ">
    <subfield code="a">published in</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">REFERD</subfield>
  </datafield>
</record>
</collection>