Humanities' Asset Management System

GAMS OAI-PMH Documentation

Vera Maria Charvat & Gerlinde Schneider

Last Update: 2021-10-17
Handle: hdl:11471/521.1.2

Table of contents
  1. GAMS OAI-PMH Documentation
    1. Base URL
    1. Metadata formats
    1. How to use our prefixes?
    1. Services

GAMS OAI-PMH Documentation

OAI-PMH (Open Archives Initiative Protocol for Metadata Harvesting) is a widely used protocol for harvesting metadata. In order to systematically harvest our metadata, or integrate it into your own contexts, you may use our interface and query it according to the rules of the protocol. The protocol follows the OAI-PMH specifications.
All our metadata is licensed under the CC BY-NC 4.0.

Base URL

Our provider is available under the following Base URL:

Metadata formats

The metadata for each file in our repository is available in several formats.
You can get our full list of metadata formats by adding ?verb=ListMetadataFormats to the Base URL - like this:

At this time we support the following 4 formats (= OAI-PMH prefixes) for our metadata: oai_dc, oai_cmdi-tei, oai_europeana and oai_edm.

  • oai_dc (Dublin Core):
    In order to ensure interoperability, the OAI-PMH protocol requires that archives must map their metadata according to Dublin Core, a recommended W3C standard, as a lowest common denominator. For this purpose the metadataPrefix oai_dc, as well as the URL for the metadata schema - - are strictly reserved by the protocol.
    The "Dublin Core Metadata Element Set" (or short: "Dublin Core", ISO 15836-1:2017) is a set of standardized terms, formulated by the Dublin Core Metadata Initiative (DCMI), which provide minimal but essential metadata for each record. It consists of the fifteen "core" elements, which are also required by the OAI-PMH protocol: Contributor, Coverage, Creator, Date, Description, Format, Identifier, Language, Publisher, Relation, Rights, Source, Subject, Title, Type.
    Meanwhile the original Dublin Core Metadata Element Set is part of the bigger DCMI Metadata Terms (ISO 15836-2:2019), where it can be found under the reserved namespace

    		<oai_dc:dc xmlns:oai_dc="" 
    			<dc:title>Alexander Rollett. Seine Welt in Briefen 1844-1903: Korrespondenz des Jahres 1906</dc:title>
    			<dc:publisher>Centre for the History of Science, University of Graz</dc:publisher>
    			<dc:relation>Alexander Rollett Briefedition</dc:relation>
    			<dc:date>1906 VI 4</dc:date>
    			<dc:rights>Resource licensed under Creative Commons BY-NC-SA 4.0</dc:rights>
    The original live example can be retrieved via this link:
  • oai_cmdi-tei (CMDI-TEI):
    Component MetaData Infrastructure (CMDI) is a metamodel which provides a well-defined framework with flexible components in order to allow integrating existing metadata schemas. For the metadata included in our projects' TEI Headers, the information is mapped into a CMDI-TEI profile.
    The CMDI specification is developed and published by CLARIN.

    		<cmd:CMD CMDVersion="1.2" 
    				<cmd:MdCreator>Zentrum für Informationsmodellierung</cmd:MdCreator>
    				<cmd:MdCollectionDisplayName>GAMS Repository</cmd:MdCollectionDisplayName>
    					<cmd:ResourceProxy id="aaif.spapcrdiam-landing_page">
    						<cmd:ResourceType mimetype="text/html">LandingPage</cmd:ResourceType>
    					<cmd:ResourceProxy id="aaif.spapcrdiam-tei">
    						<cmd:ResourceType mimetype="application/xml">Resource</cmd:ResourceType>
    				<cmdp:teiHeader type="text">
    						<cmdp:title>Corpus of Spanish Adjective-Adverbs and Prepositional Phrases in CORDIAM</cmdp:title>
    						<cmdp:date when="2020">2020</cmdp:date>
    							<cmdp:orgName>Institut für Romanistik, Karl-Franzens-Universität Graz </cmdp:orgName>
    							<cmdp:orgName>Zentrum für Informationsmodellierung - Austrian Centre for Digital Humanities, Karl-Franzens-Universität Graz</cmdp:orgName>
    							<cmdp:licence target="">Creative Commons BY 4.0</cmdp:licence>
    							<cmdp:language ident="spa">Spanish</cmdp:language>
    							<cmdp:p>Corpus of Spanish adjective-adverbs and prepositional phrases in American Spanish from 16th to 19th century, collected from the CORDIAM database.</cmdp:p>
    The original live example can be retrieved via this link:
  • oai_europeana (Europeana Semantic Elements):
    Europeana Semantic Elements (ESE) is the predecessor format of the Europeana Data Model (EDM).
    For historical and practical reasons we still provide both formats - ESE as oai_europeana and EDM as oai_edm (see below).

    		<europeana:record xmlns:europeana="" 
    			<dc:title>Cooking Recipe for Veal or chicken puree, black</dc:title>
    			<dc:contributor>Austrian Science Fund (FWF): I 3614</dc:contributor>
    			<dc:publisher>Centre for Information Modelling - Austrian Centre for Digital Humanities, University of Graz</dc:publisher>
    			<dc:relation>Cooking Recipes of the Middle Ages</dc:relation>
    			<dc:rights>Resource licensed under Creative Commons BY-NC 4.0</dc:rights>
    			<europeana:provider>EuropeanaLocal Austria</europeana:provider>
    			<europeana:dataProvider>University of Graz</europeana:dataProvider>
    The original live example can be retrieved via this link:
  • oai_edm (Europeana Data Model):
    The Europeana Data Model (EDM) was developed to gather, enrich and interlink metadata of various Cultural Heritage Objects (CHOs) and map them into a unified data model.
    EDM is based on the approaches of Linked Open Data (LOD) and the Semantic Web and provides metadata enrichment and aggregation from third party resources.

    		<rdf:RDF xmlns:rdf="" 
    			<edm:ProvidedCHO rdf:about="">
    				<dc:title xml:lang="de">Jahrrechnung Stadt Basel 1571/1572</dc:title>
    				<dc:type xml:lang="de">Handschrift</dc:type>
    				<dc:type xml:lang="en">manuscript</dc:type>
    				<dc:type rdf:resource="" />
    				<dc:identifier>StABS, Finanz H, 128.1</dc:identifier>
    				<dcterms:spatial rdf:resource="" />
    				<dcterms:isPartOf xml:lang="de">Jahrrechnungen der Stadt Basel</dcterms:isPartOf>
    				<dc:rights rdf:resource="" />
    			<edm:Place rdf:about="">
    				<skos:prefLabel xml:lang="de">Basel</skos:prefLabel>
    			<edm:WebResource rdf:about="">
    				<dc:creator xml:lang="en">Department of History, University of Basel</dc:creator>
    				<dc:creator xml:lang="de">Departement Geschichte, Universität Basel</dc:creator>
    				<dc:creator rdf:resource="" />
    				<dc:creator xml:lang="en">Centre for Information Modelling - Austrian Centre for Digital Humanities, University of Graz</dc:creator>
    				<dc:creator xml:lang="de">Zentrum für Informationsmodellierung - Austrian Centre for Digital Humanities, Karl-Franzens-Universität Graz</dc:creator>
    				<dc:creator rdf:resource="" />
    				<dc:description xml:lang="en">Funded by: University of Basel</dc:description>
    				<dcterms:isPartOf rdf:resource="" />
    				<edm:rights rdf:resource="" />
    				<owl:sameAs rdf:resource="" />
    			<ore:Aggregation rdf:about="">
    				<edm:aggregatedCHO rdf:resource="" />
    				<edm:dataProvider>University of Graz</edm:dataProvider>
    				<edm:hasView rdf:resource="" />
    				<edm:isShownAt rdf:resource="" />
    				<edm:provider>EuropeanaLocal Austria</edm:provider>
    				<edm:rights rdf:resource="" />
    			<edm:WebResource rdf:about="">
    				<svcs:has_service rdf:resource="" />
    			<svcs:Service rdf:about="">
    				<dcterms:conformsTo rdf:resource="" />
    				<doap:implements rdf:resource="" />
    The original live example can be retrieved via this link:

How to use our prefixes?


Our data is harvested by the following services:

If you harvest our server please let us know, so we can add you to this list.