1
|
<style>
|
2
|
table, th, td {
|
3
|
border: 1px solid black;
|
4
|
border-collapse: collapse;
|
5
|
}
|
6
|
th, td {
|
7
|
padding: 5px;
|
8
|
text-align: left;
|
9
|
}
|
10
|
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 {
|
11
|
border: 1px solid black;
|
12
|
}
|
13
|
</style>
|
14
|
|
15
|
<section style="font-size: 20px; font-family: Lato">
|
16
|
|
17
|
<div class="row">
|
18
|
<div class="col-lg-8 col-lg-offset-2">
|
19
|
|
20
|
<div class="card z-depth-2" style="padding-top: 10px ;">
|
21
|
<div class="row" style="margin-top: 10px; text-align: justify; text-justify: inter-word;">
|
22
|
<h4 class="center-align"><b>ABOUT SCHOLEXPLORER: THE OPENAIRE’S SCHOLIX HUB</b></h4>
|
23
|
<b>Scholix</b> The goal of the Scholix initiative is to establish a high level interoperability
|
24
|
framework for exchanging information about the links between scholarly literature and data.
|
25
|
It aims to enable an open information ecosystem to understand systematically what data underpins
|
26
|
literature and what literature references data. Scholix maintains an evolving set
|
27
|
of<a href="http://www.scholix.org">Guidelines</a> consisting of:
|
28
|
(i) an information model (conceptual definition of what is a Scholix scholarly link),
|
29
|
(ii) a link metadata schema (set of metadata fields representing a Scholix link),
|
30
|
and (iii) a corresponding XML and JSON schema.
|
31
|
</div>
|
32
|
<div class="row" style="text-align: center;">
|
33
|
<img src="static/img/ScholixDM.png" style="max-width: 80%;">
|
34
|
</div>
|
35
|
<div class="row" style="text-align: justify; text-justify: inter-word; margin-top: 10px">
|
36
|
<b>How to expose Scholix data from this hub</b> Scholexplorer harvests scholarly links
|
37
|
(i.e. collects metadata records about links from public APIs) from the Scholix
|
38
|
compatible sources and from DataCite compatible sources. The main sources collected
|
39
|
by the service are listed in Table 1.
|
40
|
</div>
|
41
|
<div class="row" style="font-size: 12px; margin-top: 10px">
|
42
|
<b>Table 1.</b> Scholexplorer: data sources. Legenda: Hub (aggregator of sources that exposes Scholix links), Source (data source that exposes Scholix links)
|
43
|
|
44
|
</div>
|
45
|
<div class="row" style="text-align: justify;">
|
46
|
<table class="table">
|
47
|
<thead>
|
48
|
<tr>
|
49
|
<th scope="col">Data Source</th>
|
50
|
<th scope="col">Type of source</th>
|
51
|
</tr>
|
52
|
<tr>
|
53
|
<td>DataCite from the DataCite OAI-PMH <a href="https://oai.datacite.org/"> end point</a></td>
|
54
|
<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>
|
55
|
</tr>
|
56
|
<tr>
|
57
|
<td>CrossRef from the Event Data <a href="https://www.crossref.org/services/event-data/"> end point</a></td>
|
58
|
<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>
|
59
|
</tr>
|
60
|
<tr>
|
61
|
<td>Data repositories that are not yet DataCite members</td>
|
62
|
<td>Source: a <i>publisher</i> of links between datasets (no DOI) and articles</td>
|
63
|
</tr>
|
64
|
<tr>
|
65
|
<td>Thematic publishers, e.g. Europe PMC</td>
|
66
|
<td>Source: a <i>publisher</i> of links between articles and accession numbers</td>
|
67
|
</tr>
|
68
|
|
69
|
<tr>
|
70
|
<td>Dataset databases, e.g. ENA</td>
|
71
|
<td>Source: a <i>publisher</i> of links between accession numbers of sequences and articles</td>
|
72
|
</tr>
|
73
|
</table>
|
74
|
</div>
|
75
|
<div class="row" style="text-align: justify; text-justify: inter-word">
|
76
|
Data sources willing to include the links they publish or provide within Scholexplorer have two options:
|
77
|
<ul>
|
78
|
<li>
|
79
|
Become Scholix-compliant and register to become a Scholexplorer data source;
|
80
|
</li>
|
81
|
<li>
|
82
|
Become a data source aggregated by any of the hubs above.
|
83
|
</li>
|
84
|
</ul>
|
85
|
|
86
|
</div>
|
87
|
|
88
|
</div>
|
89
|
</div>
|
90
|
</div>
|
91
|
|
92
|
|
93
|
<div class="row">
|
94
|
<div class="col-lg-8 col-lg-offset-2">
|
95
|
|
96
|
<div class="card z-depth-2" style="padding-top: 10px;text-align: justify; text-justify: inter-word">
|
97
|
<div class="row" style="margin-top: 10px">
|
98
|
<h4 class="center-align"><b>HOW TO ACCESS SCHOLIX DATA FROM THIS HUB</b></h4>
|
99
|
The Scholix Swagger API allows clients to run REST queries over the Scholexplorer index
|
100
|
in order to fetch links matching given criteria. In the current version, clients can search for:
|
101
|
<ul>
|
102
|
<li> Links whose source object has a given PID or PID type; </li>
|
103
|
<li> Links whose source object has been <b>published</b> by a given data source ("data source as publisher");</li>
|
104
|
<li> Links that were <b>collected</b> from a given data source ("data source as provider"). </li>
|
105
|
</ul>
|
106
|
The APIs are available from <a
|
107
|
href="https://api.scholexplorer.openaire.eu/v2/ui"> here</a>. The results of queries return lists of links
|
108
|
encoded as JSON Scholix records. JSON (and XML) schema and example records for Scholix links are availabe on
|
109
|
<a href="https://github.com/scholix/schema">GitHub</a>.
|
110
|
</div>
|
111
|
</div>
|
112
|
</div>
|
113
|
</div>
|
114
|
|
115
|
|
116
|
<div class="row">
|
117
|
<div class="col-lg-8 col-lg-offset-2">
|
118
|
<div class="card z-depth-2" style="padding-top: 10px;text-align: justify; text-justify: inter-word">
|
119
|
<div class="row" style="margin-top: 10px">
|
120
|
<h4 class="center-align"><b>TERMS OF USE and SLA</b></h4>
|
121
|
<b>REST APIs:</b> ScholeXplorer's REST APIs are free-to-use (no sign-up needed) by any third-party service. Note that:
|
122
|
<ul>
|
123
|
<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>
|
124
|
<li> Since March 2018 a full <a href="https://zenodo.org/search?page=1&size=20&q=openaire%20scholexplorer%20service%20JSON%20dump"> JSON dump of the service is made available in Zenodo.org</a>
|
125
|
every six months </li>
|
126
|
<li> For unlimited access to the APIs please contact the <a href="mailto:paolo.manghi@isti.cnr.it">service administrators</a> </li>
|
127
|
</ul>
|
128
|
<p>
|
129
|
<b>Metadata license is CC-BY:</b> Scholix metadata records returned by the service can be freely re-used by commercial and non-commercial
|
130
|
partners under CC-BY license, hence as long as OpenAIRE ScholeXplorer is acknowledged as content provider provider.
|
131
|
</p>
|
132
|
<p>
|
133
|
<b>SLA:</b> the service is running in production 24/7 within the OpenAIRE infrastructure premises deployed at the
|
134
|
<a href="http://icm.edu.pl/en/centre-of-technology/">data center</a> facilities
|
135
|
of the <a href="http://icm.edu.pl/en/">Interdisciplinary Centre for Mathematical and Computational Modelling</a> (ICM)
|
136
|
</p>
|
137
|
</div>
|
138
|
<div class="row" style="margin-top: 10px">
|
139
|
<h4 class="center-align"><b>Faq</b></h4>
|
140
|
For any questions you may have about this service please contact <a href="mailto:sandro.labruzzo@isti.cnr.it">Sandro La Bruzzo</a>.
|
141
|
|
142
|
<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>
|
143
|
Scholix does not recommend any specific protocol to expose links, although any community standard is strongly encouraged.
|
144
|
As to Scholexplorer, its harvesting layer bulk-collects links from external data sources via public APIs. OAI-PMH is preferable,
|
145
|
but also REST APIs can be accepted. The option of “incremental” harvesting is strongly encouraged (not mandatory),
|
146
|
for example allowing to search links by "last date of indexing": http://www.mydomain.eu/scholix?lastIndexingDate=yyyy-mm-dd).
|
147
|
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
|
148
|
the mandatory fields, then a "resolution" API would be required: given a PID of an object the API returns its full metadata record.
|
149
|
|
150
|
<p style="margin-top: 10px">2. <i>Which PIDs are compatible with Scholexplorer?</i></p>
|
151
|
Scholexplorer accepts links between any kind of persistent identifiers, including URLs.
|
152
|
The major standard identifiers (e.g. DOIs, PDBs, PMCID, etc) are also resolved to include the complete record information in Scholexplorer,
|
153
|
while in general URLs are not resolved as the variability of the associated resolvers cannot be handled by one service.
|
154
|
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:
|
155
|
(i) exposing complete Scholix records or (ii) exposing minimally compliant records but making a resolver available,
|
156
|
so that Scholexplorer can collect the PID complete records (note: your PIDs will have a specific type, associated by Scholexplorer to your resolver service).
|
157
|
|
158
|
|
159
|
</div>
|
160
|
</div>
|
161
|
</div>
|
162
|
</div>
|
163
|
</section>
|
164
|
|
165
|
|