| API | XML | JSON | Turtle |
|---|---|---|---|
| getNuds | NUDS/XML | ||
| getRDF | RDF/XML |
Get an aggregated NUDS/XML serialization based on the recordIds in the collection.
Webservice Type : REST
Url: https://coins.warwick.ac.uk/token-types/apis/getNuds?
Parameters : identifiers (recordIds divided by a pipe '|')
Result : returns NUDS/XML records aggregated in a nudsGroup root element.
Example: apis/getNuds?identifiers=dissard_1905.1093|TURS797|TURS892
Get an aggregated RDF/XML serialization based on the recordIds in the collection.
Webservice Type : REST
Url: https://coins.warwick.ac.uk/token-types/apis/getRDF?
Parameters : identifiers (recordIds divided by a pipe '|')
Result : returns RDF/XML triples for given objects/hoards/coin types.
Example: apis/getRDF?identifiers=dissard_1905.1093|TURS797|TURS892
Coin type corpora published in Numishare enable reconciliation of reference identifiers to URIs for coin types and subtypes. Unlike the OpenRefine reconciliation API in Nomisma, Numishare-oriented APIs support additional query properties (e.g., for rulers, mints, and denominations) to further refine queries and enhance accuracy of matches.
All API responses are in JSON. Please see the API documentation and usage documentation for more details about general usage of reconciliation services in OpenRefine.
For specific insights and recommended workflows, please read Numishare supports OpenRefine reconciliation APIs for OCRE, PELLA, and CRRO.
Service URI:https://coins.warwick.ac.uk/token-types/apis/reconcile
Numishare supports the following reconciliation services for OpenRefine:
Presently, the facet fields for a given type corpora are supported as properties, both for exact matching and free-text. It is recommended to reconcile additional property fields in your source spreadsheet (mints, rulers) to Nomisma first, and then use these reconciled preferred labels for exact matching property searches for coin type reconciliation.
Numishare supports delivery of individual records in a variety of models and serializations through both REST and content negotiation. Content negotiation (with the accept header) requests should be sent to the URI space https://coins.warwick.ac.uk/token-types/id/. Requesting an unsupported content type will result in an HTTP 406: Not Acceptable error.
| Model | REST | Content Type |
|---|---|---|
| HTML | https://coins.warwick.ac.uk/token-types/id/{$id} | text/html |
| NUDS/XML | https://coins.warwick.ac.uk/token-types/id/{$id}.xml | application/xml |
| KML | https://coins.warwick.ac.uk/token-types/id/{$id}.kml | application/vnd.google-earth.kml+xml |
| RDF/XML | https://coins.warwick.ac.uk/token-types/id/{$id}.rdf | application/rdf+xml |
| Turtle | https://coins.warwick.ac.uk/token-types/id/{$id}.ttl | text/turtle |
| JSON-LD | https://coins.warwick.ac.uk/token-types/id/{$id}.jsonld | application/ld+json |
| geoJSON | https://coins.warwick.ac.uk/token-types/id/{$id}.geojson | application/vnd.geo+json |
Search results (the browse page) are returned in HTML5, but Numishare supports Atom and RSS via REST, as well as Atom and raw Solr XML via content negotiation of the browse page URL, https://coins.warwick.ac.uk/token-types/results. The REST-based Atom feed sorts by the Lucene syntax 'timestamp desc' by default, but the sort parameter may be provided manually to alter the default field and order.
| Model | REST | Content Type |
|---|---|---|
| HTML | https://coins.warwick.ac.uk/token-types/results | text/html |
| Atom | https://coins.warwick.ac.uk/token-types/feed/ | application/atom+xml |
| RSS | https://coins.warwick.ac.uk/token-types/apis/search?q=*:*&format=rss | N/A |
| Solr/XML | N/A | application/xml |
Search results may also be serialized into geographic models when relevant, for example to show the mints, findspots, or subjects related to the current query. Results are made available in KML and geoJSON.
Data dumps conforming to the Nomisma ontology are linked on the index page. At present, these files are only available in RDF/XML.
Data dumps conforming to the Pelagios 3 model are linked on the index page. At present, these files are only available in RDF/XML.