D-Net

<style>

table, th, td {

    border: 1px solid black;

    border-collapse: collapse;

}

th, td {

    padding: 5px;

    text-align: left;

}

    table>thead>tr>th, .table>thead>tr>th, table>tbody>tr>th, .table>tbody>tr>th, table>tfoot>tr>th, .table>tfoot>tr>th, table>thead>tr>td, .table>thead>tr>td, table>tbody>tr>td, .table>tbody>tr>td, table>tfoot>tr>td, .table>tfoot>tr>td {

    border: 1px solid black;

}

</style>

            <div class="card z-depth-2" style="padding-top: 10px ;">

                    <h4 class="center-align"><b>ABOUT SCHOLEXPLORER: THE OPENAIRE’S SCHOLIX HUB</b></h4>

                    <b>Scholix</b>  The goal of the Scholix initiative is to establish a high level interoperability

                    framework for exchanging information about the links between scholarly literature and data.

                    It aims to enable an open information ecosystem to understand systematically what data underpins

                    literature and what literature references data. Scholix maintains an evolving set

                    of<a href="http://www.scholix.org">Guidelines</a> consisting of:

                    (i) an information model (conceptual definition of what is a Scholix scholarly link),

                    (ii) a link metadata schema (set of metadata fields representing a Scholix link),

                    and (iii) a corresponding XML and JSON schema.

                </div>

                <div class="row" style="text-align: center;">

                <div class="row" style="text-align: justify; text-justify: inter-word;  margin-top: 10px">

                    <b>How to expose Scholix data from this hub</b> Scholexplorer harvests scholarly links

                    (i.e. collects metadata records about links from public APIs) from the Scholix

                    compatible sources and from DataCite compatible sources. The main sources collected

                    by the service are listed in Table 1.

                </div>

                <div class="row" style="font-size: 12px; margin-top: 10px">

                    <b>Table 1.</b> Scholexplorer: data sources. Legenda: Hub (aggregator of sources that exposes Scholix links), Source (data source that exposes Scholix links)

                <div class="row" style="text-align: justify;">

                   <table class="table">

                       <thead>

                       <tr>

                           <th scope="col">Data Source</th>

                           <th scope="col">Type of source</th>

                       </tr>

                       <tr>

                           <td>DataCite from the DataCite OAI-PMH <a href="https://oai.datacite.org/"> end point</a></td>

                           <td>Hub: a <i>provider</i> of links <i>published</i> by data repositories; links are between datasets (DOIs) and articles (DOIs, handles, URLs) or datasets (DOI)</td>

                       </tr>

                       <tr>

                           <td>CrossRef from the Event Data <a href="https://www.crossref.org/services/event-data/"> end point</a></td>

                           <td>Hub: a <i>provider</i> of links <i>published</i> by publishers; links are between articles (DOIs) and datasets (DOI, accession numbers, URLs)</td>

                       </tr>

                       <tr>

                           <td>Data repositories that are not yet DataCite members</td>

                           <td>Source: a <i>publisher</i> of links between datasets (no DOI) and articles</td>

                       </tr>

                        <tr>

                           <td>Thematic publishers, e.g. Europe PMC</td>

                           <td>Source: a <i>publisher</i> of links between articles and accession numbers</td>

                       </tr>

                           <td>Dataset databases, e.g. ENA</td>

                           <td>Source: a <i>publisher</i> of links between accession numbers of sequences and articles</td>

                       </tr>

                   </table>

                </div>

                <div class="row" style="text-align: justify; text-justify: inter-word">

                    Data sources willing to include the links they publish or provide within Scholexplorer have two options:

                    <ul>

                        <li>

                            Become Scholix-compliant and register to become a Scholexplorer data source;

                        </li>

                        <li>

                            Become a data source aggregated by any of the hubs above.

                        </li>

                    </ul>

            </div>

    </div>

        <div class="col-lg-8 col-lg-offset-2">

                    The Scholix Swagger API allows clients to run REST queries over the Scholexplorer index

                    in order to fetch links matching given criteria. In the current version, clients can search for:

                        <li> Links whose source object has been <b>published</b> by a given data source ("data source as publisher");</li>

                        <li> Links that were <b>collected</b> from a given data source ("data source as provider"). </li>

                    The APIs are available from <a

                        encoded as JSON Scholix records. JSON (and XML) schema and example records for Scholix links are availabe on

            </div>

        </div>

        <div class="col-lg-8 col-lg-offset-2">

                    <h4 class="center-align"><b>TERMS OF USE and SLA</b></h4>

                    <b>REST APIs:</b> ScholeXplorer's REST APIs are free-to-use (no sign-up needed) by any third-party service. Note that:

                    <ul>

                        <li> The service limits each query to around 10,000 paged results (pages are by default of length 100 and can be navigated via resumption token); </li>

                            every six months </li>

                    </ul>

                    <p>

                    </p>

                    <p>

                        <a href="http://icm.edu.pl/en/centre-of-technology/">data center</a> facilities

                </div>

                    <h4 class="center-align"><b>Faq</b></h4>

                     For any questions you may have about this service please contact <a href="mailto:sandro.labruzzo@isti.cnr.it">Sandro La Bruzzo</a>.

                     <p style="margin-top: 10px">1. <i>How to I expose Scholix links to Scholexplorer (or other services)? Does Scholix recommend an access protocol?</i></p>

                     Scholix does not recommend any specific protocol to expose links, although any community standard is strongly encouraged.

                     As to Scholexplorer, its harvesting layer bulk-collects links from external data sources via public APIs. OAI-PMH is preferable,

                     but also REST APIs can be accepted. The option of “incremental” harvesting is strongly encouraged (not mandatory),

                     for example allowing to search links by "last date of indexing": http://www.mydomain.eu/scholix?lastIndexingDate=yyyy-mm-dd).

                     If Scholix links are returned with all metadata fields, including the optional ones, the APIs above are enough. If instead, the links are limited to

                     the mandatory fields, then a "resolution" API would be required: given a PID of an object the API returns its full metadata record.

                     <p style="margin-top: 10px">2. <i>Which PIDs are compatible with Scholexplorer?</i></p>

                     while in general URLs are not resolved as the variability of the associated resolvers cannot be handled by one service.

                     In principle if your data source is Scholix compliant and provides proprietary PIDs you can include complete Scholix links records in Scholexplorer in two ways:

                     (i) exposing complete Scholix records or (ii) exposing minimally compliant records but making a resolver available,

                     so that Scholexplorer can collect the PID complete records (note: your PIDs will have a specific type, associated by Scholexplorer to your resolver service).

                 </div>

        </div>

    </div>