Skip to main content

Frequently Asked Questions.

Find the answers to most of your questions.


How to I expose Scholix links to ScholeXplorer (or other services)? Does Scholix recommend an access protocol?
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": 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.
Which PIDs are compatible with ScholeXplorer?

ScholeXplorer accepts links between any kind of persistent identifiers, including URLs. The major standard identifiers (e.g. DOIs, PDBs, PMCID, etc) are also resolved to include the complete record information in ScholeXplorer, 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).

Haven't found what you're looking for?