The team behind Trismegistos is proud to present the new Data Services portal, developed in the Linked Open Data framework of DARIAH-BE and CLARIAH-VL. On this portal you can find a general overview of the services we offer. We've made a set of public methods, which can be used by researchers, students, webdesigners and so forth who wish to work with our data. We offer you open access to our data on a CC BY-SA 4.0 license.
What data is on offer? Well, we're glad you ask. Here's a short overview of the open services, you can find a more detailed explanation in the documentation page of each endpoint.
The TexRelations Matcher is a cross-matching tool to find links to other projects with information about Ancient World texts; this API offers you a JSON, XML and URI-based JSON response in no time and helps you identify related records of 79 other projects. You can use the TM Text ID or any ID coming from one of our partners and find all the other IDs of that same text curated by one of those other projects.
The GeoRelations Matcher is a tool based on the same principle as the TexRelations Matcher. It enables you to find other place IDs from partner projects based on any ID from another partner project. This API offers you a JSON, XML and URI-based JSON response in no time. This is a great way to help you organize your own place IDs and look for lacking information in your own database.
At this moment we offer links to 20 other projects.
This is to be considered a supplementary service to the GeoResponder tool, making the TM Geo data available for linked data projects. There are two separate endpoints: www.trismegistos.org/dataservices/rdf/geo/index.php and www.trismegistos.org/dataservices/rdf/geo/extended_index.php. Both endpoints take an argument
?id= followed by the TM Geo ID you're interested in. For convenience this endpoint is also accessible directly via the TM Places portal. Simply go the stable URI of the place you're interested in and append /rdf or /rdfe to the url. These will take you to the default RDF or extended RDF endpoint.
e.g. the stable URI for Karyanda is: www.trismegistos.org/place/3409 The TM Geo ID is thus 3409. Using this ID to access the RDF directly can be done via: www.trismegistos.org/dataservices/rdf/geo/index.php?id=3409; the direct access to the extended RDF is: www.trismegistos.org/dataservices/rdf/geo/extended_index.php?id=3409. Both of these endpoints are also easily accessible through appending
/rdf for the default RDF response or
/rdfe for the extended RDF response. To follow up on the example of Karyanda: the default RDF can be viewed at www.trismegistos.org/place/3409/rdf; whereas the extended response can be viewed at www.trismegistos.org/place/3409/rdfe.
The extended RDF response (rdfe) offers more data compared to the default RDF response. It outputs text attestations and provides information about each individual attestation of the requested place, and if available it will provide a similar response for authors.
Warning: All of these responses are made server-side, so places that have been attested in thousands of texts take more time to serialize. To keep response times low, the server is configured to only process the first 1000 texts and the first 1000 authors related to a place. Keep this in mind when processing the responses.
Matching record by record is too slow for you? No problem, we've got you covered! For large scale projects that need a customized dump file of TM Places we recommend them to use the Geographical data dump tool. Users can customize the response fields by simply checking the data that interests you and choose a CSV or JSON response format. This is the ideal starting point to import our data in another database. Just be sure to follow the CC BY-SA guidelines.
This tool will show you a JSON response for the TM Person ID you're looking for.
We also developed an online endpoint to retrieve person-related data in the RDF format. The default data available at www.trismegistos.org/dataservices/rdf/per/index.php. This endpoint takes one mandatory argument
?id= followed by the TM Per_ID you're interested in. Optionally you can provide a secondary argument to control file-downloading behavior. By appending
&dl=0 you ask your browser to display the file, whereas providing
&dl=1 will ask your browser to download the file directly. This behaviour depends on your browser and how certain functionalities are implemented, as such not every browser behaves in this way. Currently only Mozilla Firefox behaves as intended.