About Arachne Interfaces
In order to guarantee highest data interoperability the Arachne database provides all its data mapped to several metadata formats, based on the OAI PMH (Open Archives Initiative Protocol for Metadata Harvesting) standard interface. This allows you to request all of the Arachne content either as single or as mass result.
In generell this interface is meant to be for machine communication only, meaning that one computer is harvesting requested data from another computer by using the protocol's specifications. (As a matter of course you also can use the interface 'by hand'.)
The interface protocol consists of 6 different request verbs, each delivering specific information:
- Identify
- ListMetadataFormats
- ListSets
- ListRecords
- ListIdentifiers
- GetRecord
Identify, ListMetadataFormats and ListSets will give you information about the implementation, whereas ListRecords, ListIdentifiers and GetRecord will deliver archived data itself.
Please check the detailed description of the Arachne OAI PMH interface at our laboratory's website:
http://codarchlab.uni-koeln.de/index.php?category=interface&call=about_oai&typ=static
If you are interested in detailed information about the OAI PMH interface, please check:
http://www.openarchives.org/OAI/openarchivesprotocol.html
Arachne data represented in Dublin Core
Dublin Core is the agreed minimal standard convention of any OAI PMH interface, describing data with a reduced set of terms. While on the one hand this means loosing most of the semantic information within the data, the simplicity of this metadata format on the other hand results in a huge amount of repositories as well as harvesters all around the world.
If you are interested in Dublin Core, please check:
http://en.wikipedia.org/wiki/Dublin_Core
http://dublincore.org/
Arachne OAI PMH CidocCRM
In order to preserve the semantic information within one database object and its context to related database objects (such as places, dates or pictures and vice versa), the Arachne OAI PMH interface delivers data request mapped to Cidoc CRM. This metadata standard can express relations between information given to one object, allowing to set these in context to another by nesting statements. For semantic reasons relationships are expressed by referring identifier since this allows dedicated request of all relatives.
If you are interested in Cidoc CRM, please check:
http://www.cidoc-crm.org/
http://cidoc-crm.gnm.de/wiki/Hauptseite
http://erlangen-crm.org/
Right now, out of 33 content relevant database categories with approx. 1150 fields there are 23 mapped into Dublin Core and 17 mapped into Cidoc CRM.
You can check on the ongoing progress of mapping on our laboratory's website:
http://codarchlab.uni-koeln.de/index.php?category=skulpturennetzwerk&call=mappingstatus&typ=static
Arachne OAI PMH Raw XML data
We also deliver request results as raw XML data, reflecting the actual storage of an object within the database. While we limited the Cidoc CRM statement about the relationship between the requested object and other stored objects to the identifier for semantic reasons, this raw XML output shows all information of the relativs, nested as children.
Example: Basilica Aemilia
Arachne database:
http://arachne.uni-koeln.de/item/bauwerk/2100062
Arachne OAI PMH Dublin Core (please right click to obtain XML sourcecode):
http://arachne.uni-koeln.de:8080/OaiPmhServlet/oai-pmh.xml?verb=GetRecord&identifier=oai:arachne.uni-koeln.de:bauwerk/2100062&metadataPrefix=oai_dc
Arachne OAI PMH Cidoc CRM (please right click to obtain XML sourcecode):
The Basilica Aemilia object:
http://arachne.uni-koeln.de:8080/OaiPmhServlet/oai-pmh.xml?verb=GetRecord&identifier=oai:arachne.uni-koeln.de:bauwerk/2100062&metadataPrefix=cidoc_crm
Related objects (selection):
http://arachne.uni-koeln.de:8080/OaiPmhServlet/oai-pmh.xml?verb=GetRecord&identifier=oai:arachne.uni-koeln.de:bauwerksteil/1&metadataPrefix=cidoc_crm
http://arachne.uni-koeln.de:8080/OaiPmhServlet/oai-pmh.xml?verb=GetRecord&identifier=oai:arachne.uni-koeln.de:marbilder/574573&metadataPrefix=cidoc_crm
Arachne OAI PMH raw XML output (please right click to obtain XML sourcecode):
http://arachne.uni-koeln.de:8080/OaiPmhServlet/oai-pmh.xml?verb=GetRecord&identifier=oai:arachne.uni-koeln.de:bauwerk/2100062&metadataPrefix=origin
Arachne Book representation in TEI P5 and mets/mods metadata standard
ENRICH was the first Arachne project whose TEI-P5-data was harvested via OAI PMH. The ENRICH project is the joint digital manuscript library of the European Union, financed from 2007 to 2009 by the European Commission under the eContent+-programme. The project provides seamless access to more than 4'500'000 pages of manuscripts and early printed books, whereof all books stored in the Arachne database is a part of.
The harvesting works with all books in the Arachne databases, incorporated as data sets into the (so called) Manuscriptorium database and presented on their website, as well as integrated via their own interface into EUROPEANA.
In order to integrate Arachne books into the DFG Viewer all books subsequently are transformed from TEI P5 into mets/mods on the fly.
Example:
"Collection de Sculptures Antiques Grecques, et Romaines, Trouvees a Rome dans les ruines des Palais de Neron, et de Marius" by Lambert Sigisbert Adam
This is the book representation on the Arachne database website:
http://arachne.uni-koeln.de/books/Adam1755
Arachne TEI Viewer:
http://arachne.uni-koeln.de/arachne/hilfsprojekte/teiEditor/TeiEditor.html?adam_collectionpolignac
This is the OAI PMH interface delivery of the TEI P5 and mets/mods mapping of that title
This is the computed result of the harvested data on different websites
Manuscriptorium database:
http://beta.manuscriptorium.com/apps/main/en/index.php?request=show_tei_digidoc&virtnum=0&client=
Please check the detailed description of the Arachne OAI PMH Book interface at our laboratory's website:
http://codarchlab.uni-koeln.de/index.php?category=interface&call=books&typ=static
For more information about the ENRICH project, the Manuscriptorium database and the DFG Viewer see:
http://enrich.manuscriptorium.com
http://beta.manuscriptorium.com
http://dfg-viewer.de
Arachne Atom Feeds
As a low level access we offer an Atom-based data interface. The widely accepted Atom Syndication format provides a relatively simple approach to interoperability and is easily accessible through many different sorts of clients.
Our service allows querying our full-text index and provides paged feeds of the search results. These results include the title, the persistent identifier and location, and the date of the last modification and therefore are independent of any complex metadata format.
In the near future the interface will be expanded to include several extensions described in the Open Search Standard, such as relevance scoring and geospatial and time-based query options.
The Atom Interface can be accessed at the URL:
http://arachne.uni-koeln.de:8080/solr/atom/
Example: Basilica Aemilia
http://arachne.uni-koeln.de:8080/solr/atom/?q=basilica+aemilia
Pelagios Arachne cooperation Results
"PELAGIOS stands for 'Pelagios: Enable Linked Ancient Geodata In Open Systems' - its aim is to help introduce Linked Open Data goodness into online resources that refer to places in the Ancient World." see
In cooperation with the Pelagios Project Arachne places where cross referenced with Pleiades in Linked Open Data way. The reference dataset that is used by Pelagios is Pleiades. The Dataset that has been created for this Purpose is an series of RDF triples using the OAC standard.
These OAC triples describe the connections between Arachne Places to Pleiades Places and Arachne Objects to Pleiades Places.
To see how this has been achieved read the Pelagios blog entries 1, 2 .
