ariadne: final report on standards and project registry

ARIADNE–D3.4FinalReportonStandardsandProjectRegistry October2016

Deliverable3.4 2

Aboutthisdocument

Thisdocumentisthe“FinalReportonStandardsandProjectImpact”,acontractualdeliverable(D3.4)

oftheprojectARIADNE-AdvancedResearchInfrastructureforArchaeologicalDatasetNetworkingin

Europe.TheresearchleadingtotheseresultshasreceivedfundingfromtheEuropeanCommunity’s

SeventhFrameworkProgramme(FP7-INFRASTRUCTURES-2012-1)undergrantagreementn°313193.

Partner/sinchargeofthedeliverable: ADS,CNR,DCU,PIN

Authors: AchilleFelicetti(PIN)

CarloMeghini(CNR)

ChristosPapatheodorou(DCU)

JulianRichards(ADS)

Contributions: Withcontributionsbyallprojectpartners

Qualityreview: HollyWrightandJulianRichards(ADS-ArchaeologyDataService)

carolusher

Typewritten Text

Version: 2.0 28 October 2016


Deliverable3.4 3

TableofContents1 Executivesummary.............................................................................................................6

2 Introduction........................................................................................................................7

3 TheARIADNECatalogueDataModel...................................................................................9

3.1 Introduction...............................................................................................................................9

3.2 TheARIADNECatalogue.............................................................................................................9

3.3 UMLDiagramofACDM............................................................................................................10

3.4 DescriptionoftheACDM..........................................................................................................11

3.4.1 ArchaeologicalResource.................................................................................................................12

3.4.2 DataResource.................................................................................................................................13

3.4.3 TextualDocument...........................................................................................................................17

3.4.4 LanguageResource.........................................................................................................................19

3.4.5 MetadataSchema...........................................................................................................................21

3.4.6 Distribution.....................................................................................................................................23

3.4.7 DataFormat....................................................................................................................................24

3.4.8 DBSchema......................................................................................................................................25

3.4.9 EncodingLanguage..........................................................................................................................26

3.4.10DigitalObjectDesc...........................................................................................................................26

3.4.11MetadataRecord............................................................................................................................27

3.4.12MetadataElement..........................................................................................................................27

3.4.13TemporalRegion.............................................................................................................................29

3.4.14SpatialRegion..................................................................................................................................31

3.4.15MetadataAttribute.........................................................................................................................31

3.4.16Version...........................................................................................................................................32

3.4.17AriadneConcept..............................................................................................................................32

3.4.18Licence............................................................................................................................................33

3.4.19Service............................................................................................................................................34

3.4.20foaf:Agent.......................................................................................................................................37

4 TheARIADNERegistry.......................................................................................................39

4.1 ARIADNERegistryContent.......................................................................................................39

4.2 ARIADNERegistryMappings....................................................................................................39

4.3 ContentandMappingStatistics...............................................................................................40

5 StandardisationandMappinginARIADNE........................................................................41

5.1 ACDMMappings.......................................................................................................................41

5.2 AATMappings..........................................................................................................................42

5.3 PeriodOMappings....................................................................................................................45

5.3.1 Definitions......................................................................................................................................45

5.3.2 Identifiers.......................................................................................................................................46

5.3.3 DataSerialization...........................................................................................................................46

5.3.4 UserInterface.................................................................................................................................46

5.3.5 ImplementationbyARIADNE.........................................................................................................46

6 ACDMEncoding:DiagramsandSchemas...........................................................................48


Deliverable3.4 4

6.1 Diagrams..................................................................................................................................48

6.1.1 Service............................................................................................................................................48

6.1.2 Vocabulary......................................................................................................................................48

6.1.3 MetadataSchema...........................................................................................................................49

6.1.4 AriadneConcept..............................................................................................................................49

6.2 Templates.................................................................................................................................50

6.2.1 Generaltemplateforallservices...................................................................................................50

6.2.2 Additionaltemplateforstandaloneservices.................................................................................51

6.2.3 Additionaltemplateforwebservices............................................................................................52

6.2.4 AdditionalTemplateforinstitutionalservices...............................................................................52

6.2.5 MappingofADSrecordstoACDMinXSLT.....................................................................................52

6.2.6 MappingofFastiOnline/AIACrecordstoACDMinXSLT...............................................................56

7 ARIADNEMappingDetails.................................................................................................60

7.1 ADSdatasets............................................................................................................................60

7.1.1 ADSCollectionlevelrecordmappings............................................................................................60

7.1.2 ADSMappingsforindividualtextualdocuments...........................................................................61

7.1.3 ADSterminologicalmappings........................................................................................................62

7.2 AIAC–FastiOnline...................................................................................................................62

7.2.1 FastiTerminologyMappings..........................................................................................................65

7.3 ARHEO......................................................................................................................................66

7.4 ARUP-CASdatabase.................................................................................................................71

7.5 CSIC-Incipit.............................................................................................................................73

7.6 CyprusInstitute-STARCrepository.........................................................................................74

7.6.1 STARCmetadataschema................................................................................................................75

7.6.2 CustomizedLIDO............................................................................................................................75

7.6.3 CyInscriptionmetadataschema.....................................................................................................75

7.6.4 MappingstoCIDOC-CRM...............................................................................................................78

7.6.5 CyIservicesforARIADNE................................................................................................................78

7.7 DAIdatasets.............................................................................................................................78

7.7.1 CIDOCCRMmapping......................................................................................................................81

7.7.2 iDAI.objectsArachne......................................................................................................................81

7.7.3 iDAI.vocab......................................................................................................................................81

7.7.4 IDAI.gazetteer.................................................................................................................................82

7.7.5 DAIsubjects....................................................................................................................................82

7.8 DANSdatasets..........................................................................................................................82

7.8.1 DCCDtoplevelcollection...............................................................................................................82

7.8.2 DCCDTRiDaSdatasets....................................................................................................................86

7.8.3 DCCDtemporalentities..................................................................................................................91

7.8.4 DCCDspatialentities......................................................................................................................91

7.8.5 DCCDservicesandschemasintheregistry....................................................................................92

7.8.6 EASYtoplevelcollection................................................................................................................92

7.8.7 EASYarchaeologicaldatasets.........................................................................................................96

7.8.8 EASYtemporalentities...................................................................................................................99

7.8.9 EASYspatialentities.....................................................................................................................100

7.8.10EASYservicesandschemas..........................................................................................................101


Deliverable3.4 5

7.9 Discoverydatasets.................................................................................................................102

7.9.1 DataResource–Collection...........................................................................................................102

7.9.2 ArchaeologicalSurveyofIreland(ASI).........................................................................................103

7.9.3 3DIconsProject-CARARE............................................................................................................104

7.9.4 WODAN,MAPPINGDEATHandTIIExcavationReports...............................................................104

7.9.5 IrishMonumentsvocabularyAATmapping.................................................................................104

7.9.6 PeriodOmappings........................................................................................................................106

7.10INRAP.....................................................................................................................................106

7.10.1Terminologicalresources.............................................................................................................108

7.11MiBACT-ICCUinformation......................................................................................................108

7.11.1PICOmappings.............................................................................................................................108

7.11.2Terminologicalservices................................................................................................................116

7.12MiBACT–SITAR......................................................................................................................116

7.12.1CIDOCCRMMapping....................................................................................................................119

7.13MNM-NOKdatabase..............................................................................................................119

7.14NIAM-BASdatabase...............................................................................................................121


7.14.2PeriodOmappings........................................................................................................................123

7.15OEAWdatabases....................................................................................................................123



7.16SNDdatasets..........................................................................................................................126

7.16.1AATmappings...............................................................................................................................128


7.17ZRCSAZU:...............................................................................................................................129

7.17.1ZRCZbivadatabase......................................................................................................................129

7.17.2ZRCSAZU:Arkasdatabase............................................................................................................130

8 Conclusions.....................................................................................................................131


Deliverable3.4 6

1 Executivesummary

Thisdocumentisadeliverable(D3.4)oftheprojectARIADNE-AdvancedResearchInfrastructureforArchaeological Dataset Networking in Europe, funded under the European Community’s Seventh

Framework Programme. This document presents a significant update to D3.1 “Initial report on

standardsandontheregistry”.This isadeliverableofARIADNEWP3,whichwasmainlyconcerned

withthecreationofaregistry for integrationof informationconcerning legacymetadata,standard

schemas, servicesand terminological toolspertaining to thearchaeologicaldomain. The registry is

conceivedasanintegratedcentralrepositoryabletodescribedatasets,todriveresourcediscovery

operations.

Thisdeliverable iscomprisedofseveralsections,whichdetail thestructurethedatamodel for the

registry(Section3),anoverviewoftheregistrycontentandmappings(Section4)andthestandards

used to create thesemappings (Section 5). These standards include the ARIADNE Catalogue Data

Model (ACDM), theuseof theGettyArtandArchitectureThesaurus (AAT)asasinglestandard for

subject for all partners, andparticipation in thePeriodOproject,wherepartners contributed their

temporal terms relative to place. This section is followed by the specific encoding diagrams and

schemasdescribingthestructureoftheregistryandthemetadataitholds,alongwiththetemplates

usedbypartnerstocreatetheirmappings(Section6).

Theremaininghalfofthisdeliverable(Section7)details thespecificprocesspartnersundertookto

map their metadata and have it ingested into the ARIADNE portal. Each partner faced different

challengesandwentthroughadifferentprocess inordertoachievethis importantstep. Inseveral

casesthisworkwasseenasanopportunitytointroducestandardsintotheirorganisationthatwere

notinusebefore,showingtheimportanceofbestpracticeknowledgetransferwithintheproject.In

otherinstancesthesheersizeanddiversityofdataheldbyapartnerwasthemainchallenge.During

the process of making their metadata ready for inclusion within the registry, and mapping that

metadata to appropriate schemas, etc. partners looked closely at their workflows and in several

instancesupdatedtheirpractice.

Out of this joint problem solving, two key innovations emerged. First was how to deal with the

myriadsubjecttermsinuseacrossEurope,andthemanylanguages.Thisrequiredacreativesolution

tobedevelopedwithin theproject,which resulted in thedecision tomapallpartnersubject term

lists,inanylanguagetotheAAT.Byfocussingspecificallyonmappingtoconceptsratherthanterms,

and using the knowledge of the domain experts within each of the content-providing partners,

subject-based searches across languages are nowpossible. Secondwas how to dealwith time, as

whenisalwaysrelativetowhereinarchaeology.Inanattempttohelpsolvethisissue,collaboration

with the US-based PeriodO project was considered to be the best solution, and each partner

contributedtheirperiodtermstotheproject,sothattheycanbeincorporatedbackintoARIADNEas

LinkedData,alongside the restof the temporalattributionsheldby theproject.Section7outlines

notonlythemappingtotheACDMandtheingestionprocesscarriedoutbyeachpartner,buttheir

participationintheseimportantinitiatives,creatingfurtherresourcesforthearchaeologicaldomain.


Deliverable3.4 7

2 Introduction

Thisdocumentisadeliverable(D3.4)oftheprojectARIADNE-AdvancedResearchInfrastructureforArchaeological Dataset Networking in Europe that has been funded under the EuropeanCommunity’sSeventhFrameworkProgramme.ThedocumentpresentsasignificantupdatetoD3.1

“Initial reportonstandardsandon the registry”.This isadeliverableofARIADNEWP3,whichwas

mainly concernedwith the creation of a registry for integration of information concerning legacy

metadata, standard schemas, services and terminological tools pertaining to the archaeological

domain.Theregistryisconceivedasanintegratedcentralrepositoryabletodescribedatasets,and

driveresourcediscoveryoperations.

Integration was realised through a preliminary analysis of legacy archives, necessary for the

identification of such formats, standards and services. Descriptions of these resources were then

collected and encoded using the ARIADNE CatalogueDataModel standard (ACDM), developed by

ARIADNE specifically to produce a detailed, formal and unambiguous representation of legacy

archaeological information,andof thevariousstandardsandservicesusedamongtheconsortium.

Integration operations took place onmultiple levels and atmultiple depths,mainly via a series of

mappingoperationsbetweenexistingandlegacydataandtheACDMmodel.

ARIADNEhas devoted part of its activities to a careful analysis of these elements preceded by an

appropriate reduction of the concepts to a common shared vocabulary, in order to identify key

features and their proper encoding, using existing and well-accepted international standards and

terminologicaltools.

This has constituted the basis for the creation of the registry, a core resource intended to store

metadata and other valuable information concerning archaeological archives, services and tools

connected to them. The registry and the detailed descriptions it contains, constitutes the “gravity

centre”ofthewholeintegrationprocess,sinceitprovidesallthesupportnecessaryfortheretrieval

andanalysisofintegratedarchaeologicalinformationandtheresourcediscoveryfacilities.

Inthisdocument,Chapter3providesanoverviewoftheARIADNECatalogueDataModel,adetailed

description of the theoretical foundations it builds upon, and theways it has been used to foster

integration among the various archaeological information contributed to the project. Chapter 4

describes the registry content,especially focusingonmetadata concerning thedatasets, standards

andservicesitholds;anoverviewofthemappingsimplementedwithintheregistryisalsoprovided,

together with statistics about the various content contained in the final release of the registry .

Chapter 5 focuses on standardisation and mapping activities carried out within the project and

describesthegenerallogicuponwhichACDM,AATandPariodOmappingshavebeenperformed,by

describingthevariousentitiesinvolved.Inthelasttwochapters,detailedinformationconcerningthe

practicalimplementationofthemappingsanddescriptionsofconversiontechniquesusedtocreate

ACDMencodeddatasets areprovided:Chapter6 containsACDMdiagramsand templatesusedby

contentprovidersforschemamatchingoperations,andprovidesexamplesofXSLTstylesheetsused

toimplementACDMtransformationsoflegacydataaccordingwiththerelatedconceptualmappings

defined; Chapter 7 reports details about the ACDMmappings performed by content providers in

ordertoprepare informationconcerningtheirarchaeologicaldatasetsandtherelatedservicesand

terminologicalresourcesforingestionwithintheregistry.

Theexhaustive listofsubjectsmappedtotheAATthesaurus,containingthecomplete listofterms

providedbypartnersandspecificationsoftherelatedAATmatchingforeachofthem,isavailablefor

consultationanddownloadthroughthiswebpage:

http://www.ariadne-infrastructure.eu/Resources/AAT.

ThecompletePeriodOlistofperiodsbuiltbycontentprovidersandmadeavailabletoARIADNEcan

befoundandbrowsedhere:


Deliverable3.4 8

http://www.ariadne-infrastructure.eu/Resources/PeriodO

CompletedescriptionsoftheservicesmadeavailablebycontentproviderstoARIADNEanddescribed

inACDMformatarealsoincludedwithintheregistry.Thespecificentitiesofthe“services”sectionof

theACDMmodelhavebeenusedtodescribeallthefunctionalitieseachspecificserviceprovidesto

theusers,includingonlinefeaturesandAPI’sforremoteinvocationandspecificfacilitiestobeused

in combination with the datasets described within the registry itself. A list of all the available

ARIADNEservicescanbebrowsedthroughtheARIANDEportalat:

http://portal.ariadne-infrastructure.eu/services


Deliverable3.4 9

3 TheARIADNECatalogueDataModel

3.1 Introduction

Tocollectinformationabouttheresourcesproposedfordiscovery,accessandpossiblyintegrationin

the ARIADNE project, the present model is defined, called the ARIADNE Catalogue Data Model

(ACDM).

ACDM is an extension of the Data Catalogue Vocabulary (DCAT), a recommendation of theW3C

Consortium (http://www.w3.org/TR/vocab-dcat/) that “is well-suited to representing governmentdatacataloguessuchasData.govanddata.gov.uk.”TheDCATVocabularywaschosenbecauseitisproposedasatoolforpublishingdatasetsasOpenData,andisthereforeoptimalfordatare-use.Its

adoptionthereforeplacesARIADNEinanidealpositionforpublishingitsresourcesasOpenDataas

well.

In addition toDCAT, the ACDM re-uses classes and properties from several other vocabularies. In

particular,ACDMmakesusageofthefollowingnamespaces:

Prefix Namespace

dcat http://www.w3.org/ns/dcat#

dct http://purl.org/dc/terms/

dctype http://purl.org/dc/dcmitype/

foaf http://xmlns.com/foaf/0.1/

rdf http://www.w3.org/1999/02/22-rdf-syntax-ns#

rdfs http://www.w3.org/2000/01/rdf-schema#

skos http://www.w3.org/2004/02/skos/core#

xsd http://www.w3.org/2001/XMLSchema#

ThepresentsectionprovidesaspecificationoftheACDM.ThespecificationconsistsofaUMLclass

diagram(Section3.3)andofatextualdescription,providingbasicinformationoneachclassandon

eachpropertyintheModel(Section3.4).Inaddition,adescriptionoftheCatalogueitselfisprovided

(Section3.2).

3.2 TheARIADNECatalogue

Forinteroperabilitypurposes,theARIADNEProjectmakestheARIADNECatalogueaninstanceofthe

dcat:Catalogclass,whichispartoftheDCATVocabulary.Thefollowingtableprovidesthemetadata

record of the ARIADNE Catalogue, expressed in RDF through the properties defined for the

dcat:CatalogclassbytheDCATspecification.

Attribute Value Note

dct:identifier http://ariadne-infrastructure/resource/Catalogue TheURIoftheCatalogueaccording

totheARIADNEnamingscheme

dct:identifier http://ariadne-infrastructure/data/Catalogue ThepresentmetadatarecordinRDF


Deliverable3.4 10

Attribute Value Note

format,accessibleasLinkedData

foaf:homepage http://ariadne-infrastructure/page/Catalogue ThewebpageoftheCatalogue

dct:title “ARIADNECatalogue”@en Wemayhaveonetitleforeach

relevantlanguage

dct:description “ACataloguedescribingtheresourcesofthe

ARIADNEInfrastructure”@en

Wemayhaveonedescriptionfor

eachrelevantlanguage

dct:issued DateofthelaunchoftheARIADNE

portal^^xsd:date

Tobedefined

dct:modified Dateoflastmodificationofthe

Catalogue^^xsd:date

Tobeupdatedafterevery

modification

dct:language http://id.loc.gov/vocabulary/iso639-2/eng Tobedefined

dct:license http://creativecommons.org/licenses/by/1.0/ Tobedefined

dct:rights Tobedefined

dct:spatial Tobedefined

dct:publisher http://ariadne-infrastructure/resource/Ariadne-

project

Tobedefined

3.3 UMLDiagramofACDM

TheUMLdiagramincludingtheclassesandthemostimportantassociationsoftheACDMisprovided

below.Forreadability,thediagramdoesnotshowallassociationsdefinedonthedcat:Datasetclass.

Every association other than sub-class has an arrow depicted next to its name, showing the

orientationofthename.


Deliverable3.4 11

Figure1:UMLDiagramoftheACDM

3.4 DescriptionoftheACDM

Thecentralnotionofthemodel is theclassArchaeologicalResourcethathasas instancesthemain

resourcesdescribedintheCatalogue.Theseresourcesarecategorizedin:

• services,representingtheservicescreatedbytheARIADNEpartnersandusedbytheprojectfordiscoveryandaccess;

• language resources, representing vocabularies, ontologies, metadata schemas, mappings

(betweenlanguageresourcesingeneral)andgazetteers.Aslanguageresourcesofnewtypes

(e.g., subject heading systems, thesauri and so on) are introduced into the Catalogue, the

modelwillbeextendedtoaccommodatethem;

• data resources, representing the various types of data containers owned by the ARIADNEpartnersandlenttotheprojectfordiscovery,accessandpossiblyintegration.Dataresources

arecategorized incollections,datasets,databasesandGIS.Asdataresourcesofnewtypes

areintroducedintotheCatalogue,themodelwillbeextendedtoaccommodatethem.

Animportantclassofthemodelisthatofformats,calledDataFormat,whoseinstancesrepresentthe

formats that realise metadata schemas, or define the structure of the records of datasets.

Analogously, the ACDM includes the class DBSchema to represent the instances of database

schemas.

Finally, there is the class MetadataRecord for representing collection or dataset-level metadata

records,whicharestoredinthecataloguefordocumentation,discoveryandassessmentofsimilarity

betweendataresources.

Adefinitionofeachclass isgiven inthefollowingsection,alongwiththeattributesthatpertainto

the class, and the associations that have the class as domain. For each attribute the obligation is

specified,throughoneofthefollowingvalues:

• Mandatory:meaningavaluemustbeprovidedfortheattribute• Recommended: meaning it is strongly recommended that a value be provided for the

attribute

• Optional:meaningavaluefortheattributemayormaynotbeprovided

Collection

DataFormat

DigitalObjectDesc

hasAttachedObject

MetadataRecord

Vocabulary

hasMetadataRecord

usesVocabulary

usesVocabulary

AttachedDocuments

hasSimpleDigitalType

Service

DataResource

ArchaeologicalResource

LanguageResource

hasRecordStructure

Database

TextualDocument

GazetteerhasItemMetadataStructure

dct:hasParts

Mapping

hasAttachedDocument

MetadataSchema

MetadataElement

hasElements

conformsTo

1..*

1..* 0..*

1..*

1..*

0..*

1

0..*

EncodingLanguage

expressedIn

hasSchema

DBSchema

isRealizedBy

1

1..*

0..1 1..*

1..*0..*

1..*

1..*

0..*

0..*

1..*

1..*0..*

1 1..*

1..*

1

1

1..*

dct:isPartOf

1..*

dcat:Catalogdct:isPartOf

foaf:Agent dct:publisher/dct:contributor/owner/ …

Distribution dcat:distribution1..*

1

GIS

from

0..*

0..*

to

Licence

hasLicence

dct:publisher0..*

1

MetadataAttribute

hasAttribute

1

0..* Version

hasVersion

hasVersion

1

1

0..*0..*

hasVersion

0..*

1

DataSet

dcat:Dataset dcat:Distribution

hasVersion 1..*1

skos:Concept

dct:isPartOf

hasMetadataRecord

0..*

0..*

1..*

0..*

AriadneConcept

1..* 0..*native-subject

dct:publisher 1* 0..*

1

0..*1

1..*

0..1

dct:hasParts

Aariadne-subject1..*

provided-subject derived-subject

B0..*

B

A1

0..1

accessibleVia


Deliverable3.4 12

For associations, cardinality constraints are given in both directions and, when applicable, it is

indicatedwhetheravalueisrecommended.

3.4.1 ArchaeologicalResource

ArchaeologicalResource is the main class of the ARIADNE catalogue, as it has as instances the

resources described in the catalogue. These resources are represented by the subclasses of

ArchaeologicalResource,whichare:• DataResource

• LanguageResource

• Service

Associations:

dct:isPartOf associates any archaeological resource in the catalogue with the catalogue. Anarchaeological resource is part of at least one catalogue. A catalogue comprises at least one

archaeologicalresource.

dct:publisher: associates any archaeological resource with an agent responsible for making the

resourcepubliclyaccessible(viadownload,orAPI,orother).Anarchaeologicalresourcehasexactly

onepublisherandanagentcanpublishzero,oneormorearchaeologicalresources.

dct:contributor: associates any archaeological resource with an agent primarily responsible for

describingtheresourceintheCatalogue.Anarchaeologicalresourcehasexactlyonecontributorand

anagentcanbethecontributorofzero,oneormorearchaeologicalresources.

dct:creator:associatesanyarchaeologicalresourcewithanagentprimarilyresponsibleforcreating

theresource.Anarchaeologicalresourcehasexactlyonecreatorandanagentcanbethecreatorof

zero,oneormorearchaeologicalresources.

owner:associatesanyarchaeologicalresourcewithanagentthatisthelegalowneroftheresource.Aresourcehasexactlyoneownerandanagentcanownzero,oneormorearchaeologicalresources.

legalResponsible: associates any archaeological resource with a person holding the legal

responsibilityof the resource.A resourcemayhave zerooronepersonwho is legally responsible,

andapersonmaybelegallyresponsibleofzero,oneormorearchaeologicalresources.

scientificResponsible: associates any archaeological resource with a person holding scientificresponsibility for the resource. It is thepersonwhoconceived the serviceor gathered thedata.A

resource may have zero or one person who is scientifically responsible, and a person may be

scientificllyresponsibleforzero,oneormorearchaeologicalresources.

technicalResponsible: associates any archaeological resource with a person holding technicalresponsibilityfortheresourceandisthecontactperson.Itisthepersonwhowrotethecodeforthe

serviceor implemented thedataset; choosing the technologyandusing it to create thedataset.A

resource has exactly one person who is technicalyl responsible, and a personmay be technically

responsibleforzero,oneormorearchaeologicalresources.

hasAttachedDocuments: associates any archaeological resource with the documents that are

attachedtotheresourceforfurtherillustration.Aresourcecanhavezero,oneormoredocuments,

andadocumentcanbeattachedtooneormorearchaeologicalresources.


Deliverable3.4 13

3.4.2 DataResource

This class specialises the class ArchaeologicalResource, and has as instances the archaeologicalresourcesthataredatacontainerssuchasdatabases,GIS,collectionsordatasets.Theclassiscreated

forthesolepurposeofdefiningthedomainandtherangeofanumberofassociations,givenbelow.

Itisthereforeanabstractclass,itdoesnothaveanyinstances,itonlyinheritsinstancesformitssub-

classes.

TheDataResourceclassdefinesthepropertiescommontoitssubclass,mostlyusingthetermsofthe

DCATvocabulary,towhichitaddspropertiesforspecifying:

• theaccesspolicyoftheresource,and;

• theoriginalidentifieroftheresource.

Thefollowingtablegivestheattributesofthisclass.

Attribute UsageNotes

ObligationM(andatory)

R(ecommended)O(ptional)

UIcontrol Example

dct:title

Minputtext

dct:description

Rtextarea

dct:issued Dateofformalissuance(e.g.,

publication)oftheresource.

M datepicker 2013-04-24

dct:modified Mostrecentdate,onwhich

theresourcewaschanged,

updatedormodified.Ifnot

providedtheissueddatewill

beused.


originalId Theoriginalidentifierofthe

resourcesuppliedbythe

contentprovider

M inputtext

dct:identifier TheARIADNEidentifierthat

willbecomputedfromthe

original.Thiscouldlooklike:

www.ariadne.eu+prefixof

theprovider+IDofthe

resource

O inputtext Automaticallycomputedbytheoriginal

dcat:keyword O inputtext

dct:language Iftheresourceismultilingual,

morethanonevaluemustbe

givenforthisproperty

M inputtext

(autocomplete)

dcat:landingPage AWebpagethatcanbe

navigatedtoinaWeb

browsertogainaccesstothe

dataset,itsdistributions

and/oradditional

O inputtext


Deliverable3.4 14


ObligationM(andatory)

R(ecommended)O(ptional)

UIcontrol Example

information.

dcat:contactPoint LinkanArchaeological

Resourcetorelevantcontact

informationwhichisprovided

usingVCard[vcard-rdf].

O dialogwindow VCard[vcard-rdf].

accessPolicy URItostatementofpolicy

(typically,onan

organization’swebsite)

O inputtext

dct:accessRights Astatementofanyaccess

restrictionsonthedata

resource

M

CreativeCommons2.0Licence

dct:rights Informationaboutrightsheld

inandoverthedataresource

R

dct:audience Theprimaryaudience(s)of

theresource

O

dct:temporal SeetemporalRegion R dialogwindow

dct:spatial SeespatialRegion M dialogwindow

dct:accrualPeriodicity O inputtext

dct:extent Thesizeofthedataresource

(i.e.,numberofitemsina

collection,numberofrecords

inadataset,etc.)

O

archaeologicalResourceType

Associatesanyarchaeological

resourcewithoneormore

categories(types),drawn

fromthefollowinglist:

• Fieldworkarchives

• Event/intervention

resources,suchasgrey

literaturereports

• Sitesandmonuments

databasesorinventories

• Scientificdatasets,suchas

databasesofradiocarbon

dates

• Artefactdatabases,or

imagecollections

• Burialdatabases

MSelectbox


Deliverable3.4 15

Associations:

dct:isPartOf a data resource canbe part of zero, oneormore collections. The inverse association

dct:hasPartsappliesforcollections(seebelow).

dcat:distribution: associates a data resource with the distributions of a resource. A resource canhaveoneormoredistributionsandadistributionisthedistributionofexactlyoneresource.

hasItemMetadataStructure: associates a data resource with the format of the metadata of the

members(oritems)ofthedataresource(e.g.metadataofeachrecordinadataset,orofeachitem

in a collection). A data resource may have zero or more metadata formats associated with its

members(items).Itemmetadataformatscanbeusedbyoneormoredataresources.

hasMetadataRecord:associatesadataresourcewiththemetadataoftheresourceascreatedbythe

organisationholdingtheresource (for instance, therecorddescribingadataset in theorganization

holdingthedataset).Adataresourcemayhavezeroormoremetadatarecords,butthespecification

isrecommended.Ametadatarecordcanbeusedbyoneormoredataresources.

ariadne-subject associates any data resource with a subject from the Getty Art and Architecture

Thesaurus(AAT).Aresourcehasatleastoneariadne-subject.Theariadne-subjectisassociatedwith

theAriadneConceptclass.Wefurtherspecializethispropertyinto:

• provided-subject associates any data resourcewith zero, one, ormoremanually specified

subjectsdrawnfromtheGettyAAT;

• derived-subjectassociatesanydataresourcewithzero,one,ormoresubjects,automatically

derivedfrommappinglocalvocabulariestotheGettyAAT.

Atleastone(orboth)oftheaboveelementsmustbeprovided.

native-subjectassociatesanydataresourcewithasubject fromavocabulary inusebytheoriginal

owneroftheresource.Thenative-subjectisassociatedwiththeskos:Conceptclass.

Collection

This class is a specialisation of the class DataResource, and has as instances collections in the

archaeologicaldomain.Inordertobeasgeneralaspossible,wedefineanarchaeologicalcollection

asanaggregationofresources,termedthe‘itemsinthecollection’.Beingaggregations,collections

are akin to datasets, butwith the following important difference: the items in a dataset are data

recordsofthesamestructure(seedefinitionofDatasetbelow).Incontrast,theitemsinacollection

areindividualobjectsdifferentfromrecords(e.g.,images,texts,videos,etc.)orarethemselvesdata

resources such as collections, datasets, databases or GIS; for instance, a collectionmay include a

textualdocument,asetofimages,oneormoredatasetsandothercollections.

For convenience, collection items that are textual documents are explicitly represented in the

Catalogueas instancesof the classTextualDocumentsandassociated to the collectionwhere they

belong.

To the best of our knowledge, no vocabulary provides a term for the class of archaeological

collection,sothishasbeenmadeaclasswithintheARIADNEvocabulary.

For interoperability, Collection is a sub-class of dcmitype:Collection. For interoperability with

Europeana,wecanbemorespecificandmakeCollectionasubclassofthecollectionclassdefinedby

Europeana.


Deliverable3.4 16

Associations:

dct:hasParts associates a collection with the data resources that are in the collection. Thisassociationcanbeusedonly for statingmembershipofdata resources inacollection.Acollection

may have one or many data resources as parts. A data resource can be in zero, one or many

collections.

Database

ThisclassisaspecialisationoftheclassDataResource,andhasasinstancesdatabases,definedasa

setofhomogeneouslystructuredrecordsmanagedthroughaDatabaseManagementSystem,such

asMySQL.


Obligation

M(andatory)R(ecommended)

O(ptional)

UIcontrol Example

dbms Thedatabasemanagement

systemused

M

MySQL

Associations:

hasSchemaassociatesadatabasewiththeschemadefiningthestructureofthedatainthedatabase.

This schema is an instance of the class DBSchema. A database has exactly one schema, and one

schemacanbetheschemaofoneormanydatabases.

Dataset

ThisclassisaspecialisationoftheclassesDataResource.Ithasarchaeologicaldatasetsasinstances.

Anarchaeologicaldatasetisdefinedasasetofhomogeneouslystructureddatarecords,consistingof

fieldscarryingdatavalues.

Associations:

hasRecordStructure: associates a datasetwith a data format defining the structure of its records.

ThisformatisaninstanceoftheclassDataFormat.Adatasethasexactlyonedataformat,andadata

formatcanbetheformatoftherecordsofoneormoredatasets.

GIS

ThisclassisaspecializationoftheclassDataResource,andhasasinstancesdatarecords,consisting

of fieldscarryingdatavalues,whicharenotmanagedthroughaGeographical InformationSystems

(GIS).

Theattributesofthisclassaregiveninthefollowingtable.


Deliverable3.4 17


Obligation


O(ptional)

UIcontrol Example

systemName NameoftheGISsystem

described.

R

inputtext(autocomplete)

3.4.3 TextualDocument

Thisclasscomprisestexts,suchasbooks,articles,reports,andthelike.Itsattributesaretakenfrom

theDataResource class, excluding those that pertain to data containers and as such do notmake

sense for textual documents, namely: accrualPeriodicity, extent, distribution and

hasItemMetadataStructure.



Obligation

M(andatory)R(ecommended)O(ptional)

UIcontrol Example

dct:title

Minputtext

dct:description

Rtextarea

dct:issued Dateofformalissuance

(e.g.,publication)ofthe

textualdocument.


dct:modified Mostrecentdateon

whichthetextual

documentwaschanged,

updatedormodified.If

notprovidedtheissued

datewillbeused.


originalId Theoriginalidentifierof

thetextualdocument

suppliedbythecontent

provider

M inputtext

dct:identifier TheARIADNEidentifier

thatwillbecomputed

fromtheoriginal.

O inputtext Automaticallycomputed bytheoriginal


dct:language Ifthetextualdocument

ismultilingual,more

thanonevaluemustbe

M inputtext(autocomplete)


Deliverable3.4 18


Obligation


UIcontrol Example



navigatedtogainaccess

tothedocument,its

distributionsand/or

additionalinformation.

O inputtext

dcat:contactPoint Linkthetextual

documenttorelevant

contactinformation

whichisprovidedusing

VCard[vcard-rdf].

O dialog

windowVCard [vcard-rdf].

accessPolicy URItostatementof

policy(typically,onan


O inputtext

dct:accessRights Astatementofany

accessrestrictionson

thetextualdocument

M

CreativeCommons 2.0Licence

dct:rights Informationabout

rightsheldinandover

thetextualdocument

R

dct:audience Theprimaryaudience(s)

ofthetextualdocument

O


Associatesthetextual

documentwithoneor

morecategories(types),

drawnfromthe

followinglist:



resources,suchas

greyliterature

reports

• Sitesand

monuments

databasesor

inventories

• Scientificdatasets,

suchasdatabasesof

radiocarbondates

• Artefactdatabases,

orimagecollections

• Burialdatabases

M Selectbox

dct:temporal Givesthetemporal R dialog


Deliverable3.4 19


Obligation


UIcontrol Example

coverageofthe

document

window

dct:spatial Givesthespatialcoverageofthedocument

M dialogwindow

Associations:

dct:isPartOfassociatesatextualdocumentwithacollectionwherethedocumentbelongs.Atextual

document can be part of zero, one ormore collections; a collection can have zero, one ormore

textualdocuments.

dct:hasParts associates a collectionwith the textual documentswithin the collection. A collection

mayhavezero,oneormoretextualdocumentasparts.Atextualdocumentcanbeinzero,oneor

manycollections.

hasMetadataRecord associates a textual document with a native metadata record. A textual

documentcanhaveatmostonemetadatarecord,andavalueisrecommended;ametadatarecord

belongstoatleastonetextualdocument.

ariadne-subject associatesanydata resourcewitha subject from theAAT.A resourcehasat least

one ariadne-subject. The ariadne-subject is associated with the AriadneConcept class.We further

specialisethispropertyinto:

• provided-subject associates any data resourcewith zero, one, ormoremanually specified

subjectsdrawnfromtheGettyAAT;

• derived-subjectassociatesanydataresourcewithzero,one,ormoresubjects,automatically

derivedfrommappinglocalvocabulariestotheGettyAAT.


native-subjectassociatesanydataresourcewithasubject fromavocabulary inusebytheoriginal

owneroftheresource.Thenative-subjectisassociatedwiththeskos:Conceptclass.

3.4.4 LanguageResource

This is theclassofall language resourcesdescribed in theCatalogue for thepurposesof re-useor

integrationwithintheARIADNEcommunity.Alanguageresourceisaresourceofalinguisticnature,

whetherinnaturallanguage(suchasagazetteer)orinaformallanguage(suchasavocabularyora

metadata schema). It also includesmappings, understood as associations between expressions of

twolanguageresourcesthatmaybeofaformal(e.g.,sub-classorsub-propertylinks)oraninformal

(e.g.,naturallanguagerules)nature.


Obligation


O(ptional)

UIcontrol Example


Deliverable3.4 20


Obligation


O(ptional)

UIcontrol Example

dct:title

Minputtext

dct:description

Rtextarea



resource.



whichtheresourcewas

changed,updatedor

modified.Ifnotprovided

theissueddatewillbe

used.


originalId Theoriginalidentifierof

theresourcesuppliedby

thecontentprovider

M inputtext


thatwillbecomputed

fromtheoriginal.

O inputtext Automaticallycompleted


dct:language Iftheresourceis

multilingual,morethan

onevaluemustbegiven

forthisproperty

M inputtext(autocomplete)


navigatedtoinaWeb

browsertogainaccessto

thedataset,its

distributionsand/or


O inputtext


Resourcetorelevant

contactinformation


VCard[vcard-rdf].

R dialogwindow VCard[vcard-

rdf].

accessPolicy URItostatementof


organisation’swebsite)

O inputtext


accessrestrictionsonthe

dataresource

M

Creative

Commons2.0

Licence


Deliverable3.4 21


Obligation


O(ptional)

UIcontrol Example

dct:rights Informationaboutrights

heldinandoverthedata

resource

R


oftheresource

O

Associations:

ariadne-subject associates any language resourcewith a subject from the AAT. A resource has at

least one ariadne-subject. The ariadne-subject is associated with the AriadneConcept class. This

propertyisspecialisedfurtherinto:

• provided-subject associates any language resource with zero, one, or more manually

specifiedsubjectsdrawnfromtheGettyAAT;

• derived-subject associates any language resource with zero, one, or more subjects,

automaticallyderivedfrommappinglocalvocabulariestotheGettyAAT.


native-subject associates any language resource with a subject from a vocabulary in use by the

originalowneroftheresource.Thenative-subjectisassociatedwiththeskos:Conceptclass.

3.4.5 MetadataSchema

This is a subclass of LanguageResource having as instances metadata schemas used in the

archaeologicaldomain.ThisisoneofthemainclassesinthemetadataregistryofARIADNE(seeUML

graphonAnnex6).



Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

standardUsed thestandarduponwhich

theschemaisbased,if

any

O

inputtext(autocomplete)

DublinCore,

MAG,ICCD,

MARC,EAD

foaf:homepage anHTTPURIpointingto

thewebpagedescribing

theschema

O inputtext dublincore.o

rg/documen

ts/dces/

proprietaryFormatDesc

iftheformatis

proprietary,thisattribute

describestheformatinan

O TextArea


Deliverable3.4 22


Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

informalway

Associations:

isRealizedBy associates a metadata schema with a data format that realises it in some specific

encodinglanguage.AMetadataSchemamayberealisedbyoneormanydataformats.Adataformat

canbetherealisationofexactlyoneMetadataSchema.

hasElements:associatesametadataschemawithitsmetadataelements.Aschemahasatleastone

metadataelement.OneelementbelongstoexactlyoneMetadataSchema.

hasVersion: associates a metadata schema with a version. A schema might have one or more

versions.Aversioncanbetheversionofexactlyonemetadataschema.

usedby:associatesametadataschemawiththeorganisationsusingit.Aschemaisusedbyatleast

oneorganization(includingtheorganisationthatsubmitsittotheregistry);anorganisationusesat

leastoneschema.

dcat:theme:AccordingtoISO11179,eachMetadataSchemashouldbeassociatedwithacategoryof

ataxonomyoranotherknowledgeorganizationschema.

Gazetteer

Thisistheclassofgazetteers,i.e.geographicalindexesordictionaries.

Mapping

Aninstanceofthisclassrepresentsamappingbetweentwolanguageresources.


Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

name Thenameofthemapping M Inputtext

foaf:homepage

TheHTTPURItotheweb

resourcegivingor

describingthemapping

O Inputtext

Associations:

from: associates a mapping to the source language resource. A mapping has exactly one source

languageresourceandalanguageresourcecanbethesourceofzero,one,ormanymappings.


Deliverable3.4 23

to:associatesamappingtothetargetlanguageresource.Amappinghasexactlyonetargetlanguage

resourceandalanguageresourcecanbethetargetofzero,one,ormanymappings.

Vocabulary

ThisisasubclassofLanguageResource.Aninstanceofthisclassrepresentsavocabularyorauthority

file, used in the associated structure. The instances of this class define the ARIADNE vocabulary

registry.Thedatamodeloftheregistryisdepictedinsection6.



Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

status Thecurrentstatusofthe

vocabulary

M draft,

reviewed,

approved

foaf:homepage Uritothevocabularyhomepage O

Associations:

hasConcept:theconceptsofavocabulary.Avocabularyhasatleastoneconcept.

hasVersion:Avocabularyhasatleastoneversion.

usedby:Avocabularyshouldbeusedbyatleastoneorganisation(includingtheorganisationwhichsubmitsittotheregistry).

3.4.6 Distribution

ThisclassrepresentsanaccessibleformofanARIADNEresource;forexample,adownloadablefile,

anRSSfeedorafileaccessibleviaawebservice.Itextendstheclassdcat:Distributionbyaddingtwo

attributes(numOfRecords,platformDescription).



Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

dct:title

M inputtext ARIADNEdatasetsinventory

dct:description

Rtextarea

dct:issued Dateofformal M datepicker 2013-04-24


Deliverable3.4 24


Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

issuance(e.g.,

publication)ofthe

distribution.

dct:modified Mostrecentdate

onwhichthe

datasetwas

changed,updated

ormodified.



rightsheldinand

overthedata

resource

R

dct:format R inputtext

(autocomplet

e)

dcat:byteSize O inputtext

numOfRecords O inputtext

platformDescription O textarea

Associations:

hasLicense:associatesadistributionwiththeclassof licenses.Adistributionmayhavezeroorone

licences, but it is recommended that the existing ones are specified, while a licence might be

associatedwithoneormoredistributions.

dct:publisher: associates any distribution with an agent responsible for making the resource

available. A distribution has exactly one publisher and an agent can make zero, one, or more

resourcesavailable.

accessibleVia:associatesanydistributiontoaservicethroughwhichthedistributionisaccessible.Adistribution is accessible through at least one service and a servicemakes accessible atmost one

distribution.

3.4.7 DataFormat

An instance of this class describes the structure of a Dataset, of a MetadataSchema, or of aMetadataRecord.



Deliverable3.4 25


Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

dct:description describestheformatin

aninformalway

R textarea

characterSet theusedcharacterset M inputtext(autocomplete)

XSD aURIgiving,ifany,the

XMLschemaofthe

recordstructure

R inputtext

Associations:

usesVocabulary:associatesadataformatwiththevocabulariesthatareusedintheinstancesofthe

data format. A data format can use zero, one, or more vocabularies, but it is recommended the

existingonesarespecified;andavocabularycanbeusedbyoneormoredataformats.

hasAttachedObject:associatesadataformatwiththetypesofdigitalobjectsthatareattachedtoits

instances. A data format can have zero, one or more digital object types attached, and a digital

objecttypecanbeattachedtooneormoreDataFormat.Thisassociationappliestodatasetswithacomplexrecordstructure.

hasSimpleDigitalType: associates a data format with the type of the objects that make up an

instanceoftheformat,incasethedataformatissimplemediaobject(text,image,video,audio,and

soon).DataFormatcanhavezero,oronedigitalobjecttypesattached,andadigitalobjecttypecanbeattachedtooneormoreDataFormat.

expressedIn:adataformatmaybeexpressedinoneormoreencodinglanguagesandonelanguage

canencodeoneormoreDataFormats.ForinstanceaDublinCoremetadataschemamaybeencoded

inXMLorinXML:RDF.

3.4.8 DBSchema

AninstanceofthisclassdescribesthestructureofaDatabase.



Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

type describesifthedatabase

issimpleorhybrid

M Hybrid/simple

description describesinainformal

waytheentities(table)

R inputtext


Deliverable3.4 26


Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

andtheassociationsof

theDatabase

RequiredDocumentation:

The logical schemaof the recordanda sampleofa recordare required.Thesecanbeprovided in

severalways,e.g.,asascreenshotofthefields,asadocumentinExcel/XMLSchema,etc.)

3.4.9 EncodingLanguage

Aninstanceofthisclassisanencodinglanguage.

3.4.10 DigitalObjectDesc

Aninstanceofthisclassrepresentsadigitalobjecttype.



Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

dct:description

Rtextarea

dct:format(MIME) M inputtext(autocomplete)

originalId theoriginalIDofthe

objectbythecontent

provider

R inputtext

dct:identifier theARIADNEidentifier

thatwillbecomputed

fromtheoriginal.This

couldlooklike:

www.ariadne.eu+prefix

oftheprovider+IDofthe

object

M(automatic) inputtext

persistentIdentifier

Booleanvalueindicating

whetherornotthe

identifierispersistent

R Boolean


Deliverable3.4 27


Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

identifierType O Inputtext NBN,DOI,PURL

3.4.11 MetadataRecord

Aninstanceofthisclassisametadatarecord,typicallyassociatedwithadataresource.



Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

XMLdoc ThemetadatarecordinXML

format

M textarea

Associations:

conformsTo: associatesaMetadataRecordwithaDataFormat.AMetadataRecordmayconform to

zero, one, or many DataFormats, but it is recommended the existing ones are specified. A

DataFormatmayhaveoneormanyrecordsthatconformtoit.

usesVocabulary:thevocabulariesthatareusedintheMetadataRecord.AMetadataRecordcanuse

zero,one,ormorevocabularies,butitisrecommendedtheexistingonesarespecified.Avocabulary

canbeusedbyoneormoreMetadataRecord.

RequiredDocumentation

Acompletesampleofametadatarecord.Whencontrolledvocabulariesareusedforcertainfields,adocumentthatpresenttheentries-ifnecessaryinhierarchicalorder-toallowapropermappingwithARIADNEdocumentationsisrequired.

3.4.12 MetadataElement

Aninstanceofthisclassdescribesthefeaturesofametadataelement,accordingtoISO11179.



Deliverable3.4 28


Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

dct:identifier aURI,ifany,givingthe

elementdescription

R Inputtext http://iflastandards.info/ns/isbd/elements/P1004

dct:title thenameofthe

element

M Inputtext Title_proper

rdf:domain Ifitisaproperty,its

domainisdenoted

O Inputtext

rdf:range Ifitisaproperty,its

rangeisdenoted

O Inputtext

dct:description R Textarea

dct:source TheXMLschemato

whichtheelement

belongs

O Inputtext

skos:scopeNote Thecontextofusing

theelement

O Textarea

published Thecurrentstatusof

theelement

M Boolean

cardinality thecardinalityofthe

element

M Inputtext

(numeric)

>=1meansthatitismandatoryanditcouldberepeated

render Thecategoryofits

representation

O Barcode,graphic

datatype Thedatatypeofthe

element

M Inputtext

(numeric)

integer

minValue Theminimumvalueof

theelement

O Inputtext

(numeric)

maxValue Themaximumvalueof

theelement

O Inputtext

(numeric)

allowValues Thevaluesallowedfor

thiselement

O Selectbox Red,Blue,Green

proprietaryFormatDesc

iftheformatis

proprietary,this

attributedescribesthe

formatinaninformal

way

O Textarea

characterSet thecharactersetused M Inputtext


Deliverable3.4 29


Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

Associations:

hasSubelement:Anelementmightbeofsimpleorcomplextype. If it isofcomplextype, it should

haveatleastasub-element.Alsoanelementmightbesub-elementofdifferentelements.

hasAttribute:AnelementmighthavezeroormoreXMLAttributes.

dcat:theme:According to ISO11179,eachdataelementshouldbeassociatedwithacategoryofa

taxonomyoranotherknowledgeorganisationschema.

hasRelation:Anelementmightberelatedtozeroormoreotherelements.AccordingtoISO11179

therelationshiptypescanbedescribedbythefollowingvocabulary:qualifierof,qualifiedby,subject

of,physicalcondition,partof,externalreference,etc.

hasVersion:A structuredefinedbyanelement, its sub-elementsandXMLattributesmighthavea

version.

usedby: Anelementshouldbeusedbyat leastoneorganisation(includingtheorganisationwhich

submitsittotheregistry).

dct:creator:An agentprimarily responsible for the creationof themetadataelement.Ametadata

elementhasexactlyonecreatorandanagentcanbethecreatorofoneormoreschemas.

dct:publisher:Anagentresponsibleformakingthemetadataelementavailable.Ametadataelement

hasexactlyonepublisherandapublishercanpublishoneormoreelements

3.4.13 TemporalRegion

Aninstanceofthisclassisatemporalregionofoneoftwoforms:

1. atemporalinterval(e.g.,from155B.C.to243A.C.)

2. anamedperiod(e.g.,Neolithic)

Intheformercase,theextremesoftheintervalaregivenasvaluesofthefromandtoattributes.

Inthelattercase,thenamedperiodisgivenasvalueoftheperiodNameattribute.- InthecasewhereBCdateshavetobesupplied,aminus(-)signcouldbeusedasindicatedin

theexpandedYearrepresentationofISO8601

(http://www.iso.org/iso/catalogue_detail?csnumber=40874).

- Inthecasewherereducedprecisionmustbeapplied(e.g.wherenodayinformationis

available)therespectivepartcouldbeomitted(accordingtoISO8601reducedprecision

guidelines).



Deliverable3.4 30

Attribute

UsageNotes

Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol

Example

periodName nameforthisperiod MSelectbox

from adate(indicatingstartdate

forthistemporalregion)

RDatepicker 1800-?-?

until adate(indicatingenddate

forthisregion)

RDatepicker

Attribute

UsageNotes

Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol

Example

placeName anamedescribingthe

place

MInputtext

coordinateSystem thecoordinatesystem

usedtoencode

coordinates(e.g.EPSG

2763).Ifnotspecified,

EPSG4326willbe

implied

OInputtext

lat thelatitude RInputtext

(numeric)

lon thelongitude RInputtext

(numeric)

boundingBoxMinLat theminimumlatitude

oftheboundingbox

area

OInputtext

(numeric)

boundingBoxMinLon theminimum

longitudeofthe

boundingboxarea

OInputtext

(numeric)

boundingBoxMaxLat themaximumlatitude

oftheboundingbox

area

OInputtext

(numeric)

boundingBoxMaxLon themaximum

longitudeofthe

boundingboxarea

OInputtext

(numeric)

address theaddressname OInputtext


Deliverable3.4 31

3.4.14 SpatialRegion

Aninstanceofthisclassisaspatialregion,whichcantakeoneoffourforms:

1. a region identified by latitude and longitude expressed via the lat and lon attributes,

respectively;

2. a bounding box identified by four vertices (expressed via the boundingBoxMinLat,

boundingBoxMinLon,boundingBoxMaxLatandboundingBoxMaxLonattributes);

3. a postal address (expressed via the address, numberInRoad, postcode and country

attributes);

4. anamedplace(expressedviatheplaceLabelattribute).

3.4.15 MetadataAttribute

AninstanceofthisclassdescribesanXMLattributeametadataelement.



Obligation

M(andatory)

O(ptional)

UIcontrol Example

dct:identifier aURIgiving,ifany,theattribute

description

O Inputtext

dct:title thenameoftheattribute M Inputtext type

dct:description M Textarea

dct:source thenamespacetowhichtheattribute

belongs

O Inputtext

contextInfo thecontextofusingtheattribute O Textarea

published thecurrentstatusoftheattribute M Boolean

cardinality thecardinalityoftheattribute M Inputtext

(numeric)

>=1means

thatitis

mandatory

andit

couldbe

repeated

minValue theminimumvalueoftheattribute O Inputtext

(numeric)

maxValue themaximumvalueoftheattribute O Inputtext

(numeric)

numberInRoad thenumberinroad OInputtext

postcode postcode OInputtext

country thecountryofthe

place

MInputtext

(autocomplete)


Deliverable3.4 32


Obligation

M(andatory)

O(ptional)

UIcontrol Example

allowValues thevaluesallowedforthisattribute O Selectbox Red,Blue,

Green

characterSet thecharactersetused M Inputtext

3.4.16 Version

An instanceof this class provides information about a versionof a vocabulary, concept,metadata

schemaormetadataelement.



Obligation

M(andatory)

O(ptional)

UI

controlExample

dct:title thenameoftheversion M Input

text

dct:modified theDateofmodificationofa

metadataschema,metadata

element,vocabularyorconcept

M(automatic) Date

picker

skos:changeNote anoteonthemade

modifications

O Textarea

Associations:

dct:publisher: An agent responsible for making the version available. A version has exactly one

publisherandapublishercanpublishoneormoreversions.

3.4.17 AriadneConcept

Aninstanceofthisclassrepresentsaterm(concept)usedinavocabularyorauthorityfile.



Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

dct:identifier AURIthatidentifiestheconcept R Inputtext


Deliverable3.4 33


Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

skos:prefLabel Thedescriptoroftheconcept

(preferedterm)

M Inputtext

skos:scopeNote R Texarea

skos:definition R Textarea

dct:source Thevocabularywithinwhichthe

conceptexists

M Inputtext

skos:collection Thefacettowhichtheconcept

belongs

R Inputtext

published Thecurrentstatusofthe

vocabulary

M Boolean

dct:language Thelanguageofthedescriptor M Selectbox

provided Iftheconceptisprovided(true)or

derived(false)

M Boolean

Associations:

hasRelation: A conceptmight be related to zero ormore other concepts. The SKOS vocabulary is

used for the definition of the relationships between concepts: skos:narrower, skos:broader,

skos:related,skos:member,skos:inScheme.

hasVersion:Aconceptmighthavezeroormoreversions.

3.4.18 Licence

AninstanceofthisclassrepresentsaLicence.



Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

name Thenameofthemapping M Inputtext

dct:description

R selectbox

URI

TheURIofthelicense

website

R selectbox


Deliverable3.4 34

3.4.19 Service

While for thedescriptionof theARIADNEdatasets itwaspossible to adopt a standard vocabulary

(DCAT), regarding the description of the services to be surveyed for ARIADNE, the situation was

somewhatmore complicated, as several vocabularies exist, noneofwhich standout as ade factostandards.

Deliverable D13.2 provides an exhaustive list of services that will be made available through the

ARIADNE infrastructure. Basedon the evidence collected in this deliverable, services are classified

intothefollowingcategories,reflectingthewayaserviceisaccessed:

• toolstobedownloadedandinstalledonone’smachine;thesewillbetermedstand-aloneservices;

• webaccessibleserviceswithanAPI:thesearecalledwebservices,andtheservicesdevelopedbytheARIADNEprojectfallinthiscategory;

• webaccessibleserviceswithaGUIonly:thesearecalledservicesforhumans;• servicesofferedbyaninstitution,negotiatedviaapersonalinteractionwithrepresentatives

ofthatinstitutioninordertobeaccessed;thesearecalledinstitutionalservices.

Correspondingly,weintroduceinthemodelagenericServiceclass,whichisabstractandgathersthe

propertiesincommontoallservices,andfoursub-classes,whichhaveone-to-onerelationshipswith

theabovefourcategories.TheseclassesaredescribedintherestofthisSection.

Furthermore, Section 7.1 in D13.2 points out some inadequacies exhibited by the applyToassociations and calls for a representation of item-level information in relation to Services. In

response to theseobservations, theapplyTo associationhasbeendroppedand fourattributesareintroduced to represent the media type and format of the items consumed and produced by a

service.

TheclassService is introduced in theARIADNECatalogue inorder to representservicesofferedby

ARIADNEpartnersforusewithintheARIADNEinfrastructure.Thisclassisabstractinthesensethat

allitsinstancesareinstancesofsomeofitssubclasses.

Service isasub-classofArchaeologicalResourceandinheritstheassociationsdefinedforthe latter,

namely:

• dct:isPartOf:thecataloguetheserviceisdescribedin(includedtheARIADNECatalogue)

• dct:publisher:theagentmakingtheserviceaccessible

• dct:contributor:theagentresponsiblefordescribingtheserviceintheARIADNECatalogue

• dct:creator:theagentthatcreatedtheservice

• owner:theagentthatisthelegalowneroftheservice

• legalResponsible:theagentthatislegallyresponsiblefortheservice

• scientificResponsible:theagentthatisscientificallyresponsiblefortheservice

• technicalResponsible:theagentthatisthetechnicalylresponsiblefortheservice

• native-subject:asubjectfromavocabularyinusebytheoriginalowneroftheservice

• hasAttachedDocuments:thedocumentsattachedtotheserviceforillustrationpurposes

(includingvideos).



Deliverable3.4 35


Obligation

M(andatory)

R(ecommended)

O(ptional)

UI

controlExample

dct:title Thisisthenameoftheservice M

dct:description Containsadescriptionofthe

service

M

rdfs:comment Notesandcomments O

foaf:homepage URLtotheservicehomepage R

dct:issued Dateofformalissuance(e.g.,

publication)oftheservice.

M 2013-04-24

dct:modified Mostrecentdateonwhichthe

servicewaschanged,updated

ormodified.Ifnotspecified,the

issueddatewillbeused

automatically.

M 2013-04-24

functionality Amultivaluedpropertyto

classifytheservice

O 3D

visualization,

preservation

exportFacility Iftheserviceprovidesexport

functionalityforthedatasetson

whichitoperates,supplyalist

offormat.

O csv

consumedMedia Themediatypeoftheobjects

handledbytheservice.Thelist

ofpossiblemediaTypeisopen

M “image”,“audio”,“video”,“text”,“3Dmodel”,“2Dmodel”,etc.

producedMedia Themediatypeoftheobjects

createdbytheservice.Same

valuesasconsumedMedia

M

consumedFormat TheMIMEtypeoftheobjects

handledbytheservice

M

producedFormat TheMIMEtypeoftheobjects

createdbytheservice

M

supportedLanguage Thelanguagessupportedbythe

service

O

accessURL URLtotheserviceaccesspage.

Thismaybethesameasthe

M


Deliverable3.4 36


Obligation

M(andatory)

R(ecommended)

O(ptional)

UI

controlExample

foaf:homepage

Associations:

hasTechnicalSupport:Theagentofferingtechnicalsupportontheservice,ifany

developer:Theagentwhodevelopedtheservice

StandAloneService

TheclassStandAloneService is introduced in theARIADNECatalogue inorder to representservices

thatmustbedownloadedandinstalledonone’smachineinordertobeused.

As already mentioned, this is a sub-class of Service, therefore it inherits all attributes and

associationsdefinedforthelatter.

The following table gives the specific attributes of this class, mostly drawn from the DBPedia

softwareontology(http://dbpedia.org/ontology/Software).

Anexemplificationoftheuseofthisontologycanbefoundathttp://dbpedia.org/page/Lucene.


Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

dbpedia-owl:operatingSystem

TheOSplatform

requiredbytheservice

M dbpedia:Cross-

platform

dbpedia-owl:programmingLanguage

Mifsourcecode

isavailable

dbpedia:Java_(

programming_l

anguage)

dbpedia-owl:status M InProgress,

available,

dbpedia-owl:latestReleaseVersion

R

dbpedia-owl:license M

dcat:downloadURL R

dcat:byteSize O

installationRequirements

O


Deliverable3.4 37

Associations:

isInRepository: indicates whether the source code is available in a repository URI and otherinformationlikecredentialtoaccesstherepositoryaresupplied.

hasAPI:indicateswhethertheserviceprovidesanAPI,atextualdescriptionmustbesupplied.

hasComponents:thecomponentsrequiredfortheServicetobeinstalledandused.

WebService

TheclassWebServiceisintroducedintheARIADNECatalogueinordertorepresentservicesthatare

webaccessibleandhaveanAPI.TheymayormaynothavealsoaGUI.



Associations:

hasAPI:atextualdescriptionoftheserviceAPI.

ServiceForHumans

TheclassServiceForHumans is introduced in theARIADNECatalogue inorder to representservices

thatarewebaccessibleonlyviaaGUI.



Associations:

Nootherassociationdefined.

InstitutionalService

TheclassInstitutionalServiceis introducedintheARIADNECatalogueinordertorepresentservices

that are offered by some institution and thatmust be negotiated via a personal interaction with

representativesofthatinstitutioninordertobeaccessed.

Thisisalsoasub-classofService,thereforeitinheritsallattributesandassociationsdefinedforthe

latter.

Associations:

contactPerson:theAgenttobecontactedinordertoaccesstheservice.

3.4.20 foaf:Agent

Thisclassisusedinthisschematomodeltheinstitutionsthatmakearesourceavailable.



Deliverable3.4 38


Obligation

M(andatory)

R(ecommended)

O(ptional)

UIcontrol Example

foaf:name nameofthe

organisation

Minputtext

foaf:phone O inputtext

foaf:mbox M inputtext

foaf:skypeID O inputtext

Associations:

dct:isPartOf: associates any foaf:Agentwith another foaf:Agentwhere the former belongs (e.g., apersonwiththeorganisationtheyworkfor).


Deliverable3.4 39

4 TheARIADNERegistry

4.1 ARIADNERegistryContent

Thenumberof recordsprovidedby theARIADNEpartners ispresented in the following table.The

numberof records listed foreachpartner corresponds to thenumberof collection-level resources

provided, not the extent of the resource. For example a partner with many records may have

hundredsofreportsthateachhavecollection-levelmetadataandthereforehavetheirownrecord,

oronlyasingledatabasethatisarichandcomplexresource,butmighthaveonlyonecollection-level

record. Hence the differences in the number of records provided do not indicate some partners

providedresourcesoflesservaluethanothers.

Providername RecordsADS 1550082

SND 450

KNAW-DANS 30480

FastiOnline/AIAC 6310

MNMNOK 1884

MiBACT-CulturaItalia 40472

ZRCSAZU 10638

CyI-STARC 17

INRAP 20681

IncipitCSIC 1

OEAW inprogress

ARUP-CAS 1

NIAM-BAS 1

DISCOVERY 140864

DAI 39857

ARHEO 106

SUM 1841844

In total, 1,841,844 records have been ingested in the registry. The majority of them have been

providedbyADS.Regardingthetypeofmaterialprovided,mostrecordscorrespondtodatasetsand

textualdocuments,butthisdisguisesthefactthattheregistryholdsmanythousandsofbibliographic

records(seethetableinSection4.3),andasignificantsetofcollectiondescriptions.

A few records concern services. After publishing the last version of the ACDM schema, which

updated the services description, many records have been registered and their specifications are

nowavailable.Thereexistaround25descriptionsofservices,whichhavebeeninsertedmanuallyin

theRegistry(seehttp://portal.ariadne-infrastructure.eu/services).

4.2 ARIADNERegistryMappings

The content-providing ARIADNE partnersmapped descriptions of their content to the ACDM. The

mappingprocesswascompletedinanumberofways:

(i) The providers mapped their metadata locally (descriptions of their resources (databases,

collections, bibliographies, datasets, etc.) to the ACDM and sent their data to the ARIADNE


Deliverable3.4 40

technicalpartners inMSExcelformat.TheMSExcelfilesweretransformedtoXMLformatand

ingested into theARIADNE registry. Theywere then harvested by theMORe aggregator to be

enrichedandpublishedtotheARIADNEportal.

(ii) The providers locally mapped the descriptions of their resources (databases, collections,

bibliographies,datasets,etc.)totheACDMandsenttheirdata inXMLformat,validatedbythe

ACDMschema.TheXMLdocumentswereeitherdownloadedas.zipfilesorharvestedusingthe

OAI-PMHprotocolbytheMOReaggregator.ThedataintheMOReaggregatorwasthenenriched

andpublishedtotheARIADNEportal.

(iii) Theprovidersprovided large volumesof nativedata inXML format thatwerenot valid in the

ACDM schema. In such cases a stylesheet in XSLT formatwas created by theDigital Curation

Unit, ATHENA RC (DCU) for the automated transformation of the native metadata into XML

documentscompatiblewiththeACDMschema.Whenthenativemetadataweredownloadedas

.zipfilesorharvestedbytheMOReaggregator,theappropriateXSLTstylesheettransformedthe

nativeXMLrecordstoACDMrecords.FinallythedataintheMOReaggregatorwereenrichedand

publishedtotheARIADNEportal.AllthemappingsinXSLTstylesheetsarestoredintheregistry

andcanbere-usedbyusersofthetheARIADNEinfrastructure.

4.3 ContentandMappingStatistics

ThecontentoftheARIADNEregistryperpartnerandtypeispresentedinthefollowingtable.

Providername Datasets Databases TextualDocuments Collections Records

ADS 1519246 0 30127 709 1550082

SND 0 0 0 450 450

KNAW-DANS 0 0 0 30480 30480

FastiOnline/AIAC 0 0 0 6310 6310

MNMNOK 0 0 0 1884 1884

MiBACT-CulturaItalia 40470 0 0 2 40472

ZRCSAZU 10635 2 0 1 10638

CyI-STARC 16 0 0 1 17

INRAP 0 0 20680 1 20681

IncipitCSIC 1 0 0 0 1

OEAW inprogress

ARUP-CAS 1 0 0 0 1

NIAM-BAS 0 1 0 0 1

DISCOVERY 140860 0 0 4 140864

DAI 0 26192 13663 2 39857

ARHEO 104 0 0 2 106

TOTAL 1711333 26195 64470 39846 1841844

Five(5)mappingsinXSLTstylesheetsweredevelopedbyDCUforADS,FastiOnline/AIACandMiBACT

– CulturaItalia,which chose the alternative (iii) to ingest data in ARIADNE registry. The remaining

partnersprovidedACDMrecordsdirectlyinXMLorMSExcelformat.Itshouldbenotedthatmostof

the records (1,596,864) were ingested by utilising the XSLT-based mappings, while only 244,653

recordswereingesteddirectlyasACDMrecords.


Deliverable3.4 41

5 StandardisationandMappinginARIADNE

5.1 ACDMMappings

Asmentioned in sections 4.2 and 4.3, XSLT stylesheetswere created in order to ingest 1,596,864

recordsinARIADNEregistry.Moreover,samplesofindicativenativeandACDMrecordscanbefound

atthefollowingaddresses.

A.ArchaeologyDataService(ADS)

1. Collection

Native:http://more.locloud.eu:8080/objects/4467/19138216/ADS_ARCHIVE/content

ACDM:http://more.locloud.eu:8080/objects/4467/19138216/eACDM/content

2. TextualDocument

Native:http://more.locloud.eu:8080/objects/2864/10398981/GLL/content


3. Dataset

Native:http://more.locloud.eu:8080/objects/3025/11426361/Archsearch/content


B.MiBACT-CulturaItalia

4. Dataset(namedPICO)

Native:http://more.locloud.eu:8080/objects/4108/18364935/PICO/content

ACDM:http://more.locloud.eu:8080/objects/4108/18364935/ACDM/content

C.AIACFastiOnline

5. Collection

Native:http://more.locloud.eu:8080/objects/4703/23554802/OAI_DC/content


InthecaseswheredatawereprovidedinMSExcelformat,anMSExceltemplatewascreatedbythe

DCUanddistributedtothepartners.Partnerspreparedtheirdataaccordingtothetemplateandsent

theMSExcelfile(s)toDCU.DCUdevelopedaJava-basedapplication,customizedforthenativeMS

Excel file(s). The Java-based application processed the MS Excel files, transformed them to XML

format and ingested them into theARIADNE registry. Asmentioned in section 4.2 thedata in the

ARIADNEregistrywereharvestedbytheMOReaggregatorinordertobeenrichedandpublishedto

theARIADNEportal.


Deliverable3.4 42

5.2 AATMappings

The subjects to which the various datasets relate (e.g. excavations and archaeological surveys,

monuments,burials,pottery,etc.),aredescribedusingtermsdrawnfromtheArtandArchitecture

Thesaurus(AAT)oftheGettyResearchInstitute.TheAATformedthespineforthewholeframework

of terms in ARIADNE, not only with regard to the general subjects, but also for every other

typological, morphological and functional description of archaeological objects and activities

connectedtothem.

Theuseofasharedthesaurusrequiredamappingofeachterminologicalresourcealreadyinuseby

contentproviders,totheAATconcepts;afundamentalactivitythroughwhichitwasalsopossibleto

demonstrate the semantic and conceptual similarity between the different archives. Themapping

activities were undertaken by domain experts assisted by various mapping tools developed

specificallytoestablishcorrespondencesbetweenconceptscomingfromdifferentvocabularies.

Two different tools were developed to support the domain experts doing the mapping between

vocabularyconcepts,orientedtodifferentcontextsforthevocabularies.Aninteractivemappingtool

was developed for ARIADNE, oriented tomajor vocabularies already expressed as LinkedData via

local or national initiatives. Themapping tool generates SKOSmapping relationships in JSON and

other formats between the source vocabulary concepts and the corresponding AAT concepts. To

assist the production of qualitymappings, themapping tool displays the source concepts and the

AAT concepts side by side, together with contextual evidence and allows the person making the

mappings tobrowse relatedconcepts ineither vocabulary to fine tune themapping.Themapping

tool is a browser-based application working directly with Linked Data, querying external SPARQL

endpointsdirectly[BindingandTudhope2016].Themappingtool isopensourceandwillbemade

availableviatheARIADNEPortal.ApilotmappingexercisewasperformedbytheADSonUKHeritage

Data vocabularies. Analysis of results informed an iteration of the mapping guidelines and the

mapping tool user interface. The mapping guideline revisions included recommendations on the

appropriate SKOS mapping relationship to employ in different contexts and when appropriate to

specifymorethanonemappingforagivenconcept.

Thesecondmappingtoolwasorientedtocaseswherethesourcevocabularieswerenotexpressed

as LinkedDataand includedsimpler ’flat list’ vocabularies. Sincemanyof the simplervocabularies

werealreadyavailableoreasilyexpressed inspreadsheetformat, themost flexiblesolutionwasto

designastandardspreadsheetwithexamplemappingsthatdomainexpertscouldusetospecifythe

mappings. A CSV transformation produced the RDF/JSON format required by the Catalogue. The

spreadsheet was accompanied by a set of guidelines informed by the pilot mapping exercise

(togetherwithsupportfromthevocabularyteamonproblematicmappingsorprecedentsfromother

partnermappings). In somecases,data cleansingwas requiredbefore themappingexercise could

proceed.Themappingtemplatecontainedatabtorecordmetadataforthemapping.Infuturework,

making themappingsavailable asoutcomes in theirown right,withappropriatemetadata for the

mappingswouldbedesirable,asmorethanonemappingmaybeproducedforlargevocabularies.


Deliverable3.4 43

Figure2:MappingworkflowforuseoftheAATwithinARIADNE.

TheinformationfromthemappingtoolispassedtoMORe,whichassociatesitwiththeproviderof

the vocabulary. It updates the property derived-subject and enriches an ACDM record, adding a

broader term, or a skos:altLabel to correlate a term using the ‘use for’ relationship, or adds

multilinguallabels(skos:prefLabelandskos:altLabel)inordertofacilitatemultilingualsearch.

PrototypeexperimentshaveshownthepotentialofworkingwiththeURIidentifiersofAATconcepts

rather than ambiguous strings of term labels. Using the URI identifier for the concept avoids the

problem(discussedabove)commonwithmultilingualdataoftermsthatarehomographsindifferent

languages.Workingattheconceptlevelalsomakespossiblehierarchicalsemanticexpansion,making

use of the broader generic (“IS-A”) relationships between concepts in a hierarchically structured

knowledgeorganizationsystem,suchastheAAT.Thusasearchexpressedatageneral levelcan(if

desired) returnresults indexedatamorespecific level, forexampleasearchonsettlementsmight

alsoreturnmonasticcentres.

Insomecases,ARIADNEhascontributedtoupdatedorevennewsubjectvocabularies.Oneexample

istheongoinginitiativetodevelopamultilingualSKOSvocabularytobeusedfordocumentingdata

resultingfromdendrochronologicalanalysis. Inothercollaborations,ARIADNEhasassistedwiththe

generation of SKOS representations for national vocabularies. Detailed descriptions of the various

AAT mappings performed within ARIADNE are provided on the official AAT ARIADNE webpage

http://www.ariadne-infrastructure.eu/Resources/AAT.

TheTablebelowprovidesoverallstatisticsontheAATmappings.


Deliverable3.4 44

Partner VocabulariesmappedtoAAT

Nomatch

skos:exactMatch

skos:closeMatch

skos:broad

Match

skos:narrowMatch

skos:related

Match

Totals

ADS ArchaeologicalObjects(subset) 0 197 96 118 0 0 411

ADS BuildingMaterials(subset) 0 8 4 0 0 0 12

ADS MonumentTypes(subset) 0 141 107 141 0 1 390

ADS ComponentsThesaurus(subset) 0 7 1 1 0 0 9

ADS MaritimeCraft(subset) 0 13 8 3 0 0 24

DAI ARACHNE-books 0 13 4 0 0 0 17

DAI ARACHNE-collections 0 8 2 1 0 0 11

DAI ARACHNE-inscriptions 0 18 1 0 0 0 19

DAI ARACHNE-buildingsandstructures 0 81 37 44 14 0 176

DAI ARACHNE-multi-partmonument 0 51 35 22 0 0 108

DAI ARACHNE-topographicobjects 0 46 7 2 0 0 55

DANS DCCDvocabulary 0 245 9 82 0 0 336

DANS EASY-Complextypen 3 3 59 34 0 15 114

Discovery IrishMonumentTypes 0 168 69 249 0 0 486

IACA FASTIMonumentTypes 2 23 80 24 0 0 129

ICCU ICCDRAandPICOthesauri(subset) 0 642 94 310 258 0 1304

INRAP PACTOLSthesaurus(subset) 0 1161 121 346 6 0 1634

MNM-NOK SiteTypes 0 0 34 7 0 0 41

OEAW DFMROEDB 0 4 0 0 3 0 7

OEAW FranzhausenKokoernDB 0 5 2 2 1 0 10

OEAW UKMaterialPoolDB 0 7 0 4 5 0 16

OEAW UKThunauDB 0 3 1 0 0 0 4

SND Combinedtermslist 5 71 156 144 11 0 387

ZRC-SAZU ZBIVAvocabulary 0 0 25 5 0 0 30

ZRC-SAZU ARKASvocabulary 0 0 76 17 0 0 93

PartnerTotals

ADS 5 0 366 216 263 0 1 846

DAI 6 0 217 86 69 14 0 386

DANS 2 3 248 68 116 0 15 450

Discovery 1 0 168 69 249 0 0 486


Deliverable3.4 45

Partner VocabulariesmappedtoAAT

Nomatch

skos:exactMatch

skos:closeMatch

skos:broad

Match

skos:narrowMatch

skos:related

Match

Totals

IACA 1 2 23 80 24 0 0 129

ICCU 1 0 642 94 310 258 0 1304

INRAP 1 0 1161 121 346 6 0 1634

MNM-NOK 1 0 0 34 7 0 0 41

OEAW 4 0 19 3 6 9 0 37

SND 1 5 71 156 144 11 0 387

ZRC-SAZU 2 0 0 101 22 0 0 123

Totals: 25 10 2915 1028 1556 298 16 5823

Proportionin%: 0.17 50.06 17.65 26.72 5.12 0.27 100

5.3 PeriodOMappings

TheuserrequirementsfortheARIADNEportalspecifiedthatchronologicalsearchingoftheARIADNE

catalogueby archaeological period shouldbe regarded as essential.However, this introduced two

problems,whichtheprojectneededtoovercome.Firstly,eachdataproviderpartnerusedhisown

listofperiods,manyofwhichwerenon-standardised.Secondly,evenwhenthesameperiodterms

are used they are not independent variables, but are specific to country and region and specific

spatialpolygons.Forexample,thoughitisaubiquitousarchaeologicalperiodthroughoutEuropeand

muchofAfrica, the IronAgehasverydifferentstartandenddatesaccordingtoregion.Therefore,

the approach adoptedneeded to support two typesof period searching: by start andenddate in

absolutecalendaryears(e.g.2500-1800BC),andbyculturalperiod(e.g.EarlyBronzeAge).

In order to resolve these problems, it was agreed to collaborate with the North American-based

PeriodO project (http://perio.do). PeriodO is a gazetteer of scholarly definitions of historical, art-

historical,andarchaeologicalperiods.Iteasesthetaskoflinkingamongdatasetsthatdefineperiods

differently.Italsohelpsscholarsandstudentsseewhereperioddefinitionsoverlapordiverge.

5.3.1 Definitions

The PeriodOperiod gazetteer documents definitions of historical period names. Each entry of the

gazetteer identifies the definition of a single period. To be included in the gazetteer, a definition

must

• givetheperiodaname;

• imposesometemporalboundsontheperiod;

• havesomeimplicitorexplicitassociationwithageographicalregion,and;

• havebeenformallyorinformallypublishedinsomecitablesource.

MuchcarehasbeenputintogivingperioddefinitionsstableidentifiersthatcanberesolvedtoRDF

representationsofperioddefinitions.PeriodOmodelsperioddefinitionsasSKOSconcepts.Theseare


Deliverable3.4 46

groupedintoconceptschemessharingthesamebibliographicsource.Temporalextentisexpressed

via a direct textual quotation from the source, as well as via a structured approximation of this

expressionmodelledusingtheOWL-Timeontology.Similarly,spatialextentisrepresentedbothbya

textualquote(whereonewasgiven)andasetof identifiersreferringtospatialentities inexternal

resourcessuchasDBpedia.

Examples:

• http://n2t.net/ark:/99152/p05krdxmkzt identifies the “Dark Age” as defined by Davis and

Alcockonpage97ofSandyPylos:anarchaeologicalhistoryfromNestortoNavarino(seethe

JSONrepresentation).

• http://n2t.net/ark:/99152/p06v8w4identifiesalltheperioddefinitionsfromtheFastiOnline

databaseofarchaeologicalexcavations(seetheJSONrepresentation).

5.3.2 Identifiers

Eachperioddefinition is given its ownWeb-based, resolvableUniformResource Identifier (URI) in

theformofanArchivalResourceKey(ARK),mintedthroughtheEZIDsystemoftheCaliforniaDigital

Library. These ARKs are resolvable to structured, machine-readable representations of individual

perioddefinitions.

Wherever possible bibliographic sources are identified withWorldCat URIs or CrossRef DOIs, and

creatorsareidentifiedwithVirtualInternationalAuthorityFileURIs.

5.3.3 DataSerialization

Period definitions in the PeriodO gazetteer are published as JSON-LD, a serialised form of the

ResourceDescriptionFormat(RDF)usedtodescribeLinkedData.Theentiredataset isavailablefor

downloadasasingleJSONfile,sothatitcanbemoreeasilyreusedbyotherprojects.

5.3.4 UserInterface

A browser-based client provides search, visualisation, and data entry tools. It also provides an

interfaceformanagingdistributedversioningandcollaborativedevelopmentofthePeriodOdataset.

The entire editorial history of the PeriodO gazetteer is published as a separate dataset using the

PROVontology.

5.3.5 ImplementationbyARIADNE

AllARIADNEdataproviderpartnerscompletedaspreadsheetdefiningthenativeperiodtermsused

indescribingtheirresourcesintheARIADNEregistry.Foreachrecordtheyrecorded:

• Source

• Language

• Script

• SourceZoteroid(whereavailable)

• SourceLinkedDdataURI(whereavailable)

• Sourcelocator(URL)

• Label(original)

• Label(English)

• Label(alternative)whereapplicable


Deliverable3.4 47

• Startdate

• Enddate

• Datatype(e.g.BP)

• Spatialcoverage(countryorregionname)

ThisdatacouldthenbeusedwithintheRegistrytoprovideastartandenddate inabsoluteyears,

facilitatingtimelinesearching,aswellassearchbynativeperiodlabel.Alltheperioddefinitionswere

published as the ARIADNE collection on the PeriodO website: http://n2t.net/ark:/99152/p0qhb66

EachARIADNEperiodtermthereforehasapermanentURIwhichcouldbecitedwithinthecatalogue

aswellaswithinlinkeddataimplementations.

Additionalprojectdocumentationisavailableat:

http://www.ariadne-infrastructure.eu/Resources/PeriodO/documentation


Deliverable3.4 48

6 ACDMEncoding:DiagramsandSchemas

Inthissection,someofthemostrelevantACDMclassaredescribedusingUML-graph,alongwiththe

mappingtemplatesusedbypartners,andexamplemappingsusingtheXSLTtemplate.Thissetsout

the basic structure followed by all partners, in combinationwith the AAT and PeriodO, set out in

Section5.HowthesewereimplementedbyeachpartnerissetoutinSection7.

6.1 Diagrams

6.1.1 Service

6.1.2 Vocabulary

dct:identifierskos:prefLabelskos:altLabelskos:scopeNoteskos:definitionskos:Collectiondct:sourceact:language:statusfoaf:homepage

skos:Concept

foaf:homepage:status

Vocabolary

dct:titledct:modifiedskos:changeNote

Version

:hasConcept 1

:hasVersion

1

foaf:agent

:usedby

0..*

1..*0..*1..*


Deliverable3.4 49

6.1.3 MetadataSchema

6.1.4 AriadneConcept

dct:identifierdct:titlerdf:domainrdf:rangedct:descriptiondct:sourcefoaf:namedvt:publisherskos:scopeNote:status:obligation:cardinality:render:datatype:minValue:maxValue:allowValues:proprietaryFormatDescription:characterSet

MetadataElement

:standardUsed::proprietaryFormatDesc:foaf:homepage

MetadataSchema

dct:titledct:modifiedskos:changeNote

Version

dct:identifierdct:titledct:descriptiondct:source:context_info:status:obligation:datatype:minValue:maxValue:allowValues:characterSet

MetadataAttribute

skos:Concept

:hasAttribute

:hasElement1

:hasVersion

1

:hasVersion1

foaf:agent

1 dct:publisher

:usedby

:mappingTo

1

dcat:theme

1

:hasrelation

:hasSubelement

1..*

1

dcat:theme

1

0..*

1

1..*

1..*

0..*

0..*

1..*

0..*

0..*

1..*

1..*

1..*

1..*

foaf:agent

dct:publisher

:usedby

dct:creator

11..*

1

DataFormat

:isRealizedBy

1..*

1

dct:publisher/dct:creator1..*1


Deliverable3.4 50

6.2 Templates

6.2.1 Generaltemplateforallservices

Attribute UsageNotesObligation

Example

dct:title thenameoftheservice M

dct:description containsadescriptionoftheservice M

rdfs:comment notesandcomments O

dct:publisher theagentmakingtheserviceaccessible,if

any

O

dct:contributor theagentresponsiblefordescribingthe

serviceintheARIADNECatalogue

O

dct:creator theagentthatcreatedtheservice O

owner theagentthatisthelegalownerofthe

service

O

legalResponsible theagentthatislegallyresponsiblefor

theservice

M

scientificResponsible theagentthatisscientificllyresponsible

fortheservice

O

technicalResponsible theagentthatistechnicallyresponsible

fortheservice

O

native-subject asubjectfromavocabularyinusebythe

originalowneroftheresource

M

hasAttachedDocuments thedocumentsattachedtotheservicefor

illustrationpurposes(includingvideos)

O

developer Theagentwhodevelopedtheservice O

functionality Amultivaluedpropertytoqualifythe

serviceinadditiontotheAATterms

O 3Dvisualisation,

foaf:homepage URLtotheservicehomepage R

dct:issued Dateofformalissuance(e.g.,publication)

oftheservice.

M 2013-04-24

dct:modified Mostrecentdateonwhichtheservice

waschanged,updatedormodified.Ifnot

specified,theissueddatewillbeused

automatically.

M 2013-04-24

exportFacility Iftheserviceprovidesexportfunctionality

forthedatasetsonwhichitoperates,

supplyalistofformat.

O CSV

hasTechnicalSupport Theagentofferingtechnicalsupportfor

theservice,ifany

O


Deliverable3.4 51


Example

consumedMedia Themediatypeoftheobjectshandledby

theservice.ThelistofpossiblemediaType

isopen

M “image”,“audio”,“video”,“text”,“3Dmodel”,“2Dmodel”

producedMedia Themediatypeofobjectscreatedbythe

service.SamevaluesasconsumedMedia

M

consumedFormat TheMIMEtypeoftheobjectshandledby

theservice

M

producedFormat TheMIMEtypeoftheobjectscreatedby

theservice.

M

supportedLanguage Thelanguagessupportedbythepossible

GUI

O

accessURL URLtotheserviceaccesspage M

6.2.2 Additionaltemplateforstandaloneservices


Example

dbpedia-owl:operatingSystem

TheOSplatform

requiredbythe

service

Mdbpedia:Cross-platform

dbpedia-owl:programmingLanguage

Mifsource

codeis

available

dbpedia:Java_(programming_l

anguage)

dbpedia-owl:status M InProgress,available

dbpedia-owl:latestReleaseVersion

R

dbpedia-owl:license M

dcat:downloadURL R

dcat:byteSize O

isInRepository O

hasAPI atextualdescription

oftheserviceAPI;if

any

O

hasComponents thecomponents

requiredforthe

O


Deliverable3.4 52


Example

Servicetobeinstalled

andused,ifany

6.2.3 Additionaltemplateforwebservices


Example

hasAPI atextualdescriptionoftheserviceAPI;

ifany

O

6.2.4 AdditionalTemplateforinstitutionalservices


Example

contactPerson TheAgenttobecontactedinorderto

accesstheservice

R

6.2.5 MappingofADSrecordstoACDMinXSLT

This is an example of the XSLT template used for data conversion from the legacy ADS format to

ACDMisprovided.

<?xmlversion="1.0"encoding="utf-8"?>

<xsl:stylesheetversion="2.0"

xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

xmlns:dcterms="http://purl.org/dc/terms/"

xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"

xmlns:dc="http://purl.org/dc/elements/1.1/"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:dcat="http://www.w3.org/ns/dcat#"

xmlns:foaf="http://xmlns.com/foaf/"

xmlns:dcmitype="http://purl.org/dc/dcmitype/"

xmlns:dbpedia-owl="http://dbpedia.org/ontology/"

xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"

xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"

xmlns:sch="http://purl.oclc.org/dsdl/schematron"

xmlns:skos="http://www.w3.org/2004/02/skos/core#"

xmlns:vcard="http://www.w3.org/2006/vcard/ns#"

xmlns:aat="http://vocab.getty.edu/aat/"

xmlns:acdm="http://registry.ariadne-infrastructure.eu/"

xmlns:owl="http://www.w3.org/2002/07/owl#"

xsi:schemaLocation="http://archaeologydataservice.ac.uk/advice/archiveSchema">

<xsl:strip-spaceelements="*"/>

<xsl:outputmethod="xml"version="1.0"encoding="utf-8"indent="yes"/>

<xsl:templatematch="/">

<acdm:ariadne>

Deliverable3.4 53

<acdm:ariadneArchaeologicalResource>

<xsl:elementname="acdm:collection">



<xsl:elementname="acdm:publisher">

<xsl:elementname="foaf:name">ArchaeologyDataService</xsl:element>

<xsl:elementname="acdm:typeOfAnAgent">Organization</xsl:element>

</xsl:element>



<xsl:for-eachselect="//Actors/actor">

<xsl:iftest="@type='creator'">

<xsl:iftest="name">

<xsl:elementname="acdm:contributor">

<xsl:elementname="foaf:name">

<xsl:value-ofselect="name/text()"/>

</xsl:element>

<xsl:element

name="acdm:typeOfAnAgent">Person</xsl:element>

</xsl:element>

</xsl:if>

<xsl:iftest="organisation">

<xsl:elementname="acdm:contributor">


<xsl:value-ofselect="organisation/text()"/>

</xsl:element>

<xsl:element

name="acdm:typeOfAnAgent">Organization</xsl:element>

</xsl:element>

</xsl:if>

</xsl:if>

</xsl:for-each>



<xsl:for-eachselect="//Coverage/subjects/subject">

<xsl:elementname="acdm:nativeSubject">

<xsl:elementname="skos:Concept">

<xsl:elementname="skos:prefLabel">

<xsl:value-ofselect="text()"/>

</xsl:element>

</xsl:element>

</xsl:element>

</xsl:for-each>



<xsl:for-eachselect="//archive/title">

<xsl:elementname="dcterms:title">


</xsl:element>

</xsl:for-each>



<xsl:for-eachselect="//description">

<xsl:elementname="dc:description">


</xsl:element>

</xsl:for-each>



<xsl:for-eachselect="//published/firstReleased">

<xsl:elementname="dcterms:issued">


</xsl:element>

</xsl:for-each>



<xsl:for-eachselect="//published/lastUpdated">

<xsl:elementname="dcterms:modified">


</xsl:element>

</xsl:for-each>

Deliverable3.4 54

<xsl:for-eachselect="//id">

<xsl:elementname="acdm:originalId">


</xsl:element>

</xsl:for-each>



<xsl:elementname="dc:language">en</xsl:element>



<xsl:for-eachselect="//doi">

<xsl:elementname="dcat:landingPage">

http://dx.doi.org/<xsl:value-of

select="text()"/>

</xsl:element>

</xsl:for-each>



<xsl:element

name="acdm:accessPolicy">http://archaeologydataservice.ac.uk/advice/termsOfUseAndAccess</xsl:element>



<xsl:elementname="dcterms:accessRights">ADSTermsand

Conditions</xsl:element>



<xsl:for-eachselect="//Coverage/periods/period">



<xsl:elementname="acdm:temporal">

<xsl:elementname="acdm:periodName">

<xsl:element

name="skos:Concept">

<xsl:element

name="skos:prefLabel">

<xsl:value-of

select="text()"/>

</xsl:element>

</xsl:element>

</xsl:element>

</xsl:element>

</xsl:for-each>

<xsl:for-eachselect="//Coverage/temporal/dateRange">




<xsl:for-eachselect="startYear">

<xsl:elementname="acdm:from">

<xsl:value-of

select="text()"/>

</xsl:element>

</xsl:for-each>



<xsl:for-eachselect="endYear">

<xsl:elementname="acdm:until">

<xsl:value-of

select="text()"/>

</xsl:element>

</xsl:for-each>

</xsl:element>

</xsl:for-each>



<xsl:elementname="acdm:spatial">



<xsl:for-eachselect="//Coverage/locations/location">

<xsl:choose>

<xsl:whentest="@type='TGN'">

<xsl:element

name="acdm:placeName">

Deliverable3.4 55

<xsl:value-of

select="text()"/>

</xsl:element>

</xsl:when>

<xsl:whentest="@type='None'

andcontains(text(),'World')">

<xsl:element

name="acdm:placeName">

<xsl:value-of

select="text()"/>

</xsl:element>

</xsl:when>

<xsl:otherwise/>

</xsl:choose>

</xsl:for-each>



<xsl:for-eachselect="//Coverage/coordinates/world">

<xsl:element

name="acdm:coordinateSystem">

<xsl:value-ofselect="@type"/>

</xsl:element>

</xsl:for-each>



<xsl:for-each

select="//Coverage/coordinates/world/latitude">

<xsl:elementname="acdm:lat">


</xsl:element>

</xsl:for-each>



<xsl:for-each

select="//Coverage/coordinates/world/longitude">

<xsl:elementname="acdm:lon">


</xsl:element>

</xsl:for-each>



<xsl:for-each

select="//Coverage/coordinates/boundingBox/southLatitude">

<xsl:element

name="acdm:boundingBoxMinLat">


</xsl:element>

</xsl:for-each>



<xsl:for-each

select="//Coverage/coordinates/boundingBox/westLongitude">

<xsl:element

name="acdm:boundingBoxMinLon">


</xsl:element>

</xsl:for-each>



<xsl:for-each

select="//Coverage/coordinates/boundingBox/northLatitude">

<xsl:element

name="acdm:boundingBoxMaxLat">


</xsl:element>

</xsl:for-each>



<xsl:for-each

select="//Coverage/coordinates/boundingBox/eastLongitude">

<xsl:element

name="acdm:boundingBoxMaxLon">

Deliverable3.4 56


</xsl:element>

</xsl:for-each>

</xsl:element>



<xsl:for-eachselect="//acdmType">

<xsl:element

name="acdm:archaeologicalResourceType">


</xsl:element>

</xsl:for-each>

</xsl:element>

</acdm:ariadneArchaeologicalResource>

</acdm:ariadne>

</xsl:template>

</xsl:stylesheet>

6.2.6 MappingofFastiOnline/AIACrecordstoACDMinXSLT

This is anexampleof theXSLT templateused for data conversion from the legacyAIAC format to

ACDMisprovided.

<?xmlversion="1.0"encoding="utf-8"?>

<xsl:stylesheetversion="2.0"

xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

xmlns:dcterms="http://purl.org/dc/terms/"

xmlns:oai_dc="http://www.openarchives.org/OAI/2.0/oai_dc/"

xmlns:dc="http://purl.org/dc/elements/1.1/"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:dcat="http://www.w3.org/ns/dcat#"

xmlns:foaf="http://xmlns.com/foaf/"

xmlns:dcmitype="http://purl.org/dc/dcmitype/"

xmlns:dbpedia-owl="http://dbpedia.org/ontology/"

xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"

xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"

xmlns:sch="http://purl.oclc.org/dsdl/schematron"

xmlns:skos="http://www.w3.org/2004/02/skos/core#"

xmlns:vcard="http://www.w3.org/2006/vcard/ns#"

xmlns:aat="http://vocab.getty.edu/aat/"

xmlns:acdm="http://registry.ariadne-infrastructure.eu/"

xmlns:owl="http://www.w3.org/2002/07/owl#"

xmlns="http://archaeologydataservice.ac.uk/advice/archiveSchema"

xmlns:dct="http://purl.org/dc/terms"

xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"

>

<xsl:strip-spaceelements="*"/>

<xsl:outputmethod="xml"omit-xml-declaration="yes"version="1.0"encoding="utf-8"indent="yes"/>

<xsl:templatematch="/">

<acdm:ariadne>

<acdm:ariadneArchaeologicalResource>

<xsl:elementname="acdm:collection">



<xsl:for-eachselect="//dc:publisher">

<xsl:iftest="text()!=''">

<xsl:elementname="acdm:publisher">



</xsl:element>

<xsl:element


</xsl:element>

</xsl:if>

Deliverable3.4 57

</xsl:for-each>



<xsl:for-eachselect="//dc:owner">


<xsl:elementname="acdm:owner">



</xsl:element>

<xsl:element


</xsl:element>

</xsl:if>

</xsl:for-each>



<xsl:for-eachselect="//*[local-name()='technicalResponsible']">


<xsl:elementname="acdm:technicalResponsible">



</xsl:element>

<xsl:element


</xsl:element>

</xsl:if>

</xsl:for-each>



<xsl:for-eachselect="//*[local-name()='scientificResponsible']">


<xsl:elementname="acdm:scientificResponsible">



</xsl:element>

<xsl:element

name="acdm:typeOfAnAgent">Person</xsl:element>

</xsl:element>

</xsl:if>

</xsl:for-each>



<xsl:for-eachselect="//dc:title">


<xsl:elementname="dcterms:title">


</xsl:element>

</xsl:if>

</xsl:for-each>



<xsl:for-eachselect="//dc:identifier">


<xsl:elementname="dcat:landingPage">


</xsl:element>

</xsl:if>

</xsl:for-each>



<xsl:for-eachselect="//dc:description">


<xsl:elementname="dc:description">


</xsl:element>

</xsl:if>

</xsl:for-each>



<xsl:for-eachselect="//dc:issued">

Deliverable3.4 58

<xsl:elementname="dcterms:issued">


</xsl:element>

</xsl:if>

</xsl:for-each>



<xsl:for-eachselect="//dc:modified">


<xsl:elementname="dcterms:modified">


</xsl:element>

</xsl:if>

</xsl:for-each>



<xsl:for-eachselect="//*[local-name()='originalId']">


<xsl:elementname="acdm:originalId">


</xsl:element>

</xsl:if>

</xsl:for-each>



<xsl:for-eachselect="//dc:language">


<xsl:elementname="dc:language">


</xsl:element>

</xsl:if>

</xsl:for-each>



<xsl:for-eachselect="//dc:accessRights">


<xsl:elementname="dcterms:accessRights">


</xsl:element>

</xsl:if>

</xsl:for-each>





<xsl:variablename="countTemporal">

<xsl:value-ofselect="count(//dc:coverage/dc:temporal)"/>

</xsl:variable>

<xsl:for-eachselect="//dc:coverage/dc:temporal">




<xsl:for-eachselect="from">

<xsl:elementname="acdm:from">

<xsl:iftest="contains(text(),'+')">

<xsl:value-of

select="substring-after(text(),'+')"/>

</xsl:if>

<xsl:iftest="contains(text(),'-')">

<xsl:value-of

select="text()"/>

</xsl:if>

</xsl:element>

</xsl:for-each>



<xsl:for-eachselect="until">

<xsl:elementname="acdm:until">

<xsl:iftest="contains(text(),'+')">

<xsl:value-of

select="substring-after(text(),'+')"/>

</xsl:if>

Deliverable3.4 59

<xsl:iftest="contains(text(),'-')">

<xsl:value-of

select="text()"/>

</xsl:if>

</xsl:element>

</xsl:for-each>

</xsl:element>

</xsl:for-each>



<xsl:for-eachselect="//dc:spatial/geo:Point">

<xsl:iftest="//geo:lat/text()!=''or//geo:lon/text()!=''">

<xsl:elementname="acdm:spatial">



<xsl:for-eachselect="//geo:lat">

<xsl:elementname="acdm:lat">

<xsl:value-of

select="text()"/>

</xsl:element>

</xsl:for-each>



<xsl:for-eachselect="//geo:lon">

<xsl:elementname="acdm:lon">

<xsl:value-of

select="text()"/>

</xsl:element>

</xsl:for-each>

</xsl:element>

</xsl:if>

</xsl:for-each>



<xsl:for-eachselect="//skos:Concept">


<xsl:elementname="acdm:nativeSubject">

<xsl:elementname="skos:Concept">

<xsl:element

name="skos:prefLabel">

<xsl:value-of

select="text()"/>

</xsl:element>

</xsl:element>

</xsl:element>

</xsl:if>

</xsl:for-each>



<xsl:element

name="acdm:archaeologicalResourceType">Event/interventionresources</xsl:element>



<xsl:element

name="dcterms:isPartOf">www.fastionline.org</xsl:element>



</xsl:element>

</acdm:ariadneArchaeologicalResource>

</acdm:ariadne>

</xsl:template>

</xsl:stylesheet>


Deliverable3.4 60

7 ARIADNEMappingDetails

Thischapterpresentsadetaileddescription,foreachpartner,ofthevariousmappingscarriedoutto

encodelegacyinformationconcerningdatasets,standardsandservices, intheACDMformatandin

theotherformatsusedtofosterintegrationwithintheproject.

7.1 ADSdatasets

Three broad categories of ADS resources corresponding to six ARIADNE

ArchaeologicalResourceTypeswereuploadedintotheACDMregistry:

1. Fieldworkarchives–derivedfromADSarchives

2. Event/interventionresources,suchasgreyliteraturereports–derivedfromtheADSlibrary

ofunpublishedfieldworkreports

3. Sitesandmonumentsdatabasesorinventories–derivedfromADSArchSearchcatalogue

4. Scientificdatasets,suchasdatabasesofradiocarbondates–derviedfromADSarchives

5. Artefactdatabases,orartefactimagecollections–derivedfromADSarchives

6. Burialdatabases–derivedfromADSarchives

AllADSarchivesaredescribedinaninternallydevelopedcollectionsmanagementsystem.TheADS

ArchSearch catalogue and the library of unpublished fieldwork reports are described in separate

Oracledatabases.AlloftheseADSresourcesaredescribedinDublinCorecompliantmetadata,with

specificschemagenerallydrawnfromMIDASHeritage(theUKHistoricEnvironmentDataStandard).

MIDAS isaBritishculturalheritagestandard for recording informationonbuildings,archaeological

sites,shipwrecks,parksandgardens,battlefields,areasofinterestandartefacts.Thedatastandard

suggests the minimum level of information needed for recording heritage assets and covers the

procedures involved in understanding, protecting and managing these assets. It also provides

guidelines on how to support effective sharing of knowledge, data retrieval and long-term

preservation of data.MIDASHeritage is freely available to anyone interested in recording historic

environmentinformation.Itisusedbynationalgovernmentorganisations,localauthorities,heritage

sector organisations, amenity groups and societies, the research community and professional

contractors.1

As an example, the ADS Library of Unpublished Fieldwork Reports was described as a single

Collection within the ACDM, although it is comprised of thousands of textualDocuments. Thecollectionisencodedinaschemacalled“archiveSchema”whilethetextualDocumentsareencodedinacustomisedDublinCore.ExamplesofnativeandACDMrecords,aswellasthemappingbetween

them,aregivenbelow.

7.1.1 ADSCollectionlevelrecordmappings

ACDMTerm ADSarchiveSchema

acdm:nativeSubject archive.Coverage.subjects.subject

acdm:publisher ArchaeologyDataService

acdm:contributorarchive.Actors.actor[type="creator"].nameOR

archive.Actors.actor[type="creator"].organisation

1https://historicengland.org.uk/images-books/publications/midas-heritage/


Deliverable3.4 61

ACDMTerm ADSarchiveSchema

acdm:typeOfAnAgent Person/organization

dcterms:title archive.title

dc:description archive.description

dcterms:issued archive.published.firstReleased

dcterms:modified archive.published.lastUpdated

acdm:originalId archive.id

dc:language en

dcat:landingPage "http://dx.doi.org/"+archive.doi

acdm:accessPolicyhttp://archaeologydataservice.ac.uk/advice/termsOfUseAnd

Access

dcterms:accessRights ADSTerms&Conditions

acdm:archaeologicalResourceType archive.acdmType

acdm:periodName archive.Coverage.periods.period

acdm:placeName archive.Coverage.locations.location[type=TGN]

acdm:coordinateSystem archive.Coverage.coordinates.world[type]

acdm:lat archive.Coverage.coordinates.world.latitude

acdm:lon archive.Coverage.coordinates.world.longitude

acdm:boundingBoxMinLat archive.Coverage.coordinates.boundingBox.southLatitude

acdm:boundingBoxMinLon archive.Coverage.coordinates.boundingBox.westLongitude

acdm:boundingBoxMaxLat> archive.Coverage.coordinates.boundingBox.northLatitude

acdm:boundingBoxMaxLon archive.Coverage.coordinates.boundingBox.eastLongitude

7.1.2 ADSMappingsforindividualtextualdocuments

ACDMTerm ExtendedDC(GLL)

acdm:nativeSubject dc:subjectMonuments,dc:subjectFinds


Deliverable3.4 62

ACDMTerm ExtendedDC(GLL)

dcterms:isPartOf numberOfCollection–originalId

dcterms:title dc:title

dcterms:issued dc:published

acdm:originalId dc:identifier

dc:language en

dcat:landingPage "http://dx.doi.org/"+dc:identifier

acdm:accessPolicyhttp://archaeologydataservice.ac.uk/advice/termsOfUse

AndAccess

dcterms:accessRights ADSTerms&Conditions

acdm;archaeologicalResourceType Event/interventionresources

7.1.3 ADSterminologicalmappings

The mappings from ADS native subject terms to the Getty AAT were undertaken using the USW

mapping tool by a member of ADS staff with a degree in Archaeology, and checked by a senior

archaeologist. Native terms in the ADS catalogue are described according to a number ofMIDAS-

compliant thesauri, which are approved by the UK Forum for Information Standards in Heritage

(FISH) and all of which are available at heritagedata.org. The primary thesauri from which ADS

subjecttermsaredrawnare:

• FISHThesaurusofMonumentTypes

• FISHArchaeologicalObjectsThesaurus

• FISHMaritimeCraftTypesThesaurus

• FISHBuildingsMaterialsThesaurus

• FISHComponentsThesaurus

AllmatchesweredescribedasBroad,Exact,orClose.Section5.2providesthenumbersofmatches

ofeachtype.Asmightbeexpectedgiventhesimilarityofcontent, thehighestproportionofExact

Matcheswas for theArchaeologicalObjectsThesuarus,witha lowernumberofExactMatches for

MonumentTypes.

7.2 AIAC–FastiOnline

TheFastidatamodelisstructuredaroundaconceptof‘Season’,whichisaschemeofarchaeological

work.Eachofthesemusttakeplaceonasite inaparticularyear.Thesiterecordhasa location,a

name,amonumenttypeandadaterange.Thedaterangewillberelatedtoaperioddependenton

the location of the site. The data is held in a complex relational database, and made available

through theFastiOnlinewebportal. Thedata canbeviewed in several formats, includinganXML

representationusingtheOAI-PMH,whichwasusedtoingestthedataintotheARIADNEPortal.The

followingtableexplainsthemappings.


Deliverable3.4 63

ACDMTerm FastiMappingExplanation

dct:titleThiswascreatedusingacombinationofthesitename

andtheseasonyeare.g‘Baccano2004’

dct:descriptionThisusedastandardphraseconstructedusingthesite

nameandtheseasonyeare.g‘Fastirecordfor

interventionsintheyear2000atBaccano’

dct:issuedThedatefromthedatabaseofwhentheseasonrecord

wasregistered

dct:modifiedThedatethatthemostrecentsummarywasregistered

onthedatabase

dct:originalIdTheFastiseasoncode,joinedwithFastiandtheitemkey

fromthedatabaseinthiscasethecodeforseasonis

sea_cde.g.fasti.sea_cd.AIAC_1

dct:identifierTheURLforthisseasonresourceonFastie.g.

http://www.fastionline.org/season/AIAC_1

dct:languageSummariesinFastiarestoredintwolanguages,eachof

theseisaddedtotherecord

dct:accessRightsAlldatainFastiisunderthe

https://creativecommons.org/licenses/by-sa/4.0/license

dct:spatialThelatitudeandlongitudeofeachsitearestoredas

numbersinthedatabase,thesearepresentedasgeo:lat

andgeo:loninthexmlrepresentationoftheFastidataset

ariadne:archaeologicalResourceTypeTheexcavationrecordsinFastiareallofthetype

“Event/interventionresource”

TheFASTIportalisavailableasaservice,andwasuploadedtotheregistry.Thespecificationsarein

thetablebelow.


dct:titleThiswascreatedusingacombinationofthesitename

andtheseasonyeare.g‘Baccano2004’


Deliverable3.4 64


dct:title FastiOnline

dct:description

Theaimofthesiteistoprovideadatabaseof

excavationssince2000,providingarecordinEnglishand

inthelocallanguageforeachseason.Wedonotpretend

toofferinformationonallsitesbeingexcavated,and

certainlynotonthoseexcavatedinthepast,ornever

excavated.Eachparticipatingcountryisresponsiblefor

uploadingthedataitgathers:somecountries’records

aremorecompletethanothers.

foaf:homepage http://www.fastionline.org

dct:issued 2006-09-07

acdm:exportFacility CSV

acdm:consumedMedia image,text,video

acdm:producedMedia HTML

acdm:consumedFormat text/html,application/pdf

acdm:producedFormattext/html

acdm:supportedLanguage

English,Romanian,Slovenian,Macedonian,Bulgarian,

Serbian,Croatian,Italian,French,Arabic,Albanian,

Spanish,Montenegrin,Ukrainian,Catalan

acdm:accessURL http://www.fastionline.org

The complete Fasti concept model was mapped to the CIDOC CRM, which is presented in the

following figure. The terms are colour coded according to Fasti item keys, light blue for site

information,turquoiseforseasoninformation,greenforactor information,yellowforbibliographic

information, pink for Fasti FOLD&R information, red for volunteer information. The purple


Deliverable3.4 65

informationispresentedontheFastiportal,butisstoredinGeoNames.Thelatitudeandlongitude

are used to query the liveGeoNames database. The information in the orange boxes is stored as

‘Events’ in the Fasti model, these are combinations of actors, activities and times. These can be

unpackedintotheCIDOCCRMmodel,butforthisrepresentationtheyhavebeenleftasentities,to

preventthisillustrationfrombeingrepetitive.Therelationshipsofthesemappingsarenotcurrently

viewableforourusersintheFastiOnlinePortal.

Figure2:FasticonceptualmappingtoCIDOCCRM.

7.2.1 FastiTerminologyMappings

Themappings fromFastimonument types to theGettyAATwerecompleted in collaborationwith

USW. Thesemappings were then imported into the Fasti database and presented in the service,

andthencheckedmanually.ThemappingswerestoredintheFastidatabaseaslinksbetweenaFasti

concept URI e.g. http://www.fastionline.org/concept/attribute/castle and an AAT URI

http://vocab.getty.edu/aat/300006891. Thesemappings canbe viewed through theFasti Concepts

Pages.For theOAI-PMHrepresentation, theAATURI’swere resolved to thexl:prefLabel,and then

incorporatedintotheARIADNEportal.

Adetaileddescriptionof thePeriodOmappingsof the temporalentities recorded inFasti archives

were used for time integration within the ARIADNE Portal. The Fasti period data has been fully

incorporatedintothePeriodOdataset.ForPeriodO,withhttp://www.fastionline.orgassource,itwas

possible to establish directmappings between the Fasti period data and the PeriodO data of the

samename.


Deliverable3.4 66

7.3 ARHEO

In order to integrate its datasets in the ARIADNE Registry, ARHEO has delivered datasets

describing archaeological sites from the Historical Monuments List. The National

ArchaeologicalRepertoireformat,fromwhichthedeliveredinformationwasextracted,and

theACDMformat,usedtoencoderegistryinformation,coincidedtoalargeextent.Theterm

dct:titlewasfilledwiththegeneraltitleofthedataset,thatis,“ListofHistoricalMonuments

Sites”; the restof the fieldswere filledwith specific information taken from thedatabase

itself.

Inparticular,thedct:descriptionfieldwasfilledinformationcomingfromthe“Description”

fieldofthesourcedatabase,containingshortinformationregardingthearchaeologicalsite.

Thefielddct:identifierpresentsalphanumericaldataspecificonlytothearchaeologicalsites

contained in the Archaeological Monuments List; this is also a unique identifier and it is

specified within the source in the field “Cod LMI”. The archaeological sites that are not

included in Historical Monuments List (LMI) do not hold such an indicator, being

distinguishedexclusively by thedct:origicalId field. The fielddct:language field, specifyingthe language inwhich the information is registered,was filledusingnewly created string,

havingno correspondenceswithin the source fields. The fielddct:temporal is referring tothearchaeologicalsitechronologyandwithinthesourcethisiscorrespondingtotherecords

from the field called “Descoperiri in cadrul sitului” and the subfield “Epoca(Datare)”.New

textual information was created also for the dct:accrualPeriodicity field, referring to therhythm in which updates are made within the native documents. Source records do not

provide exact matching information for this field; values have been derived indirectly by

gatheringinformationin“Dataultimeimodificariafisei”field,whichisnumericaltypedata

representinga calendardata.Thedct:landingPage fieldwasderived fromtheURLofeach

record in the original dataset. The fields dct:creator, dct:contributor, dct:owner anddct:legalResponsible hold newly created textual information, referring to the person

responsible for creating,administratingandholdingof thedata.The technicalResponsiblefieldcontainsinformationontheadministratorsofthelegacydatabase,independentlyfrom

thearchaeologicalsiterecordsfields.

TablebelowshowstheARHEOmappingsindetail.

OriginalField FieldDescription ACDMField Comment

nameofthe

recorddcterm:title

dcterms:isPartOf

Descriere Thefieldistexttypeofferingshortinformationaboutthearchaeologicalsitewhoisreferingto

dcterms:description


Deliverable3.4 67


entrydate

dcterms:issued

ussuallyisthesamedateasdcterms:modified

Dataultimeimodificăriafişei

thefieldisnumericaltype,indicatingthelastupdateofthesheet

dcterms:modified

dcterms:accrualPeriodicity

CodRAN numericaltypedata,representingtheuniquenumbergiventoeacharchaeologicalsiteregisteredinthedatabase

acdm:originalId

Tip texttypedata,offeringinformationaboutthenatureofthearchaeologicalsite(eg.Fotificatie)

dcat:keyword

N/A notafieldinthedatabase

dcterms:languagedefault“Romanian”

Epocă(Datare) texttypedata,

indicatingthe

period/ageofthe

archaeologicalsite

acdm:temporal

N/A notafieldinthe

databaseacdm:country

defaul“Romania”

N/A acdm:from

N/A acdm:to


Deliverable3.4 68


LocalizeazăpehartaRomaniei

thefieldisalink(URL)whichgoestoRomania'smapwherethearchaeologicalsitesarelocated.Fromthereinformationlikespatialcoordinatescanbecolected.Thecoordinatesareexpressedindegrees,decimals(eg.21.50501)

acdm:spatialLon

http://map.cimec.ro/Mapse

rver/?layer=ran&cod=15770

9.16

LocalizeazăpehartaRomaniei

thefieldisacctuallyalink(URL)whogoestoRomania'smapeherethearchaeologicalsitesarelocated.Fromheretherecanbecolectedinformationlikespatialcoordinates.Thecoordinatesareexpressedindegrees,decimals(eg.46.06483)

acdm:spatialLat

http://map.cimec.ro/Mapse

rver/?layer=ran&cod=15770

9.16

itisnotafieldinthedatabase,thisinfocanbetakenfromthebrowser

dcat:landingPage

ex.

http://ran.cimec.ro/sel.asp?

descript=alios-masloc-timis-

situl-arheologic-de-la-alios-

valea-aliosu-s-cod-sit-ran-

157709.16


Deliverable3.4 69


Instituţia atexttypefieldwheretheinstitutionwhodeliveredtheinformationtocIMECisspecifiedinordertobuildtheRANsheet

dcterms:publisher

dcterms:contributor

N/A

dcterms:creator

cIMEC-creating,

administrationand

responsabilityoftheRAN

sheetswhoconstitutethe

databaseareregulatedby

law

N/A

acdm:owner

cIMEC-creating,

administrationand




law

N/A

acdm:legalResponsible

cIMEC-creating,

administrationand




law

Colectiv thisfieldhasanotherthreesubfields:Name,SurnameandRole

acdm:scientificResponsible


Deliverable3.4 70


N/A

acdm:technicalResponsible

Thetechnicalpersonresponsibleismentionedinthelowerpartofthewebpage,thereisnospecificfieldwithinthesheet

acdm:archaeologicalResourceType

acdm:nativeSubject

N/A

acdm:accessPolicy

isregulatedbylaw/copyrightoftheMinistryofCulture.ThecontentoftheappisheldandadministeredbycIMEC/HeritageInstituteaccordinglytoOMCCno.2458/21.10.2014

N/A

acdm:accessRights

itisregulatedbylaw/copyrightoftheMinistryofCulture.ThecontentoftheappisheldandadministeredbycIMEC/HeritageInstituteaccordinglytoOMCCno.2458/21.10.2014

dcterms:rights

dcterms:extent

dcterms:audience


Deliverable3.4 71

7.4 ARUP-CASdatabase

ARUP-CAS contribution to ARIADNE concerned a database of aerial photographs (AAP) used for

archaeological investigation. The AAP database contains more than one thousand images of

archaeologicalsites.TheAAPcontainsalargenumberofaerialimages(c.20,000)collectedduringthe

intensiveaerial surveywhichbegan immediatelyafterbeingallowedby thestate systemand lasts

until today. Most of the photographs come from the Prague CAS Institute´s survey activities

conductedwith itsownaircraft.Thephotographsexist inbothanalogueanddigital form. In2012-

2015,asystematiccatalogueofexistingphotosandcorrespondingsiteswascreatedaspartof the

Archaeological Map of the Czech Republic project and other collaborating projects on aerial

archaeology.Photographsfromseveralotherarchaeological institutionsinBohemiahavealsobeen

included.Sitesidentifiedfromtheairasspecificmarksoncropsorsoilandmanystandinghistorical

monumentshavebeenrecorded.Aerialphotographscanbedescribedandlinkedtootherdatabase

objects by means of the specialized AMCR module. The rectification, geo-referencing and

vectorisation of selected aerial photos is currently being carried out independently of AMCR

activities.AschemaoftheAAPdatabaseisprovidedinfigurebelow.

Figure3:ARUP-CASIAPAerialImagesdatabaseschema

DetailsoftheIAPdatabasefieldsandthewaytheyweremappedtoACDMareprovidedinthetable

below.

ACDM Aerial_ImagesDatabaseFields

dcterm:title LOKALITA.NAZEV(nameofsite)

dcterms:ispartof ArchiveofAerialImages

dc:description DOKUMENT.IDENT_CELY(documentID)

LOKALITA.KATASTR(cadaster)

LOKALITA.DRUH(typeofsite)


Deliverable3.4 72

ACDM Aerial_ImagesDatabaseFields

dcterms:issued EXTRA_DATA.DATUM_VZNIKU(dateofacquisition)

dcterms:modified DOKUMENT.DATUM_VLOZENI(dateofentry)

dcterms:accuralPeriodicity n/a

acdm:originalID DOKUMENT.IDENT_CELY

dcat:keyword LOKALITA.DRUH(typeofsite)

TVAR.TVAR(typeofshapes–eg.circularcropmarksetc.)

KOMPONENTA_DOK.AREAL(typeofactivityarea)

dc:language DOKUMENT.JAZYK_DOKUMENTU

acdm:temporal KOMPONENTA_DOK.OBDOBI(period/culture)

acdm:country CzechRepublic

acdm:From Derivedfromperiod(KOMPONENTA_DOK.OBDOBI)

acdm:To Derivedfromperiod(KOMPONENTA_DOK.OBDOBI)

acdm:SpatialLon PIAN.CENTROID_E(WGS-84decimaldegrees)

acdmSpatialLat PIAN.CENTROID_N(WGS-84decimaldegrees)

dcat:landingPage Digitalarchive(inprogress)

acdm:publisher InstituteofArchaeologyCAS,Prague

acdm:contributor DOKUMENT.ODPOVEDNY_PRACOVNIK_VLOZENI(personresponsible

fordataentry)

acdm:creator DOKUMENT.AUTOR(author)

DOKUMENT.ORGANIZACE(authororganisation)

acdm:owner DOKUMENT.ORGANIZACE(authororganisation)

acdm:legalResponsible DOKUMENT.ORGANIZACE(authororganisation)

acdm:scientificResponsible DOKUMENT.AUTOR(author)

DOKUMENT.ORGANIZACE(authororganisation)

acdm:technicalResponsible DOKUMENT.ODPOVEDNY_PRACOVNIK_ARCHIVACE (responsible

archiver)


Sitesandmonumentsdatabasesorinventories

acdm:nativeSubject aerialarchaeologyimages

acdm:accessPolicy Digitalarchive(inprogress)

acdm:accessRights DOKUMENT.PRISTUPNOST(useraccessrights)

dc:rights Digitalarchive(inprogress)

dcterms:extent Numberofassociatedfiles(intheclassSOUBORY)

dcterms:audience professional


Deliverable3.4 73

7.5 CSIC-Incipit

CSIC has always emphasized the integrated treatment of information. For this reason, standalone

datasets have rarely been created; rather, the information generated bymost of its projects and

workgointoacentralinformationsystemwhichislinkedwithpreviousinformation,andfromwhere

it may be reused by future activities. This central information system is called the SIA+

(ArchaeologicalInformationSystem,enhancedversion).

ThedatasetisstoredasasingleMicrosoftJet4database,whichissharedonafileserverandusedby

a collection of server-side software components and client applications,most ofwhich have been

developed in house. So far, the dataset has been for internal use at Incipit CSIC only, and as a

consequenceitisnotexposedtothewebinanymanner.Thereisnowayinwhichitcanbeaccessed

throughregularHTTPinterfaces.However,CSIChastheinfrastructuretobuildandhostthem,sothis

would not be a difficult change to implement, at least from the technical point of view. From a

structuralpointofview,eachentity in theSIA+hasauniquecode that remainsuniqueacross the

wholesystem.Theoldestinformationinthedatasetdatesbacktothelate1980s.Thedatasetislive,

beingupdatedinanongoingbasis.Totalcurrentsizeinitsusualformatisover134MB.Information

comes mostly from Galicia (North-West Spain) and surrounding areas, although there is some

information fromother areas of Spain aswell as overseas (e.g.Uruguay). The free text fields of a

descriptivenaturearewritteninSpanish.BitsofGalicianandotherlocallanguagesappearnowand

thenasquotations.

CSIChasappliedpowerfulabstractionmanagementtechniquesfromtheverybeginning,sothatend

usersdonotneed toworryaboutdata implementationdetails, focusing insteadon informationat

theconceptual level.Forexample,mostusersatIncipitCSICdonotknoworcarehowtheirdatais

stored on the computer in terms of tables, fields or data types, or whether there is a relational

databaseoranobject-orientedstorageenginebehindtheuserinterface.

Finally,weoftenconvertsubsetsofdatafromtheSIA+forvariousresearchorreportingpurposes,

usingXMLandotherintermediaryformats.Itwasveryeasytoexportorconvertpartsofthedataset

into anyXML-based schemaonce the structure is clearlydefined.CSIChasdefineda singleACDM

record for describing its database, whose details are provided in the table below. Using general

knowledgeaboutthedatabaseitselfratherthanspecificdatabasefieldsandvaluescreatedmostof

theACDMinformation.


PlaceName dcterm:title

Databaseisaunique

resource

dcterms:isPartOf

Description “Archaeologicalsites

ofNorth-WestSpain

documentedby

IncipitCSICduring

fieldworkinthe

1990sand2000”

dcterms:description

Lastmodification

date

dcterms:modified


Deliverable3.4 74


Code acdm:originalId

es dcterms:language

CCA acdm:temporal

Spain acdm:country

UtmX acdm:spatialLon

UtmY acdm:spatialLat

dcat:landingPage

CSIC dcterms:publisher

Variouscontent

providers

dcterms:contributor

CSIC

dcterms:creator

CSIC acdm:owner


CesarGonzalez-

Perez


CesarGonzalez-

Perez


Type acdm:archaeologicalResourceType

7.6 CyprusInstitute-STARCrepository

CyI-STARC repository (http://public.cyi.ac.cy/starcRepo) currently contains 16 datasets, which are

constantlyupdatedandgrowing innumber.Theheterogeneityofthedatacollection,that includes

archaeological sites, museum items, architectural structures and inscriptions, made us to adopt

differentmetadata schema according to the specific needs. In particular we adopted 3metadata

schemas:

1. STARCmetadataschema

2. CustomizedLIDO

3. CyInscriptionmetadataschema.


Deliverable3.4 75

7.6.1 STARCmetadataschema

Themajorityof availablemetadata schemastandardshavenotbeendeveloped todescribedigital

media files, such as 3D objects. Datasets produced by STARC team refer mostly to 2D and 3D

archaeological data. To fully describe the data produced and respond to the needs of the STARC

researchgroup,aninternalmetadataschema(STARCmetadataschema)wasdeveloped.

The schema ismostly based on LIDO (www.lido-schema.org) and CARARE (www.carare.eu) and is

CIDOC-CRMcompliant.

TheSTARCmetadataschemahasaglobalwrappernamedPROJECT,sub-dividedintofourconceptual

areas:

1. General Information: itgivessynthetic informationaboutadministrativedata, language

anddateofcreationofthemetadataentry,aswellasashortdescription,includingthe

sourceareaanddatingoftheculturalheritageitrefersto.

2. Cultural Heritage Asset: this area contains detailed information about the cultural

heritage that themetadata refers to,namelyprecise source location (coordinates)and

dating,adescriptionofitsappearanceandhistory,andtherightsoftheresource.

3. Digital Resource Provenance Data: it gives detailed information on the digital data

acquisition process. It provides information about the operators and the device

employed (e.g. camera model, serial number, etc.). Also, it describes the acquisition

procedureincludingtheinstrumentationsettings(e.g.focallength,exposuretimeetc.).

4. DigitalResource:itdescribesthepost-processingmethods,includingthesoftwareused,

thedataformatandweight,andtherightsofthedigitalproduct.

7.6.2 CustomizedLIDO

STARC repository also stores the collection of icons of the Byzantine Museum in Nicosia, the

collectionofartworksoftheArtGalleryinNicosia,theIX-XXcenturyphotographicdatasetfromthe

privatecollectionDerAvedissian-Hawleyandacollectionofancientbooks.

TheitemsinthiscasearedescribedthroughacustomizedLIDOmetadataschema.Theartefactsare

described through title, IDnumber,date, technical details (e.g. dimension,material etc.), location,

short description and rights aswell as the link to thepage inwhich thedigital resource is stored,

togetherwithitsrights.Theschemasupportsmultilingualresources(specificallyEnglishandGreek).

7.6.3 CyInscriptionmetadataschema

CyI-STARC has developed a metadata schema to describe the corpus of Ancient Cypriot literary

inscriptions. Traditional schemas, like EpiDoc, the most used by the epigraphist community, are

focused on the epigraph itself. Instead, the CyInscription metadata schema, integrates

multidisciplinary information regarding the objects and also their digital “surrogate” (3D models,

photographic documentation, digital texts, transliterations, videos, audios, etc.). The schema is

organized in groups corresponding to different research domains divided in wrappers and sub-

wrappers.

1. ProjectInformation:givesinformationabouttheadministrativedataoftheproject,language

anddate,aswellasashortdescription.

2. RealWorldObjectcollection:thiswrappercontainsdetailed informationaboutthecultural

heritage themetadata refers to. Specifically, it describes the inscription alongwith all the

information related (the description of the inscription as text and the support of the

inscription),location(coordinates)anddating,andtherightsoftheresource.


Deliverable3.4 76

3. Digital Resource Provenance: it gives detailed information on the digital data acquisition

process, thedataprocessingand thedescriptionof thedigitaloutcome (2Dand3D)along

withitsdescriptionandrights.

4. Activity: it gives information about all the activitieswhichhaveoccurred and the relations

withotherresourcesofthecollection.

DetailsontheACDMmappingsperformedbyCyprusInstituteareshowninthefollowingtable:


General

Information/

Collection

nomeofthecollection dcterm:title

dcterms:isPartOf

General

Information/

Description

descriptionofthe

datasetandofthe

specificitem

dcterms:description

General

Information

/creation_date

dateofthecreationof

theentry

dcterms:issued

dcterms:modified


acdm:originalId

dcat:keyword Thisfieldwasfilled

accordingtothedataset

contents

General

Information/

Language

languageofthedataset dcterms:language

Cultural

heritageasset/

start_dateand

end_date

datingofthecultural

heritage

acdm:temporal

Cultural

heritageasset/

Location_name

geographicalpositionof

theculturalheritage

acdm:spatial

acdm:from

acdm:to

Cultural

heritageasset/

x

coordinateofthe

culturalheritage

acdm:spatialLon


Deliverable3.4 77


Cultural

heritageasset/

y

coordinateofthe

culturalheritage

acdm:spatialLat

Cultural

heritageasset/

IsShownAt

linktothelandingpage dcat:landingPage

General

Information/

Source

dcterms:publisher

General

Information/

Rights

dcterms:contributor

General

Information/

Source

dcterms:creator

Cultural

heritageasset/

Rights

acdm:owner

Digital

resources/

Rights


Digital

resources/

Rights


Digital

resources/

Rights



Thisfieldwasfilledin


contents

acdm:nativeSubject Thisfieldwasfilledin


contentsandtotheGetty

ResearchInstitute,Art&

ArchitectureThesaurus

Online

[http://www.getty.edu/res

earch/tools/vocabularies/a

at/]

acdm:accessPolicy

Digital

resources/

Rights

acdm:accessRights


Deliverable3.4 78


General

Information/

Rights

dcterms:rights

dcterms:extent

7.6.4 MappingstoCIDOC-CRM

AmappingofSTARCmetadatatoCIDOC-CRMwasattemptedwithintheproject.Afirstversionofthe

mapping was presented at the Annual Conference on Computer Applications and Quantitative

MethodsinArchaeologyinOslo(CAA2016).

7.6.5 CyIservicesforARIADNE

TheARIADNEportalmakesitpossibletoaccesstheSTARCrepository.Itispossibletodirectlyaccess

allthedatasetsbysearchingthroughvariousfieldsavailableinthesourcecollection:

• Identicationnumber

• Language

• Resourcetype

• Keywords

• Date

• Place

• Publisher

• Issueddate(thisfieldismissingintheitemsofthe“ByzantineMuseumcollection”)

• Creator

• Contributors

Allthedatasetsareshortlydescribed.

Thedatasetsarealsodividedandidentifiedbydifferenticonsaccordingtothegrouptheybelongto:

• fieldworkarchives,

• artefactdatabasesorimagecollections,

• sitesandmonumentsdatabasesorinventories

Allresourcesarepreciselylocatedonamapandtime-line.

7.7 DAIdatasets

The German Archaeological Institute (DAI) maintains a large aracheological database called

iDAI.obejcts Arachne. We have mapped datasets from several Arachne categories to ARIADNE,

namely:


Deliverable3.4 79

• Topographie (eng. Topography, http://arachne.dainst.org/category/?c=topographie):

Arachne’s most granular object unit, which is the superior context for all related classes,

whichincludeslandscapes,sites,andpartofsites.

• Bauwerke (eng. Buildings): This class comprises buildings andmonuments, which forms a

contextforsingleobjectrecordsandcouldbepartofalargersite.

• MehrteiligeDenkmäler(akaGruppen,eng.Multipartmonuments):Allkindsofgroups,which

are not buildings and topographic units, are subsumed into multipart monuments, e.g.

groupsofstatues,graveyards,hoards.

• Sammlungen(eng.Collections):Privateandmuseumcollectionsbelongtothisclass.

• Bücher (eng. Books): Digital reproduction, characterisation and context of classical study

printsfromthe16thto19thcentury.

• Inschriften (eng. Inscriptions): This class contains inscriptions and epigraphs depicted on

objects.

SincethedatasetsinArachnearecontextualisedandhighlyconnected,thebestcorrespondencesfor

thesecategoriesintheACDMdatamodelwere:

• Bauwerk,Gruppen,Topographie:Sitesandmonumentsdatabasesorinventories

• Buch,Inschrift,Sammlungen:Artefactdatabasesorimagecollections

For inscriptions and digitised books DAI has created two separate umbrella collections in the

ARIADNEregistry.

Themappingprocesswasmainlystraightforward.AproblemontheArachnesidewasthatthemost

completedatafordigitisedbookscomesinadifferentformatthantheothercategories.Aproblem

ontheACDMsidewastheveryspecificdateformatwheretheprecisedayneededtobespecified,

andthisinformationwassimplynotavailableforDAIdata.Themappingblueprintsforthecategories

and the corresponding conversion script can be found at https://github.com/dainst/arachne-oai-

pmh-scripts/tree/master/ariadne.

DAImappingactivitiesaredetailedinthefollowingtable.


KurzbeschreibungBauwerketc.,

InschriftOhneKlammern

dcterm:title books:separate

titles

"Arachne" dcterms:isPartOf inscriptions:the

carrier

"databaseofobjectsthatare

partthisgroup"etc.,Inschrift

dcterms:description books:separate

descriptions

creation dcterms:issued

last_modified dcterms:modified


http://arachne.dainst.org/entit

y/[ArachneEntityID]

acdm:originalId

"Archaeology" dcat:keyword


Deliverable3.4 80


"de" dcterms:language books:separate

languageinfo

acdm:temporal

->ort.Country acdm:country ortconnected

viaGazetteerid

->datierung.[datefromseveral

fields],

sammlungen.EntstehungDatum

acdm:from Datierung

connectedvia

foreignkey

->datierung.[datefromseveral

fields]

acdm:to Datierung

connectedvia

foreignkey

acdm:spatialLon

acdm:spatialLat

http://arachne.dainst.org/entit

y/[ArachneEntityID]

dcat:landingPage

"GermanArchaeological

Institute"

dcterms:publisher

KorrektorBauwerketc. dcterms:contributor

BearbeiterBauwerketc. dcterms:creator


Institute"

acdm:owner


Institute"



Institute"



Institute"



buch.classification,

bauwerk.Gebaeudetyp,

TopographieTypus,

Sammlungskategorie,

ArtDerGruppe

acdm:nativeSubject defaultisthe

categoryname

"http://arachne.dainst.org/info

/order"

acdm:accessPolicy

"CCBY-NC-ND3.0" acdm:accessRights


Institute"

dcterms:rights


Deliverable3.4 81


(numberofobjects) dcterms:extent

dcterms:audience

7.7.1 CIDOCCRMmapping

Arachne has a detailed CIDOC CRM mapping for most of its categories (see

https://arachne.dainst.org/categories). The mapping is available via an OAI-PMH interface

(http://arachne.uni-koeln.de/OAI-PMH/oai-pmh.xml?verb=Identify).

In addition, DAI pursued an experiment on the tight integration of detailed descriptions of single

items of research.We describe a practice-oriented approach to dealing with heterogeneous data

withthehelpofSemanticWebtechnologies,andpresentedaspecificusecaseaboutsculpturesand

integratingarcheologicalfindsfromvariousdatabases,includingArachne.

7.7.2 iDAI.objectsArachne

ArachneisthecentralObjectdatabaseoftheDAIandtheArchaeologicalInstituteoftheUniversity

ofCologne.

Arachne is intended toprovidearchaeologistsandClassicistswitha free internet research tool for

quicklysearchinghundredsofthousandsofrecordsonobjectsandtheirattributes.Thiscombinesan

ongoingprocessofdigitisingtraditionaldocumentation(storedonmediawhichareboththreatened

by decay and largely unexplored) with the production of new digital object and graphic data.

Wherever possible, Arachne follows a paradigm of highly structurized object-metadata which is

mappedtotheCIDOC-CRM,toaddressmachine-readablemetadatastrategiesoftheSemanticWeb.

This “structuredworld”ofArachne requires largeefforts in timeandmoneyand therefore is only

possibleforprivilegedareasofdata.Whileontheever-increasingrangeofnew,digitallyborndata,

inrealityonlyasmalleffort-per-objectratiocanbeapplied. Itthereforerequiresa“low-threshold”

processingstructurewhichislocatedinthe“unstructuredworld”ofArachne.Alldigital(graphicand

textual) information is secure on a Tivoli Storage System (featuring long-term multiple

redundandancy)anddistributedonlinethroughtheStorageAreaNetworkinCologneviaAFS.

Homepage:http://arachne.dainst.org

7.7.3 iDAI.vocab

ThenewDAIThesaurusofArchaeologicalConceptswasdesignedfromtheonsetasathesaurusof

Germanwordsandphraseswithmassivemultilingualsupport.Thecoreofourthesaurusisalistof

concepts related to the domain of archaeology (nouns, verbs, less frequently adjectives, but also

complex phrases that point to a specific object, such as “carrarischer Marmor”) all linked to the

correspondingtranslationsinawidespectrumofdifferentlanguages;wealsopurposedtoestablish

aminimalsetofrelationsbetweentheGermanterms(synonyms,directhyper-andhyponyms),and

to group the equivalent terms together; whenever it is possible, we intended also to resolve

equivalenttermsbyselectingonepreferredconcept.Inadditionweconnectourtermsandconcepts

bySKOS-linkstoexternalthesauriliketheArts&ArchitectureThesaurusoftheGettyInstitution.

Homepage:http://archwort.dainst.org/thesaurus/de/vocab/index.php


Deliverable3.4 82

7.7.4 IDAI.gazetteer

TheDAI,togetherwiththeCologneDigitalArchaeologyLaboratoryisdevelopingtheiDAI.gazetteer-

a web service connecting toponyms with coordinates. It was initially built as an authority file /

controlled vocabulary for any geo-related information in information systems of the DAI.

Furthermoreitismeanttolinkthesedatawithotherworldwidegazetteer-systems.

Homepage:http://gazetteer.dainst.org/

7.7.5 DAIsubjects

TheITinfrastructureoftheDAIcontainsmanydifferentsubjectspecificinformationsystems,e.g.for

excavations and surveys (iDAI.field), objects and publication of data (Arachne), bibliographical

information (Zenon) and digitised books (iDAI.bookbrowser). While places are already centralised

structureswithin the iDAI.gazetteer (http://gazetteer.dainst.org/)andall informationsystemsrefer

tothegazetteer,eachofthesystemshastheirownvocabularyfordescribingthestoredobjects.At

themomentworkisongoingtoharmonisethedifferentDAIthesauriintoonecommonstandardin

iDAI.vocab(http://archwort.dainst.org/).

For themapping activities in ARIADNE, the relevant vocabulary categories of the object database

Arachne were chosen, as Arachne contains, in contrast to iDAI.field, with more than 3.6 million

datasets,alargeamountofdatawhichisopenlyavailable.Thevocabularyofthefollowingcategories

weremappedtoGettyAAT:

• Topographie:55valuesmappedtoGettyAATfrom2differentvaluelists

• Bauwerke:176valuesmappedtoGettyAATfrom4differentvaluelists

• MehrteiligeDenkmäler:108valuesmappedtoGettyAATfrom6differentvaluelists

• Sammlungen:11valuesmappedtoGettyAATfrom2differentvaluelists

• Bücher:17valuesmappedtoGettyAATfrom3differentvaluelists

• Inschriften:19valuesmappedtoGettyAATfrom1valuelist.

7.8 DANSdatasets

7.8.1 DCCDtoplevelcollection

ThefollowingtableshowsdetailsconcerningthemappingbetweenDANSDCCDDendrochronology

datamodelandtheACDM,bothforautomaticmappingviaOAI-PMHandfor‘manual’entryintothe

registry.Inparticular,thetabledescribesthetoplevelcollectionvalidforallDCCDdatasets.Specific

usage notes and detailed comments for each DCCD entity mapping are provided in the related

columns.

Attribute UsageNotes DCCD Comment

dct:title DCCD:Digital

Collaboratoryfor

Cultural

Dendrochronology

dct:description DCCDstandsforDigital


Deliverable3.4 83


Collaboratoryfor

Cultural

Dendrochronologyand

isaninitiativeofDANS

(DataArchivingand

NetworkedServices)

andtheRCE(Cultural

HeritageAgencyofthe

Netherlands).This

internationaldigital

datalibraryofannual

growthringdata

containsdigitalgrowth

ringseriesandmean

chronologies,aswell

astheirdescriptiveand

interpretative

metadata.Thecontent

isdevelopedby

researchfrom

archaeologicalsites

(includingold

landscapes),

shipwrecks,buildings,

furniture,paintings,

sculpturesandmusical

instruments.The

archivecontainsdata

fromEuropean

institutes.



resource.

2009 ThedateDCCDrepositorystarted?


whichtheresourcewas

changed,updatedor

modified.

2015-11 Thedatethisinformationismodified,andnotaboutthecontentofthecollection

acdm:originalId Theoriginalidentifier

oftheresource

suppliedbythecontent

provider

dccd usethisincontentisPartOf


thatwillbecomputed


couldlooklike:

www.ariadne.eu+

Generatedbytheregistry


Deliverable3.4 84


prefixoftheprovider+

IDoftheresource

dcat:keyword Dendrochronology,Archaeology,Climatology,Wood,Dating



onevaluemustbe


nl,en,du,fr Multipleentries,forthemainlanguagesofourdatasets


navigatedtoinaWeb

browsertogainaccess

tothedataset,its

distributionsand/or


http://dendro.dans.knaw.nl

Nohttpsneeded


Resourcetorelevant

contactinformation


VCard[vcard-rdf].

Prof.dr.E.Jansma(projectleader)

CulturalHeritageAgency(RijksdienstvoorhetCultureelErfgoed)

POBox1600

NL-3800BPAmersfoort

TheNetherlands

E-mail:[email protected]

Usecontactinfofromwebsite.

Vcard?

acdm:accessPolicy URItostatementof



http://dendro.dans.kn

aw.nl/termsofuse



thedataresource

Themetadatawhichis

freeforuseandopen

accessisvisibletoany

userwhoisnotlogged

in.Togetaccessto

deeperinformation

levels,userregistration

isnecessaryand

differentlevelsof

accessareapplicable.

dct:rights Informationabout http://dendro.dans.kn


Deliverable3.4 85


rightsheldinandover

thedataresource

aw.nl/termsofuse

dct:audience Theprimary

audience(s)ofthe

resource

Dendrochronologists,

Archaeologists,

Historians

Focusonthe

CulturalHeritage.

dct:temporal SeetemporalRegion ALLAATperiods Note:diduse

Holocenefrom

AAT,butthatisnot

archaeologyproof!

dct:spatial SeespatialRegion Placename:World,

Europe

Boundingbox;

boundingboxof

Europe

Country:NA

Thenallcountries

separatewithout

boundingbox?

Belgium,Denmark,

France,Germany,

Latvia,Lithuania,

Netherlands,Poland,

Spain,UnitedKingdom

dct:accrualPeriodicity NA

dct:extent Thesizeofthedata

resource(i.e.,number

ofitemsinacollection,

numberofrecordsina

dataset,etc.)

Morethenfifty

thousandseriesof

tree-ring

measurements

Approximate

number;atthe

timeofdescribing

this


Associatesany

archaeologicalresource

withoneormore

categories(types),

drawnfromthe

followinglist:

• Fieldwork

archives

• Event/intervent

ionresources,

suchasgrey

literature

reports

• Sitesand

Scientificdatasets usedtobe

ariadneSubject


Deliverable3.4 86


monuments

databasesor

inventories

• Scientific

datasets,such

asdatabasesof

radiocarbon

dates

• Artefact

databases,or

image

collections

• Burial

databases

BelowarelistedassociationshavingtheDCCDclassasdomain:

• dct:publisher: DANS (acdm:agentType). Although DANS is not the publisher of each

individualdataset,itisneverthelessthepublisherofthearchive,becauseitmadeitavailable

withinthecatalogue.

• dct:creator,dct:contributor,acdm:owner:DANS

• acdm:nativeSubject:Dendrochronology

• acdm:derivedSubject:AAThttp://vocab.getty.edu/aat/300054715

• dcat:distribution:

o title:DCCDArchive

o issued,modified:Sameastoplevelcollection

o dcat:accessURL:http://dendro.dans.knaw.nl

o oai-pmhServerURI:http://dendro.dans.knaw.nl/oai

o publisher:DANS

7.8.2 DCCDTRiDaSdatasets

The table below shows details concerning mapping at dataset level between DANS DCCD

Dendrochronology datamodel the ACDMmodel. In particular, the table reports all themappings

valid for each DCCD dataset within the TRiDaS (Tree Ring Data Standard) project and the

corresponding ACDM entities. Specific usage notes and detailed comments for each DCCD entity

mappingareprovidedintherelatedcolumns.



Deliverable3.4 87


dct:title title

dct:description NA TRiDaSproject

description

wasnotopen

access

dct:issued Dateofformal

issuance(e.g.,

publication)ofthe

resource.

stateChanged Thelastmodificationwaswhenitwasarchived/published?


whichtheresource

waschanged,updated

ormodified.

stateChanged Thelastmodificationwaswhenitwasarchived/published?

acdm:originalId Theoriginalidentifier

oftheresource

suppliedbythe

contentprovider

Sid

OurinternalidthatwealsouseintheURLofthelandingpage:theonethatstartswith“dccd:”

Therecordidentifierisalsoourrepositoryspecificidentifier.

AlsoaddtheTRiDaSprojectidentifier,butthationeisnon-prefered!

ACDMnowonlyallowsone!Puttheothersinkeywords!

NotethatthisisoriginalfromtheARIADNEviewpoint.

WheretoputtheTRiDaSidentifiers?

Maybeinthekeywords.

Couldaddthose,andmakethemnon-preferred!

dct:identifier TheARIADNE

identifierthatwillbe

computedfromthe

original.Thiscould

looklike:

www.ariadne.eu+

prefixoftheprovider

+IDoftheresource

dcat:keyword Textthatwecan’tmapotherwise:identifiersetc.etc

Maybeallinformationwecannot


Deliverable3.4 88


mapotherwise

dc:language Iftheresourceis

multilingual,more

thanonevaluemust

begivenforthis

property

language TRiDaSlanguage,mainlyforvocabularies

dcat:landingPage AWebpagethatcan

benavigatedtoina

Webbrowsertogain

accesstothedataset,

itsdistributions

and/oradditional

information.

Usesid=originalId

http://dendro.dans.knaw.nl/p

roject/{sid}

Humanreadable(html)page,usingthepersistentidentifierandresolver


Resourcetorelevant

contactinformation

whichisprovided

usingVCard[vcard-

rdf].

NA Notethatwewon’tputapersonhere.

acdm:accessPolicy URItostatementof


organization’s

website)

Sameasforwholecollection:

http://dendro.dans.knaw.nl/t

ermsofuse



thedataresource

Thepermission.defaultLevel Dataset

specific,

Notethatalso

restrictedto

registerred

usersofthe

DCCD


rightsheldinandover

thedataresource

Sameaspolicy:

http://dendro.dans.knaw.nl/t

ermsofuse

Notethatthe

rightsholders

shouldbeset

asowners

organisation

dct:audience Theprimary

audience(s)ofthe

resource

Sameasfrowholecollection:

Dendrochronologists,

Archaeologists,Historians

dct:temporal SeetemporalRegion periodName=

Wedon’thaveit;insteadof

‘Notavailable’usethetextual

Wehaveastroyears


Deliverable3.4 89


representationoftheperiod

inyears:

start–end,withBCandADif

needed

Notethatstrictlythisis

WRONGandweshouldbe

abletospecifythatwedon’t

haveit!

Betternotspecifysomething

wedon’thave,becauseit

dependsonthelocationas

wellasontheyeasrsandfor

dendrowehavedatafrom

lotsofdifferentregionsin

Europe

dct:spatial SeespatialRegion placeName

Wedon’thaveitbutinstead

of‘Notavailable’putherea

textualreprecsentationofthe

coordinates;lat,lng

Notethatstrictlythisis

WRONGandweshouldbe

abletospecifythatwedon’t

haveit!

WGS84

dct:accrualPeriodicity NA



ofitemsina

collection,numberof

recordsinadataset,

etc.)

NA Whatwould

‘records’bein

TRiDaS.

Maybe

numberof

series.

Butanywayit

isnoteasily

accessible!


Associatesany

archaeological

resourcewithoneor

morecategories

(types),drawnfrom

thefollowinglist:

• Fieldwork

archives

Scientificdatasets usedtobe

ariadneSubjec

t


Deliverable3.4 90


• Event/interve

ntion

resources,

suchasgrey

literature

reports

• Sitesand

monuments

databasesor

inventories

• Scientific

datasets,such

asdatabases

ofradiocarbon

dates

• Artefact

databases,or

image

collections

Burialdatabases

BelowarelistedassociationshavingtheDCCDclassasdomain:

• dct:isPartOf:dccd,theidentifierwithinACDMforDANStoplevelcollection

• acdm:publisher:DANS

• acdm:owner:ownerOrganizationId

• acdm:nativeSubject:Dendrochronology


• dcat:distribution:RESTfullTRiDaSfiledownloadURL(non-public)

o title:DCCDArchive

o issued,modified:sameastoplevelcollection

o dcat:accessURL:theURLwiththeSIDinit

o publisher:DANS

• acdm:hasItemMetadataStructure: TRiDaS metadata format: http://tridas.org/1.2.2/tridas-

1.2.2.xsd

• acdm:hasMetadataRecord:TRiDaSdownloadURL(thesamefordataandmetadata)


Deliverable3.4 91

7.8.3 DCCDtemporalentities

Temporalintervalsandnamedperiods(i.e.acdm:temporalRegionsubnodes)forDCCDcollectionand

datasets,withtherelatedusagenotesandcomments,areprovidedinthetablebelow.

Attribute UsageNotes DCCD Comments

:periodName Notavailable

:from timeRange.firstYear Converttoxs:date

:until imeRange.lastYear Converttoxs:date

7.8.4 DCCDspatialentities

Spatialregioninformation(i.e.acdm:spatialRegionsubnodes)forDCCDcollectionanddatasets,with

therelatedusagenotesandcomments,areprovidedinthetablebelow.

Attribute UsageNotes DCCD Comments

:placeName Anamedescribingthe

place

Notavailable

:coordinateSystem Thecoordinatesystem

usedtoencode

coordinates(e.g.EPSG

2763)

http://www.o

pengis.net/def

/crs/EPSG/0/4

326

WGS84

:lat TheLatitude Location.lat

:lon TheLongtitude Location.lng

:boundingBoxMinLat TheminLatofthe

boundingboxarea

NA

:boundingBoxMinLon TheminLonofthe

boundingboxarea

NA

:boundingBoxMaxLat ThemaxLatofthe

boundingboxarea

NA

:boundingBoxMaxLon ThemaxLonofthe

boundingboxarea

NA

:address Theaddressname NA

:numberInRoad Thenumberinroad NA

:postcode Postcode NA

:country Thecountryoftheplace Notavailable Wehavecoordinatesto

lookupingeonames?


Deliverable3.4 92

7.8.5 DCCDservicesandschemasintheregistry

Services

• ServiceForHumans:DANSonline repositorywhereuserscandeposit, searchanddownloaddatasetsandrelatedinformation

WebService

• DANSOAI-PMHendpoint,(viathe“‘hasAPI’=OAI-PMH”relationship).

StandAloneService

• Sourcecodefortherepository,canbedownloaded,buildandinstalledfromDANSwebsite.

TRiDaSmetadataschema

• title=TRiDaS

• description=TheTreeRingDataStandard

• dct:identifier=schema:35(automaticallygenerated)

• dct:language=en

• dct:landingPage=http://tridas.org/1.2.2/tridas-1.2.2.xsd

• foaf:homepage=http://tridas.org/

• :standardUsed=other

TRiDaSdataformat

• title=TRiDaS

• description=TheTreeRingDataStandard

• :characterSet=UTF-8

• :XSD=http://tridas.org/1.2.2/tridas-1.2.2.xsd

• :expressedIn=XML

7.8.6 EASYtoplevelcollection

ThefollowingtableshowsdetailsconcerningmappingbetweentheDANSarchaeologicalinformation

encoded using the EASY Metadata model (EMD, available at

https://easy.dans.knaw.nl/schemas/md/emd/2013/11/emd.xsd)and theACDMmodel for ingestion

intotheregistry.Inparticular,thetabledescribesthetoplevelcollectionvalidforallEASYdatasets.

Specific usage notes and detailed comments for each DCCD entity mapping are provided in the

relatedcolumns.

Attribute UsageNotes DANS Comment

dct:title DANS:DataArchivingand


Deliverable3.4 93

Attribute UsageNotes DANS CommentNetworkedServices

dct:description Thee-depotforDutch

archaeologyis

accommodatedatDANS,

thenationaldigital

researchdataarchivefor

theNetherlands.Awealth

ofdigitalarchaeological

excavationdatasuchas

maps,fielddrawings,

photographs,tablesand

publicationsisaccessible

viaEASY,DANS’online

archiving(deposit,

preservationandreuse)

service.DANSoperates

accordingtotheOAIS

modelfordigitalarchives

andholdstheDataSealof

Approval,the

internationallyrecognized

qualitymarkfortrusted

digitalrepositories.



resource.

2006 Thedateeasystarted


whichtheresourcewas

changed,updatedor

modified.

2015-11 Thedatethisinformationismodified,andnotaboutthecontentofthecollection

:originalId Theoriginalidentifierof

theresourcesupplied

bythecontentprovider

easy-collection:4 usethisincontentisPartOf


thatwillbecomputed


couldlooklike:

www.ariadne.eu+

prefixoftheprovider+

IDoftheresource

Generatedbytheregistry

dcat:keyword Archaeology,Excavation,Survey,Report



onevaluemustbegiven

nl,en Multipleentries,forthemainlanguagesofourdatasets


Deliverable3.4 94

Attribute UsageNotes DANS Commentforthisproperty


navigatedtoinaWeb

browsertogainaccess

tothedataset,its

distributionsand/or


http://easy.dans.knaw.nl Nohttpsneeded.

Notethatitwouldbeniceifwecouldrestricttoarchaeologywiththeurl.


Resourcetorelevant

contactinformation


VCard[vcard-rdf].

DataArchivingandNetworkedServices(DANS)

POBox93067|2509ABDenHaagTheNetherlands

E-mail:

[email protected]

Usecontactinfofrom

website.

vcard?

:accessPolicy URItostatementof



http://dans.knaw.nl/en/ab

out/organisation-and-

policy/legal-information



thedataresource

Metadata(thecontentof

allfieldsunderthe

"Description"tabinevery

datasetinEASY,theonline

archivingsystemofDANS)

isfreeforuseandopen

access.Howeverthedata

itselfhasconditionsforuse

andlicenseagreements.

Theusershould,

particularlyupon

distributionordisclosure,

respectanycopyrights

and/ordatabaserightson

thedataset.Thisdoesnot

applytodatafiles

depositedundertheCC

ZeroWaiver.


rightsheldinandover

thedataresource

http://dans.knaw.nl/en/ab

out/organisation-and-



oftheresource

Archaeologists,

Researchers,Policymakers

andGeneralpublic

dct:temporal SeetemporalRegion SequenceofALLABRmain

Periods!

dct:spatial SeespatialRegion

Placename:World,Europe,

TheNetherlands.


Deliverable3.4 95


Boundingbox:Netherlands

boundingbox

Country:TheNetherlands

dct:accrualPeriodicity

NA



ofitemsinacollection,

numberofrecordsina

dataset,etc.)

ThousandsofReportsand

Excavationarchives

Approximatenumber;

atthetimeof

describingthis


Associatesany


withoneormore

categories(types),

drawnfromthe

followinglist:

• Fieldwork

archives

• Event/interventi

onresources,

suchasgrey

literature

reports

• Sitesand

monuments

databasesor

inventories

• Scientific

datasets,such

asdatabasesof

radiocarbon

dates

• Artefact

databases,or

image

collections

• Burialdatabases

=Fieldworkdatabases,Event/interventions

usedtobe

ariadneSubject

BelowarelistedassociationshavingtheEASYcollectionasdomain:

• dct:publisher,dct:contributor,dct:creator,acdm:owner,acdm:technicalResponsible:DANS

• acdm:nativeSubject:Archaeology



Deliverable3.4 96

• dcat:distribution(issued,modified):sameastoplevelcollection

• dcat:accessURL:https://easy.dans.knaw.nl

• oai-pmhServerURI:https://easy.dans.knaw.nl/oai

7.8.7 EASYarchaeologicaldatasets

The next table contains details concerning mapping at dataset level between the DANS EASY

archaeologicaldatamodelandtheACDMmodel.EASYdatasetsareheterogeneous“collections”of

files containing reports about archaeological excavations. Many correspond to

acdm:textualDocument andothers have a specific structure. The field acdm:textualDocuments are

detected by inspecting the emd:type/dc:type fields (with eas:scheme='DCMI' and text()='Text') to

identifyexcavationreports.Otherdatasetsnotmatchingthesecriteria(mostlyexcavationarchives)

havebeenmappedascollections.


dct:title emd:title/dc:title Alsowantsubtitleas

dcterms:alternative.

Meanwhilewecouldmapit

todct:description.

Appendingtothetitle(wita

colon)giveslongtitles.

dc:description emd:description/dc:descripti

on

Andalso

dcterms:abstractdcterms:ta

bleOfContents



resource.

emd:date/*:created UsedateCreated,because

thatitthepublicationdate!


whichtheresourcewas

changed,updatedor

modified.

emd:date/*:created

Note:was

emd:date/eas:dateSubmitte

d

Shouldbedatepublished,

butthatisdatecreated,see

above!

:originalId Theoriginalidentifierof

theresourcesuppliedby

thecontentprovider

emd:identifier/dc:identifier

Onlytheonewith

eas:scheme='DOI'or‘

DOI_OTHER_ACCESS’.Thisis

themostimportant,

persistent,andtherefore

preferredone.

Wealsohavealotofother

idslikeISSN.


Deliverable3.4 97


thatwillbecomputed


couldlooklike:

www.ariadne.eu+prefix

oftheprovider+IDof

theresource

dcat:keyword Textthatwecan’tmap

otherwise.

Subjects:

notintheVocabulary

=>Not@eas:scheme='ABR'

and

@eas:schemeId='archaeolog

y.dc.subject'

Spatial:

Withoutcoordinatethatwe

canmap=>

not(emd:coverage/eas:spati

al/eas:point/@eas:scheme='

RD

Identifiers:

Non-DOI=>

not(@eas:scheme='DOI'or

@eas:scheme='DOI_OTHER_

ACCESS')

dc:language Iftheresourceis


onevaluemustbegiven

forthisproperty

emd:language/dc:language


navigatedtoinaWeb

browsertogainaccess

tothedataset,its

distributionsand/or


UsethePID,seeoriginalId

andtheresolverURL

ShouldbeDOIresolver!!!!

AANPASSEN

Humanreadable(html)

page,usingthepersistent

identifierandresolver


Resourcetorelevant

contactinformation


VCard[vcard-rdf].

DataArchivingand

NetworkedServices(DANS)

POBox93067|2509AB

DenHaagTheNetherlands

E-mail:

[email protected]

SameasforDANStoplevel

collection


Deliverable3.4 98

:accessPolicy URItostatementof



Zelfdealsvoordehele

collective:

http://dans.knaw.nl/en/abo

ut/organisation-and-




thedataresource

emd:rights/dcterms:accessRi

ghts

Notethatthecodes(like

GROUP_ACCESS)are

translatedtoahuman

readabletext

Datasetspecific,maybea

URL,wouldbebetter?

dct:rights Informationaboutrights

heldinandoverthe

dataresource

Sameasforthewhole

collection.

Notethatitwas:

emd:rights/dc:rights

Notethattherightsholders

arepresentedasowners


oftheresourceArchaeologists

dct:temporal SeetemporalRegion emd:coverage/dcterms:tem

poral

WithABR,maptoyearsand

periodname

Maptofrom-toyears,as

specifiedbyABR-Period,

Andifit’snotintheABR,putinkeywords

dct:spatial SeespatialRegion

emd:coverage/eas:spatial

mapeas:pointandeas:box

tocoordinatesinWGS84

Mapaddressnamesetc.in

emd:coverage/dcterms:spatialtokeywords!

dct:accrualPeriodicity

NA


resource(i.e.,numberof

itemsinacollection,

numberofrecordsina

dataset,etc.)

NA Maybenumberoffilesisin

theEMD(internally),but

notexposedviaOAI.

Butanywayitisnoteasily

accessible!


Associatesany


withoneormore

categories(types),

drawnfromthe

emd:type/dc:typeif

eas:scheme='DCMI'and

text()='Text'then

‘Event/interventions’

otherwise‘Fieldwork


Deliverable3.4 99

BelowarelistedassociationshavingtheEASYdatasetsasdomain:

• acdm:publisher:DANS

• acdm:contributor:emd:contributor/dc:contributor

• acdm:creator:emd:creator/dc:creatorandemd:creator/eas:creator

• acdm:owner:emd:rights/dcterms:rightsHolder

• acdm:nativeSubject:emd:subject/dc:subjectwitheas:scheme='ABR'and

eas:schemeId='archaeology.dc.subject'


• dcat:distribution:

o title:DANSEasyArchive

o dcat:accessURL:theURLwiththespecificDOI

o publisher:DANS

• acdm:hasItemMetadataStructure:http://easy.dans.knaw.nl/schemas/md/emd/2012/11/emd.xsd

• acdm:hasMetadataRecord:https://easy.dans.knaw.nl/ui/?wicket:interface=:3:tabs:panel:downloadPanel:download_xml

::IResourceListener::

7.8.8 EASYtemporalentities

In the tablebelow,EASY temporalentitiesare represented.An instanceof this class is a temporal

regionof oneof two forms: a temporal interval (e.g., from155BC to243AD)or anamedperiod

(e.g.,Neolithic).Intheformercase,theextremesoftheintervalaregivenasvaluesofthe:fromand

:toattributes.Inthelattercase,thenamedperiodisgivenasvalueofthe:periodNameattribute.

• InthecasewhereBCdateshavetobesupplied,aminus(-)signcouldbeusedas

indicatedintheexpandedyearrepresentationofISO8601

(http://www.iso.org/iso/catalogue_detail?csnumber=40874).

followinglist:



resources,suchas

greyliterature

reports

• Sitesand

monuments

databasesor

inventories

• Scientificdatasets,

suchasdatabasesof

radiocarbondates

• Artefactdatabases,

orimagecollections

• Burialdatabases

databases’(mostlikely

Dataset)


Deliverable3.4 100

• Inthecasewherereducedprecisionmustbeapplied(e.g.wherenodayinformationis

available)therespectivepartcouldbeomitted(accordingtoISO8601reducedprecision

guidelines).

Attribute DANS Comments

:periodNameskos:Concept

withtheaboutattributereferringto

theRCEURIandtheprefLabelsldo

fromtheABR+

Maptofrom-toyears,asspecifiedbyABR-

Period,

Andifit’snotintheABR,justcopythestring?

:fromUseABR Convertyearstoxs:date

:untilUseABR Convertyearstoxs:date

7.8.9 EASYspatialentities

ThenexttableshowsEASYSpatialentities.Aninstanceofthisclassisaspatialregionofoneoffour

forms: a region identified by latitude and longitude expressed via the :lat and :lon attributes,

respectively; a bounding box identified by four vertices (expressed via the :boundingBoxMinLat,

:boundingBoxMinLon, :boundingBoxMaxLat and :boundingBoxMaxLon attributes); a postal address

(expressed via the :address, :numberInRoad, :postcode and :country attributes); a named place

(expressedvia the :placeLabelattribute).Mostof theoriginal informationwas is inRD formatand

convertedtoWGS84.

Attribute UsageNotes DANS Comments

:placeName AnamedescribingtheplaceConcatenateall

valuesof

emd:coverage/

dcterms:spatial

:coordinateSystem Thecoordinatesystemusedto

encodecoordinates(e.g.EPSG

2763)

WGS84

:lat TheLatitude

:lon TheLongtitude

:boundingBoxMinLat TheminLatoftheboundingbox

area

:boundingBoxMinLon TheminLonoftheboundingbox

area

:boundingBoxMaxLat ThemaxLatoftheboundingbox


Deliverable3.4 101

Attribute UsageNotes DANS Comments

area

:boundingBoxMaxLon ThemaxLonoftheboundingbox

area

:address Theaddressname

:numberInRoad Thenumberinroad

:postcode Postcode

:country ThecountryoftheplaceDefaultsto‘The

Netherlands’

ThisisNOTalways

correct!

7.8.10 EASYservicesandschemas

Services:

• ServiceForHumans:ThisisDANSonlinerepositorywheredeposit,searchanddownloadcanbeperformed

• WebService:‘hasAPI’=OAI-PMH

MetadataSchema

• title:EMD

• description:easymetadata

• dct:identifier:schema:36(automaticallygenerated)

• dct:language:en

• dct:landingPage:https://easy.dans.knaw.nl/schemas/md/emd/2013/11/emd.xsd

http://easy.dans.knaw.nl/easy/easymetadata/https://easy.dans.knaw.nl/schemas/index.xml

• :standardUsed:DublinCore

Vocabulary

• ArcheoComplexTypes

• UploadedSKOS:ArcheoComplexTypes.xml

• dct:identifier:voc:35(automaticallygenerated)

• status:draft

• dct:language:nl

• URL:https://easy.dans.knaw.nl/schemas/vocab/2012/10/abr-type.xsd

Vocabulary


Deliverable3.4 102

• ArcheoPeriods

• status:draft

• dct:language:nl

• UploadedSKOS:ArcheoPeriods.xml

Distribution(Service)

• DANSWebPortal

• Title=DANSWebPortal

• dct:description=EASYonlinearchivingsystem

• dcat:accessURL=https://easy.dans.knaw.nl/

EASYOAI-PMH(Service)

• Title=EASYOAI-PMH

• dct:description=EASYOAI-PMHEndpoint

• dcat:accessURL=http://easy.dans.knaw.nl/oai/

7.9 Discoverydatasets

DatasetscontributedtotheARIADNEregistrybytheDiscoveryProgrammewere ingestedusingMS

Excel files,ormanually through the registryweb tool. Themajorityof thedatasetswereoriginally

recordedusingtheQualifiedDublinCoremetadataschema.Forthoseinotherformats(e.g.INSPIRE)

theDiscoveryProgrammeundertookmapping to theACDM.Datasetswerepreparedmanually for

each collection using the Excel template available via the ARIADNE registry. In most cases some

additionalmetadatahadtobesuppliedforthespecificdemandsoftheACDMmodel.

7.9.1 DataResource–Collection

The Leo Swan Aerial Photographic Archive, the Discovery Programme Image Collection and the

Hanson/OlteanArchaeologicalAerialArchiveofRomaniaarecollectionsavailableonlinewhichuse

theOmeka contentmanagement andwebpublishing system.Although the systemallows anOAI-

PMHharvestforindividualrecords,thesedatasetswereconsideredmoresuitabletobeingestedat

collection level to the ARIADNE registry. The collections conformed to the Qualified Dublin Core

metadataschemaandwereingestedusingthewebregistrytoolmanuallybeforebeingharvestedto

theMORe aggregation tool. The table below describes Dublin Coremapping of a DataResource –

Collection toACDM.SinceDCAT (onwhichACDM isbased)borrowsextensively fromDublinCore,

mappingwasrelativelystraightforward.

DublinCore ACDM

dc:title dct:title

dc:description dct:description

dcterms:issued dct:issued


Deliverable3.4 103

DublinCore ACDM

dcterms:modified dct:modified

dc:identifier acdm:originalid

[DefinedbyDiscoveryatingestiontime] dct:identifier

dc:subject dcat:keyword

dc:language dct:language

dcterms:temporal dct:temporal

dcterms:spatial dct:spatial

dcterms:accrualPeriodicity dct:accrualPeriodicity

[DefinedbyDiscoveryatingestiontime] dct:landingPage

dc:publisher dct:publisher

dc:creator dct:creator

dcterms:rightsHolder acdm:owner

dcterms:rightsHolder acdm:legalResponsible

dcterms:rightsHolderordc:creator acdm:scientificResponsible

dcterms:rightsHolderordc:creator acdm:technicalResponsible

[DefinedbyDiscoveryatingestiontime] acdm:archaeologicalResourceType

dc:subject dct:subject

[DefinedbyDiscoveryatingestiontime] acdm:accessPolicy

dcterms:accessRights dct:accessRights

dc:rights dct:rights

dcterms:extent dct:extent

dcterms:audience dct:audience

[DefinedbyDiscoveryatingestiontime] acdm:hasItemMetadataStructure

[DefinedbyDiscoveryatingestiontime] acdm:hasMetadataRecord

dcterms:isPartOf dct:isPartOf

[DefinedbyDiscoveryatingestiontime] acdm:Distribution

7.9.2 ArchaeologicalSurveyofIreland(ASI)

This datasetwas received as a CSV file from theNationalMonuments Service, and contained the

datasetoftheArchaeologicalSurveyof Ireland.ThedatasetconformstotheEUINSPIREdirective.2

Assuchthedatasetwas largelyconcernedwithspatialdata,whichwasthensupplementedbythe

DiscoveryProgrammeforconformanceto theACDMspecification.TheCSV filehadbeenexported

2FortheIrishINSPIREgeoportalseehttps://www.geoportal.ie/geoportal/catalog/main/home.page.


Deliverable3.4 104

fromtheArcGISmappingsoftwareandcontainedthefollowingfields,whichcouldbemappedtothe

ACDM.

FEATURECLASS[ArcGIS] ACDM

ENTITY_ID acdm:originalid

NAT_GRID_E (IrishNationalGrid-eastings) dct:spatial

NAT_GRID_N (IrishNationalGrid-northings) dct:spatial

ITM_E (IrishTransverseMercator-eastings) dct:spatial

ITM_N(IrishTransverseMercator-northings) dct:spatial

CLASSDESC acdm:nativeSubject

SMRS (Sitesandmonumentsrecordnumber) acdm:originalid

TLAND_NAMES(Townlandname) dct:spatial<acdm:placeName>

Lat dct:spatial<acdm:lat>

Lon dct:spatial<acdm:lon>

Link dct:landingPage

For thepurposesofmapping to theACDM, itwasdecided toonlyuseacdm:placeName,acdm:latandacdm:lon for thedct:spatial valuesas theother spatial referenceswouldnotbeconfigurable.Oncethecollection-levelrecordwasingestedintothewebtool,childrecordswereingestedusingan

MS Excel file.Most of the additional fieldswere repeatable, although the title fieldneeded to be

concatenatedfromotherfieldsbeforeingestioninordertomakeitclearertotheenduser.

7.9.3 3DIconsProject-CARARE

The3D IconsProjectmetadatawasstructuredusing theCARAREmetadataschema.Thiscollection

was ingested into the registry using the web tool, as no collection-level record for the dataset

existed.Whenthiscollectionismadeavailableintheregistryasadataset,thecollectionwilllikelybe

ingestedusinganXMLfile.TheDiscoveryProgrammeiscurrentlydevelopingaworkflowformapping

theCARARErecordstotheACDM,usingaservicesuchastheMINTmappingandaggregationtool.

7.9.4 WODAN,MAPPINGDEATHandTIIExcavationReports

The Discovery Programme is currently configuring two further databases, WODAN and Mapping

Death, for ingest into the ARIADNE registry. In addition to this, the Discovery Programme is

collaborating with Transport Infrastructure Ireland [TII] to include a collection of grey literature

(mainlyexcavationreports)intheARIADNEregistry.MetadatahasbeenrecordedinQualifiedDublin

CoreandisavailableinbothMSExcelandXMLfiles.

7.9.5 IrishMonumentsvocabularyAATmapping

Themostdetailed classification systemavailable for IrishMonument types is the class list

developedby theNationalMonumentsService [NMS].This isa flat/simplehierarchical list

which was used in the classification of sites and monuments that formed part of the

ArchaeologicalSurveyofIreland[ASI],whichwasestablishedtocompileaninventoryofthe


Deliverable3.4 105

knownarchaeologicalmonumentsintheState.Theinformationisstoredinadatabaseanda

seriesofpaperfilesthatcollectivelyformtheASISitesandMonumentsRecord(SMR).Each

site/monument has a unique SMRnumberwhich greatly facilitates the creationof Linked

Dataandeachsite/monumentisgivenaclassificationbasedontheNMSclasslist.Theclass

list consists of a site ormonument classification (e.g. armorial plaque)with an associated

scopenotewhichdetailsthesite/monumentfeatures(Forexample:‘Astonetabletorslab

bearingacoatofarms, sometimesaccompaniedbyadateand/or inscription.This term is

notusedformemorialsofthedeadfoundinchurches, forwhichsee‘Wallmonument’.or

Thesedate from the latemedievalorpost-medievalperiods (c.1400-1600AD)onwards.’)

Thedevelopmentof the listwasanorganicandevolvingprocessand the list is subject to

reviewwithamendmentsmadeonanon-goingbasis.

ThiswasundertakenbytheDiscoveryProgrammeinordertomapthesubjectclassifications

intheNMSlisttotheGettyAAT.Thiswasdoneforeachtermbycomparingthescopenotes

of theNMSclass list to thenotes fieldof theAATOnline. This automatically introducesa

levelof subjectivitywhichwascounteredbyusinganappropriateSKOSmappingproperty

whenlinkingtothetargetvocabulary[AAT].Wheretherewasanyambiguityabouttheterm,

broadermappingpropertieswerealwaysused.

IncertaincaseswheremappingsweredifficultandcouldbemorecloselyrelatedtotheFISH

ThesaurusofMonumentTypes,theVocabularyMatchingTooldevelopedbyUSWwasfirst

used to identifymatching terms,whichwas in turnmapped to the AAT (i.e. a two stage

mappingprocess).

ThenatureoftheclassificationlistoftheNMSpresentedoccasionaldifficulties:

• Some classifications contained highly detailed elements e.g. object terms were

refined at term level by their present location [Cist(present location)] or were

developed inorder to classify idiosyncratic sites [turf stand;watchman’shut-burial

ground]

• Therewas greater congruence between the FISHMonument Type vocabulary and

theIrishsubjecttermsenablinggreaterpossibilitiestofindanexactorclosematch.

InsomecasestermshadclearlybeenbasedontheFISHvocabulary.Thiswastobe

expected due to geographical/historical contiguity. For example bullaun stone, for

whichthereareover1000currentlydocumentedintheASI,relatesmorecloselytoa

‘cup-markedstone’inFISHbutcanonlybesatisfactorilymappedusingtwo(ormore)

termsintheGettyAAT[ceremonialobjects;mortaria].

• SometermsarenotclearlydefinedintheNMSclasslist[e.g.settlementplatform:‘A

raisedarea,oftensurroundedbywaterloggedorboggyland,whichhasevidenceof

formerhumanhabitation]whichmademapping,evenatahighlevel,difficult.

• Subjectdefinitionsoftenincludedbroadperiodclassificationswithinthescopenote,

thereforeitwasdecidednottotakethisintoconsiderationasperiodtermscouldbe

coveredbytheIrishPeriodsVocabulary.Occasionallytermscontainedperiodterms

intheirtermname(e.g.House-16thcentury;House-16th/17thcentury)aswellasa

refiningsubjectelement(e.g.House-fortifiedhouse)Thisnecessitatedboththeuse

oftheIrishPeriodsVocabularyand/oradditionaltermsfromtheAAT.

• Some classifications were subdivided (but not hierarchically) into more specific

elements(e.g.Ringfort-cashel;Ringfort-rath;Ringfort-unclassified).Thegranularityof


Deliverable3.4 106

thetermswasconservedbyusingtheappropriatemappingproperty,insomecases

bymappingtermstomultipletermsinthetargetvocabulary.

Themapping process attempted to balance the pressing need to implement Linked Data

with thereality that theavailablevocabularywas rich indetailbut lackedastructure that

waseasilyreconciledwithstandardconceptsofcontrolledvocabulariesandindexing. This

was largely achievedbymultiplemappings to the target vocabulary aswell asutilising an

intermediate vocabulary which more closely reflected the particular nuances of Irish

Monumenttypes.

7.9.6 PeriodOmappings

ThewithinIrelandthereisnoformallyprescribedvocabularyfortimeperiod,thereforethe

Discovery Programme utilised an extended version of the period classification scheme

utilised internallyby thenationalmonuments services (NMS)of Ireland (NMS timeperiod

list ends at 200BP so an additional modern period was added). All time periods have

relativelygenericnamese.g.EarlyBronzeAgeandhavedatingrangingapplicabletoIreland.

The discovery Programmes time period vocabulary was mapped to PeriodO’s English-

languagevocabularywithstart_labelsandend_labelsforeachrecordcreatedandallspatial

coveragesettoIreland.

7.10 INRAP

DOLIA[http://dolia.inrap.fr/inrapgestdoc/jsp/index.jsp]isanonlinesystemusedbyINRAP

to manage and disseminate scientific documentation. The system, based on the Decalog

contentmanagementsystem,Flora(v.3.1.0),wassetupforINRAPbetween2008and2009.

DOLIAemploys international librarystandards,specificallytheUNIMARCformat.UNIMARC

isaEuropeanversionofMARCstandard,aformatforthedescriptionofitemscataloguedby

libraries, suchasbooksor grey literature. Each field in aMARC recordprovidesparticular

informationabouttheitemtherecordisdescribing,suchastheauthor,title,publisher,date,

language, media type, etc. This is both a description of a bibliographical object and its

contents via a summary of the work and a chronological, thematic and geographical

indexation.Itisametadatatransmissionstandard,easilytransferableandeasilyencodable,

forexample,inDublinCoreformat.

DOLIA’s data conforms to the ISO2709 standard and canbe also easily exchanged via the

Z3950protocol.

The mapping with ACDM was easily done, and an export framework was developed by

INRAP to provide content to the ARIADNE registry. The following table documents the

variousmappingsbetweenUNIMARCandACDMperformedby INRAP tomake its content

availablewithintheARIADNEinfrastructure.

UNIMARCField Description ACDMField Type

UNIMARC200[$a+$e] dcterm:title 1

"Dolia" dcterms:isPartOf

UNIMARC330[$a] dcterms:description 0-1


Deliverable3.4 107

UNIMARCField Description ACDMField Type

UNIMARC210[$d] dcterms:issued 1

UNIMARC5(AAAAMMJJhhminminss) dcterms:modified 1

NULL dcterms:accrualPeriodicity

UNIMARC991[$a] acdm:originalId

UNIMARC610[$a] dcat:keyword 0-∞

UNIMARC101[$a] dcterms:language

UNIMARC634[$5] acdm:temporal 1-∞

UNIMARC102[$a] acdm:country

MappingPeriodO acdm:from

MappingPeriodO acdm:to

GeocodingIGNLonUNIMARC901[$a+

$d]

acdm:spatialLon 1-∞

GeocodingIGNLatUNIMARC901[$a+$d] acdm:spatialLat

URI(http://dolia.inrap.fr/flora/ark:+

UNIMARC991[$a])

dcat:landingPage

"Institutnationalderecherches

archéologiquespréventives"

dcterms:publisher 1

UNIMARC210[$c] dcterms:contributor

UNIMARC700[$a]+701[$a]+702[$a] dcterms:creator 1-∞

UNIMARC801[$b] acdm:owner

UNIMARC801[$b] acdm:legalResponsible

UNIMARC700[$a] acdm:scientificResponsible

UNIMARC700[$a] acdm:technicalResponsible

"Event/interventionresources" acdm:archaeologicalResourceType

UNIMARC606[$5] acdm:nativeSubject 1-∞

http://www.inrap.fr/Dolia/Annexes/p-

17075-Conditions-d-utilisation.htm

acdm:accessPolicy

"Freeaccessexceptforattached

documents"

acdm:accessRights

"Scientific" dcterms:audience


Deliverable3.4 108

7.10.1 Terminologicalresources

The terminological resources mapped to the AAT by Inrap are the PACTOLS thesauri

(http://frantiq.mom.fr/thesaurus-pactols) produced by the archaeological network FRANTIQ

(Fédérationetressourcessurl’Antiquité)[http://frantiq.mom.fr/]supportedbytheCentreNational

delaRechercheScientifique(CNRS).InrapusedfourofthesixPACTOLSthesauriforachronological,

geographicalandthematicindexing.

The reports, stored in PDF format, are indexed with native subjects inherited by the PACTOLS

“Sujets/Subjects”thesaurus.TheDoliacataloguecurrentlyuses1573termsinthesubjectmetadata

on5149presentinthePACTOLSthesaurus.Sothemappingconcernsonlytheindexedtermsofthe

Dolia catalogue. The alignment has been done between those terms and the AAT

thesaurushttp://vocab.getty.edu/byusingasourcetermfromPACTOLS,asourceURI,atargetterm

fromAATandatargetURI,specifyingtheSKOSmatch.Mappingexamplesfollow:

PACTOLSterm:Archéologie

PACTOLSURL:http://ark.frantiq.fr/ark:/26678/pcrty05M9SVnLu

SKOSmatch:exactMatch

AATterm:archaeology

AATURL:http://vocab.getty.edu/aat/300054328

PACTOLSterm:amphoregauloise

PACTOLSURL:http://ark.frantiq.fr/ark:/26678/pcrtiUhJYvi7PG

SKOSmatch:broadMatch

AATterm:amphorae(storagevessels)

AATURL:http://vocab.getty.edu/aat/300148696

7.11 MiBACT-ICCUinformation

This sections documents the activity carried out by ICCU-MiBACT, in particular through the

CulturaItaliaPortal,theofficialportalfortheItalianculturalheritageworlddevelopedbytheItalian

Ministry of Cultural Heritage. CulturaItalia was developed to promote interoperability of digital

contentbyensuringtheintegration,independenceandavailabilityofculturalresources.Accessibility

of information is realised through its architecturebasedon international standards suchasDublin

Core (DCMI) for interoperabilityofmetadata from the various sectors,OAI-PMHandHTTP for the

distributionofinformationfromtheintegrateddatabases,XMLfordatarepresentation,RDFforthe

publication of Linked Open data. Thanks to these standards CulturaItalia manages and organises

heterogeneousinformationfromdifferentcataloguingsystemsandmetadataresources,andmakes

themaccessibleviaindexes,thematicandgeographicqueryfeatures.

7.11.1 PICOmappings

For compatibility with the choices made in the international arena, and in accordance with the

guidelines of the CulturaItalia project for the realisation of the CulturaItalia Portal, metadata

integrationofexternaldatasources isdonebyamappingtoasingleschema:thePICOApplication

Profile. This schema isexpressedaccording to theQualifiedDublinCore standard,whichhasbeen

furtherextendedtodefinetheApplicationProfiledesignedforthePortal.QualifiedDublinCoreisa


Deliverable3.4 109

derivedversionofSimpleDublinCore,encodedbytheDublinCoreMetadataInitiative.Itincludesa

setofbasicelementswithwhichyoucandescribeanykindofresource.Aresourceis“anythingthat

hasidentity.”Itsbasicelementsare:Title,Creator,Subject,Description,Publisher,Contributor,Date,

Type, Format, Identifier, Source, Language, Relation, Coverage, Rights, to which the other three

elementshavebeenaddedrecently:Audience,ProvenanceandRightsHolder.QualifiedDublinCore,

in addition to 18 basic elements, also includes 33-refinement elements and a series of encoding

schemas,(ontologiesorcontrolledvocabularies)forinterpretingthevalueofeachitemonformalor

grammatical notations. The PICO Application Profile and schema are accessible through at the

followinglinks:

PicoApplicationProfile:

http://www.culturaitalia.it/opencms/export/sites/culturaitalia/attachments/documenti/picoap/pico

ap1.0.xml

PICOXSDSchema:

http://www.culturaitalia.it/opencms/export/sites/culturaitalia/attachments/schemas/1.0/pico.xsd

In general, it was always possible to find one-to-one direct correspondences between PICO and

ACDMentities,withsomenotableexceptions:

InthePICO,thedc:subjectelementcanspecify:

• A subject or scene represented on or by a given artefact (according, for instance, to

traditionaliconographicdefinitions,suchas:“BirthofAphrodite”)

• The description of the items in question, i.e. the analytical and literal description of the

subject of the item under consideration through the use of standardised iconographic

categoriesand/ordecorativeapparatus,forexample:“CHARACTERS:Aphrodite”)

• The topic of the resource in associationwith specific concepts of the PICO Thesaurus, for

example: http://culturaitalia.it/pico/thesaurus/4.1#reperti_archeologici (this is one of the

mandatoryrequirementsforthepublicationofdataonthePortal)

Forthedc:titleelementtheruleforthecreationofvaluesinthetagisasfollows(orderedby

priority):

• Name / dedication, i.e. the historic or traditional name of the artifact, for example:

“AmphoraofBaratti”)

• Titlegivenbytheauthorortraditionalnameofthesubject,forexample:“ApolloBelvedere”

• Definition, i.e., word or phrase that identifies the artefact based on the functional and

morphologicalconnotations,forexample:“urn/cineraria,cover”

Finally it is important to specify that for some elements it was not possible to define one-to-one

mappings,inparticularforACDMelementsassociatedwithtwoelementswithinthePICOProfile,for

instancethedcat:landingPageandacdm:temporalentities,obtainedfromPICOasfollows:

ACDMdcat:landingPage

dc:relation[xsi:type=”pico:Anchor”

URL=@@resourcelandingPage

Arelatedresource.Recommendedbestpracticeisto

identify the related resource by means of a string

conformingtoaformalidentificationsystem.


Deliverable3.4 110

dcterms:isReferencedBy

[xsi:type=”pico:Anchor”]

The described resource is referenced, cited, or

otherwise pointed to by the referenced resource.

Must be used to point to the web page where the

dataproviderpublishestheharvestedresource,using

theencodingscheme‘pico:Anchor’.

ACDMacdm:temporal

dcterms:temporalTemporalcharacteristicsoftheintellectualcontentof

theresource.

dcterms:created Dateofcreationoftheresource.

For PICO elements associated with two elements within the ACDM model, for instance

dc:contributor,dc:formatanddc:coverage,builtasshownbelow:

PICOdc:contributor

An entity responsible formaking contributions to the

resource. Examplesof aContributor includeaperson,

anorganization, or a service. Typically, thenameof a

Contributorshouldbeusedtoindicatetheentity.

dcterms:contributor


PICOdc:format

Thefileformat,physicalmedium,ordimensionsofthe

resource. Examples of dimensions include size and

duration. Recommended best practice is to use a

controlledvocabularysuchasthelistofInternetMedia

Types-MIME.

dcterms:format

expressedIn

PICOdc:coverage

The spatial or temporal topic of the resource, the

spatialapplicabilityof the resource,or the jurisdiction

underwhichtheresourceisrelevant.Spatialtopicmay

be a named place or a location specified by its

geographic coordinates. Temporal period may be a

namedperiod,date,ordate range.A jurisdictionmay

beanamedadministrativeentityorageographicplace

to which the resource applies. Recommended best

practice is to use a controlled vocabulary such as the

Thesaurus of Geographic Names (TGN). Where

appropriate,namedplacesortimeperiodscanbeused

in preference to numeric identifiers such as sets of

coordinatesordateranges.

placeName

address

Table below contains detailed information concerning the PICO Application Profile mapping to

ACDM.


Deliverable3.4 111


dc:title Anamegiventotheresource.

Typically,aTitlewillbeanameby

whichtheresourceisformally

known.Itisrecommendedto

specifythelanguage.

dcterm:title

dcterms:isPartOf Thedescribedresourceisa

physicalorlogicalpartofthe

referencedresource.

dcterms:isPartOf

dc:description Anaccountoftheresource.

Descriptionmayincludebutisnot

limitedto:anabstract,atableof

contents,agraphical

representation,orafree-text

accountoftheresource.

dcterms:description

dcterms:issued Dateofformalissuance(e.g.:

publication)oftheresource.

dcterms:issued

dcterms:modified Dateonwhichtheresourcewas

changed.

dcterms:modified

dcterms:accrualPer

iodicity

Thefrequencywithwhichitems

areaddedtoacollection.


dc:identifier Anunambiguousreferencetothe

resourcewithinagivencontext.

Recommendedbestpracticeisto

identifytheresourcebymeansofa

stringconformingtoaformal

identificationsystem.

acdm:originalId

dc:language Alanguageoftheresource.


useacontrolledvocabularysuchas

RFC3066.

dcterms:language

dcterms:temporal Temporalcharacteristicsofthe

intellectualcontentofthe

resource.

acdm:temporal dcterms:tempor

al?

Theelement

acdm:temporal

mapwithtwo

elementsof

PICO

dcterms:created Dateofcreationoftheresource.

“Italy” acdm:country

dcterms:spatial Spatialcharacteristicsofthe

intellectualcontentofthe

resource.

dcterms:spatial


Deliverable3.4 112


dc:relation[xsi:type="pico:Anc

hor"

URL=@@resourcel

andingPage

Arelatedresource.Recommended

bestpracticeistoidentifythe

relatedresourcebymeansofa



dcat:landingPage Theelement

dcat:landingPag

emapwithtwo

elementsof

PICO

dcterms:isReferencedBy[xsi:type="pico:Anc

hor"]

Thedescribedresourceis

referenced,cited,orotherwise

pointedtobythereferenced

resource.Mustbeusedtopointto

thewebpagewherethedata

providerpublishestheharvested

resource,usingtheencoding

scheme'pico:Anchor'.

dc:publisher Anentityresponsibleformaking

theresourceavailable.Examplesof

aPublisherincludeaperson,an

organization,oraservice.Typically,

thenameofaPublishershouldbe

usedtoindicatetheentity.

dcterms:publisher

dc:contributor Anentityresponsibleformaking

contributionstotheresource.

ExamplesofaContributorincludea

person,anorganization,ora

service.Typically,thenameofa

Contributorshouldbeusedto

indicatetheentity.

dcterms:contributor ThePICO

element

dc:contributor

mapwithtwo

elementsof

ACDMacdm:scientificResponsible

dc:creator Anentityprimarilyresponsiblefor

makingtheresource.Examplesofa

Creatorincludeaperson,an

organization,oraservice.Typically,

thenameofaCreatorshouldbe

usedtoindicatetheentity.

dcterms:creator

dcterms:rightsHolder

Apersonororganisationowningor

managingrightsovertheresource.


usetheURIornameoftheRights

Holdertoindicatetheentity.

acdm:owner


Deliverable3.4 113


pico:responsible Anydeadoralivephysicalperson,

anycorporatebodyorinstitution,

responsibleforthemanagement,

organisation,administration,etc.

oftheresourceorofapartofit.In

somecasesitcoincideswiththe

contactperson,whosecontactsare

indicatedforpeoplewhoare

lookingforinformationaboutthe

resource.e.g.theperson

responsibleforaprojectorofone

ofitsworkpackages,amuseum

director,thedirectorofa

universityoradepartment,etc.


pico:isManagedBy Thedescribedresourceismanaged

withdifferentresponsibilities

(scientific,administrative,

technical,etc.)bythereferenced

resource.



dc:subject[xsi:type="pico:The

saurus"]

Thetopicoftheresource.Typically,

thetopicwillberepresentedusing

keywords,keyphrases,or

classificationcodes.Recommended

bestpracticeistouseacontrolled

vocabulary.Todescribethespatial

ortemporaltopicoftheresource,

usetheCoverageelement.

acdm:nativeSubject N.B.:Pico

Thesaurusis

organizedby

categoriesof

objectsand

doesn'tcontain

theindividual

entriesofthe

"object

definition"

(specific

vocabularies).

Toenable

semanticsearch

inARIADNE

Portalhasbeen

necessaryto

modify

individualXML

filesbyinserting

indc:subjectto

thefollowing

additional

information,

Eg.:

acdm:nativeSub


Deliverable3.4 114


jectxmlns:acdm

=

"http://registry.

ariadne-

infrastructure.e

u/">

<skos:Concept

xmlns:skos=

"http://www.w

3.org/2004/02/s

kos/core#">

<skos:prefLabel

>lama</skos:pr

efLabel>

</skos:Concept

>

</acdm:nativeS

ubject>

Thevalue‘lama’

matchswiththe

mappingICCD-

RAThesaurus/

AAT.

dcterms:license Alegaldocumentgivingofficial

permissiontodosomethingwith

theresource.Recommendedbest

practiceistoidentifythelicense

usingaURI.Examplesofsuch

licensescanbefoundat

http://creativecommons.org/licens

es/.

acdm:accessPolicy

dcterms:accessRights

Informationaboutwhocanaccess

theresourceoranindicationofits

securitystatus.AccessRightsmay

includeinformationregarding

accessorrestrictionsbasedon

privacy,securityorother

regulations.

acdm:accessRights dcterms:accessR

ights?

dc:rights Informationaboutrightsheldin

andovertheresource.Typically,

rightsinformationincludesa

statementaboutvariousproperty

rightsassociatedwiththeresource,

includingintellectualproperty

dcterms:rights


Deliverable3.4 115


rights.

dct:extent Thesizeordurationofthe

resource.

dcterms:extent

dcterms:audience Aclassofentityforwhomthe

resourceisintendedoruseful.A

classofentitymaybedetermined

bythecreatororthepublisheror

byathirdparty.

dcterms:audience

dc:relation Arelatedresource.Recommended

bestpracticeistoidentifythe

relatedresourcebymeansofa



dcat:contactPoint

pico:distributor Anydeadoralivephysicalperson,

anycorporatebodyorinstitution,

responsibleforthedistributionof

aneditedorpublishedresource.

Theusageofthistermis

recommendedforresourcesas

musicrecordsandmovies.

dcat:distribution

dcterms:hasPart Thedescribedresourceincludes

thereferencedresourceeither

physicallyorlogically.

dcterms:hasParts

dc:format Thefileformat,physicalmedium,

ordimensionsoftheresource.

Examplesofdimensionsinclude

sizeandduration.Recommended


vocabularysuchasthelistof

InternetMediaTypes-MIME.

dcterms:format ThePICO

element

dc:formatmap

withtwo

elementsof

ACDMexpressedIn

dc:source Theresourcefromwhichthe

describedresourceisderived.The

describedresourcemaybederived

fromtherelatedresourceinwhole

orinpart.Recommendedbest

practiceistoidentifytherelated

resourcebymeansofastring

conformingtoaformal


dcterms:source

dc:coverage Thespatialortemporaltopicofthe placeName ThePICO


Deliverable3.4 116


resource,thespatialapplicabilityof

theresource,orthejurisdiction

underwhichtheresourceis

relevant.Spatialtopicmaybea

namedplaceoralocationspecified

byitsgeographiccoordinates.

Temporalperiodmaybeanamed

period,date,ordaterange.A

jurisdictionmaybeanamed

administrativeentityora

geographicplacetowhichthe

resourceapplies.Recommended


vocabularysuchastheThesaurus

ofGeographicNames(TGN).

Whereappropriate,namedplaces

ortimeperiodscanbeusedin

preferencetonumericidentifiers

suchassetsofcoordinatesordate

ranges.

address element

dc:coverage

mapwithtwo

elementsof

ACDM

pico:contact Informationaboutcontactsrelated

totheresource.Examplesof

Contactinclude:telephone

number,fax,address,e-mail

address,etc.Itcan’tbeusedfor

indicatingcontactsofpeoplewhich

contributetotheresource.

contactPerson

7.11.2 Terminologicalservices

ASKOSencodedversionoftheRA(ArchaeologicalArtefacts)modeloftheICCDCentralInstitutefor

Cataloguing and Documentation of the Italian Ministry of Culture, derived from an RA to AAT

mapping,havebeenreleasedasserviceandisnowavailableat:

http://vast-lab.org/thesaurus/ra/vocab/index.php

7.12 MiBACT–SITAR

This section presents the twomappings to ACDM carried out by SITAR (Archaeological Territorial

InformativeSystemofRome)startingfromtheir“InformationSource”and“ArchaeologicalPartition”

datasets. The “Information Source” (OI) is an archive of archaeological activities (mostly

archaeological excavations, surveys and other activities relatedwith archaeological investigations)

under the supervisionof SITAR. Thearchivealso containsadministrativeand scientific information

foreverysinglearchaeologicalexcavation,geophysical/geologicalsurvey,topographicalstudyandso

forth. “Archaeological Partition” (PA) datasets contains the scientific description of the

archaeologicalfindingseveniffragmentary,identifiedbychronologicalorfunctionalcriteria.OIand

PAdatasetshavesomeinternalrelationships,e.g.:eachOIrecordusuallyhasPartandformsoneor


Deliverable3.4 117

manyPArecords.BothdatasetshaveEstandNordcoordinatesencodedinEPSG:3004,longitudeand

latitudeinEPSG:4326.

ThefollowingtablereportsacomparativeanddetailedmappingofeachOIandPAfieldtoACDMand

thecriteriauponwhicheverymappingwasdefined.

ACDMEntities SITARInformationSourceClassSITARArchaeologicalPartition

Class

dct:title st_information_source.name concat(st_archaeo_part.objective_defin

ition||'pertinente/ia:'||st_archaeo_part.specific_definiti

on)

dct:description st_information_source.descripti

on

st_archaeo_part.description

dct:issued st_information_source.created_

at

st_archaeo_part.created_at

dct:modified st_information_source.updated

_at

st_archaeo_part.updated_at

originalId st_information_source.sitar_co

de

st_archaeo_part.id

dct:identifier assignedbyARIADNE assignedbyARIADNE

dct:language Italian Italian

dcat:landingPage http://webais.archeositarprojec

t.it/webgis/

http://webais.archeositarproject.

it/webgis/

dcat:contactPoint [email protected]

om

[email protected]

m

accessPolicy URItopolicywebpagetobe

defined

URItopolicywebpagetobe

defined

dct:accessRights Dataaccessandusewillbe

grantedinfullcompliancewith

MiBACTdata/opendatapolicies

andlicenses

Dataaccessandusewillbe

grantedinfullcompliancewith

MiBACTdata/opendatapolicies

andlicenses

dct:rights Theinstitutionownerofdatais

MiBACT-Special

Superintendencefor

ArchaeologicalHeritageof

Rome

Theinstitutionownerofdatais

MiBACT-Special

Superintendencefor

ArchaeologicalHeritageofRome

dct:audience archaeologists,geologists,

urbandevelopment

professionists,scholars,public

administrations,andinfuture

thewiderpublic.

archaeologists,geologists,urban

developmentprofessionists,

scholars,publicadministrations,

andinfuturethewiderpublic.

dct:temporal st_information_source.start_da st_phase.start_year


Deliverable3.4 118


Classte

st_information_source.end_dat

e

st_phase.end_year

dct:spatial est_epsg3004/nord_epsg3004

long_epsg4326/lat_epsg4326

est_epsg3004/nord_epsg3004

long_epsg4326/lat_epsg4326

dct:extent totalamount:801recordsof

InformationSource+5506

documentreferences

totalamount:2475recordsof

ArchaeologicalPartition+136

documentreferences

archaeologicalResourceType Fieldworkarchives;

Event/interventionresources,

suchasgreyliteraturereports;

Sitesandmonumentsdatabases

orinventories

Fieldworkarchives;

Event/interventionresources,

suchasgreyliteraturereports;

Sitesandmonumentsdatabases

orinventories

dct:isPartOf ArcheoSITARProject ArcheoSITARProject

dcat:distribution http://webais.archeositarprojec

t.it/webgis/


it/webgis/

dct:hasParts Referencetoanexternaltable

toestablishthe1:N

relationships

NO

native-subject Referencesfromtwoexternal

tables:IS_native-subjectAND

IS_native_subject_AAT_mappin

g

Referencesfromtwotables:

st_archaeo_part.objective_defini

tionAND

AP_native_subject_AAT_mappin

g

dct:publisher MiBACT-Soprintendenza

SpecialeperilColosseoeiBeni

ArcheologicidiRoma

MiBACT-Soprintendenza


ArcheologicidiRoma

hasSchema Relationaldatabase Relationaldatabase

dct:contributor MiBACT-Soprintendenza


ArcheologicidiRoma



ArcheologicidiRoma

dct:creator MiBACT-Soprintendenza


ArcheologicidiRoma



ArcheologicidiRoma

owner MiBACT-Soprintendenza


ArcheologicidiRoma



ArcheologicidiRoma

legalResponsible MiBACT-Soprintendenza


ArcheologicidiRoma



ArcheologicidiRoma

scientificResponsible MirellaSerlorenzi MirellaSerlorenzi

technicalResponsible [email protected] [email protected]


Deliverable3.4 119


Classom m

hasAttachedDocuments Referencesfromanexternal

IS_Documentstable

Referencesfromanexternal

AP_Documentstable

accessibleVia http://webais.archeositarprojec

t.it/webgis/


it/webgis/

usesVocabulary Referencesfromthe

IS_vocabolariessuppliedinthe

CIDOC-SITARmappingtechnical

report

Referencesfromthe

AP_vocabolariessuppliedinthe

CIDOC-SITARmappingtechnical

report

expressedIn NO;otherwiseanRDFformatis

availablefortheCIDOC-mapped

versionoftheInformation

Sourcedataset

NO;otherwiseanRDFformatis

availablefortheCIDOC-mapped

versionoftheInformation

Sourcedataset

placeName Località

(public_st_italian_locality.name

)

NO

contactPerson [email protected]

om

[email protected]

m

7.12.1 CIDOCCRMMapping

ACIDOCCRMmappingofSITARinformationhasalsobeencarriedoutwithintheARIADNEproject.

The new CRMarchaeo extension has been also used to create a semantic representation of the

various SITARentities. The goal of thisworkwas twofold: ononehand themappingbetween the

SITARdatabaseschemaandtheconceptsoftheCIDOCCRMandCRMarchaeosemanticmodelwas

defined,inordertocheckthefeasibilityofthisworkandtestthelastreleaseofCRMarchaeo(under

development also with the contribution of ARIADNE). On the other hand, to produce a semantic

encodingofSITARinformation,tobeusedwithintheLinkedDataCloudinfrastructureandtheother

experimental activities ongoing amongWP14 andWP15: for this purpose, the data contained in

SITARdatabasehavebeenextractedandrepresentedinRDFusingtheXMLlanguage.

InformationconcerningCIDOCCRMmappingandencodingofSITARdatabasecanbebrowsedviathe

FORTHMappingMemoryManagertoolathttp://www.ics.forth.gr/isl/3M/.

7.13 MNM-NOKdatabase

This section provides ACDMdescriptions for theHungarianMagyarNemzetiMuzeumdatabase of

archaeological sites. The MNM-NOK database was created by collecting and aggregating all the

necessary data from the other participating departments of the Hungarian National Museum -

NationalHeritageProtectionCentre(http://www.mnm-nok.gov.hu/)forthepurposeoftheARIADNE

project. The table below reports detailed descriptions of mappings between legacy fields in the

original database and the corresponding ARIADNE datamodel entities, necessary for ingestion of

legacy information into the project registry. Information concerning intermediate mappings on

DublinCoreandDCATschemasforlegacyentitiesisalsoreportedwithinthe“OriginalField”column,

whenavailable.


Deliverable3.4 120

OriginalField FieldDescription ACDMField

:originalid(KÖHazonosító) ID acdm:originalID

dct:title(lelőhelyneve) Sitename dcterms:title

dct:description(dokumentációrövid

leírása)

Description dcterms:description

dct:issued(dokumentumdátuma) Dateofthecreatingof

documentation

dcterms:issued

documentation_type dcterms:issued

dct:modified(változtatásdátuma) Modificationdateofthe

documentation

dcterms:modified

dcat:keyword(kulcsszavak) Keywords dcat:keyword

dct:temporal(lelőhelykora) age acdm:nativeSubject

dct:temporal(lelőhelykora) period acdm:nativeSubject

dct:temporal(lelőhelykora) subperiod acdm:nativeSubject

dct:temporal(lelőhelykora) culture acdm:nativeSubject

dct:temporal(lelőhelykora) phase acdm:nativeSubject

dct:spatial/EOVX Spatialcoordinates:X acdm:spatial

dct:spatial/EOVY Spatialcoordinates:X acdm:spatial

dct:creator(személy(ek)akikkészítettéka

dokumentációt)

Creatorof

documentation

acdm:contributorPerson

dct:isPartOf project dcterms:isPartOf

Leadarcheologist acdm:creator

dct:languAge(dokumentációnyelve,ez

végighulesz)

documentation_language dcterms:language

dct:spatial(földrajziterület,megye) county acdm:placeName

dct:publisher(dokumentációtkészítő

intézmény)

documentation_publishe

r

acdm:publisher/Organisation

:legalResponsible(jogifelelős) legalresponsible

institution

acdm:legalResponsible/Organisation

scientificresponsible

archaeologist

acdm:scientificResponsible/Person

dct:accessRights(hozzáféréstípusa) access_rights dcterms:accessRights

dct:rights(milyenjogunkvana

dokumentációhoz)

documentation_rights dc:rights

dct:extent(dokumentációmennyisége.Pl.

ezakollekcióáll:30dbword,13xls,26

dwg,1456JPGstb)

fileformatsinthe

documentation

dcterms:extent


Deliverable3.4 121

7.14 NIAM-BASdatabase

TheNationalInstituteofArchaeologyandMuseumattheBulgarianAcademyofSciences(NIAM-BAS)

participated inARIADNEwith a specific data export of their “Archaeologicalmapof Bulgaria” (AIS

AKB) information system.TheAISAKB is adatabase storing information for archaeological sites in

Bulgaria,protectedbytheBulgarianMinistryofCulture3.AISAKBisasite-baseddatabase,whereone

record (one registration card number) corresponds to a specific place on the surface in which

archaeologicalmaterialsarefound.

ForthepurposesoftheARIADNEcatalogueanXMLdataexportinEnglishofthesystemwascreated

thatconsistsofregistrationcardsoffamousarchaeologicalsites.Separately,arecordiscreatedfor

theeachentryofthewholedatabase.

The following table details the various mappings to the ACDM carried out by NIAM BAS within

ARIADNE.

OriginalFieldnamesinAISAKB

FieldDescription ACDMField Comment

Име titleofthesite dcterm:title

titleofthedatabase dcterms:isPartOf

Особености,Допълнителнаинформацияикоментар

descriptionofthesite dcterms:description acombinationoftwo

fields

Създадено(дата) datewhenacardis

issued

dcterms:issued

Променено(дата) datewhenacardis

modified

dcterms:modified

actuality dcterms:accrualPeriodicity

Регистрационнакарта№

registrationcardnumber acdm:originalId

Вид keywords dcat:keyword one-to-many

relationship

language dcterms:language one-to-many

relationship

Хронология periods acdm:temporal one-to-many

relationship

country acdm:country

years acdm:from

3 An issue released in 2011 that strictly defined its structure, support and limited access

(http://www.lex.bg/laws/ldoc/2135726967)


Deliverable3.4 122

OriginalFieldnamesinAISAKB

FieldDescription ACDMField Comment

years acdm:to

Longitude longitude acdm:spatialLon

Latitude latitude acdm:spatialLat

webpage dcat:landingPage

publisher(organisation) dcterms:publisher

contributor

(organisation)

dcterms:contributor

Автор creator(person) dcterms:creator

Собственик owner(person) acdm:owner

responsibleforthelegal

part(organisation)


Автор responsibleforthe

scientificpart(person)


Собственик responsibleforthe

technicalpart(person)


typeofthedatabase acdm:archaeologicalResourceType

Вид,хронология,съоръжения,находки

subjecttobemappedto

AATvocabularywiththe

corresponding

chronologicalperiodsas

wellasfindingsand

structures

acdm:derived(orprovided)Subject

one-to-many

relationship,a

combinationoffour

fields

Вид originalsubjects acdm:nativeSubject one-to-many

relationship

policyofaccess acdm:accessPolicy

policyofrights acdm:accessRights

rights dcterms:rights

extent dcterms:extent

audience dcterms:audience


The terminological resourcesmapped to AAT fromAIS AKB are internally-produced lists (with the

exceptionofone)whichareusedtomanagefordatamanagementpurposes.

AISAKB’sBulgarianterminologyisintheprocessofmappingtoAATusinganMSExcelfile.Thefile

consistedofthreetabs:ReadMe,Mappings,andLookups.


Deliverable3.4 123

The Readme tab consisted of metadata for the mapping exercise – basic information about the

dataset,creator,dates,etc.TheMappings tabcontainedtheactualvocabulariesand itsmappings.

Thefieldsincludedinthetabare:

- sourceLabel–terminBulgarian

- matchURI–matchtype(exactMatch;closeMatch;broadMatch;narrowMatch)

- targetLabel–AATmapping

- TargetURI–AATmappingURI

- Source-En–BestEnglish-languagetranslation(insomecasesmoreexactthanAATmapping)

- Translation,matching,issuesandoutput.

Mappingisgoingtobedoneintwosteps.ThiswasduetoNIAM-BASreceivingtheoutputmapping

templateaftera translation tookplace.All termswere first translated toEnglishusingavarietyof

resources,includingtechnicallexicons,dictionaries,archaeologicaltexts,andonlineresources.

TranslationsproducedthiswaywereoftenbettermatchesthanAATmappings.Thisisduetoseveral

factors:AATisnotstrictlyarchaeology—oriented,ittakesanAmericanapproachtoterminologydoes

not always coincidewith theBulgarian approach, and languageand cultural differences can affect

theontologyofaterm.


AIS AKB used and internal time period vocabulary for documentation and data management

purposes.AlltimeperiodsusedareusedwithinaBulgariancontext,whichmeansthatsomegeneric

names(likeIronAge),havelocaldatings.

AIS AKB’s internal time-period vocabulary has been mapped to PeriodO’s English-language

vocabulary. Start and end dates for each period have been provided, as well as spatial coverage

(Bulgaria)andalternatelabels(English).

7.15 OEAWdatabases

OEAWdatasetsprovidedthreedatasetstotheARIADNEproject:dFMROe,acollectionofinformation

concerning coins; UK MaterialPOOL, a collection on late Bronze Age sites descriptions; and

Franzhausen-Kokoron,acemeteryexcavationdatabase.Allofthemarelegacydatasetswhichwere

createdindividuallywithoutusingexistingmetadatastandards.

ThedFMROedatasetwas createdbasedon standardsofnumismaticswhileUKMaterialPOOLand

Franzhausen-Kokoron are archaeological datasets, which were created for the requirements of

individualprojects.ThedefinitionsoffieldnamesandmetadatawererecordedinWordfiles.

ExportingtotheACDMmodelwassimplebecausematchescouldbemadeformostoftherequired

fields and new information was gathered when it was not covered in the datasets (e.g. spatial

coordinates,copyright,etc.).

Exporting these three datasets to the ACDM provided OEAWwith the incentive to usemetadata

standards for future projects for good practise. Details about the OEAW dFMROe coins database

mappingstoACDMareprovidedbelow.


Deliverable3.4 124


dcterm:title informationcollectedfrom

textsaboutcollection

dcterms:isPartOf informationcollectedfrom


dcterms:description informationcollectedfrom


dcterms:issued informationcollectedfrom


dcterms:modified informationcollectedfrom


dcterms:accrualPeriodicity informationcollectedfrom


FIND_SPOT_ID uniqueIDoffind

spot

acdm:originalId

dcat:keyword createdbasedon

informationavailablein

individualdataset

dcterms:language informationcollectedfrom


AUTHORITY Primaryareas

(Greek,Roman,..)

acdm:temporal Theprimaryareasarealso

theperiodofthecoins

COUNTRY indFMRÖthereare

coinsfromAustria

&Romania

acdm:country

DATE_FROM startdateofthe

coins

acdm:from

DATE_TO enddateofthe

coins

acdm:to

FIND_SPOT placenameofthe

findspot

acdm:placeName

acdm:spatialLon createdwithGPSvisualizer

basedonplaceName

acdm:spatialLat createdwithGPSvisualizer

basedonplaceName

dcat:landingPage fromprovidedinformation

oncollection,nouniquelinks

couldbeprovidedforthe

collectionduetothe

programmingofthesite

dcterms:publisher informationcollectedfrom



Deliverable3.4 125


dcterms:contributor informationcollectedfrom


dcterms:creator informationcollectedfrom


acdm:owner informationcollectedfrom


acdm:legalResponsible informationcollectedfrom


acdm:scientificResponsible informationcollectedfrom


acdm:technicalResponsible informationcollectedfrom



informationcollectedfrom


acdm:nativeSubject informationcollectedfrom


acdm:accessPolicy informationcollectedfrom


acdm:accessRights informationcollectedfrom


dcterms:rights informationcollectedfrom


dcterms:extent createdbasedon

informationavailablein

individualdataset

dcterms:audience informationcollectedfrom


TwoOEAWdatasetswerealsomappedtoCIDOCCRM:

• The dFMROe coins collection with the 3M tool by OEAW and FORTH

http://139.91.183.3/3MEditor/Index?type=Mapping&action=view&lang=en&id=Mappin

g209

• TheFranzhausen-Kokorondatabase(conceptualmappingonly,viaanExcelfile).


TheterminologicalresourcesmappedtotheAATarestandardnumismaticvocabularies4inthecase

of dFMROe and project-specific controlled vocabularies on finds and findspot types for UK

MaterialPOOLandFranzhausen-Kokoron. The languageused in thesevocabularies isGerman.The

4BernhardProkisch,ThesaurusNummorumRomanorumetByzantinorumBand10,DierömischenMünzendes

OberösterreichischenLandesmuseumsinLinz(Generalsammlung),Wien1998.


Deliverable3.4 126

terminology of the threeOEAWdatasetswasmapped to AAT using the provided Excel filewhich

consistedofthreetabs:Metadata,Mappings,andLookups.

ThemappingmetadatawasprovidedinthemetadatatabandthemappingtotheAATwasdonein

theMappingstab.

• sourceLabel:termtranslatedtoEnglish

• SourceURI:NosourceURIwasavailable,sosourcelabelwasprovided

• matchURI:matchtype(exactMatch;closeMatch;broadMatch;narrowMatch)

• targetLabel:NameoftheAATmapping

• TargetURI:AATmappingURI

• Translation,matching,issuesandoutput

Forthemapping,termsusedaskeywordsintheACDMwerefirsttranslatedfromGermantoEnglish

withthehelpofdictionaries,archaeologicaltexts,onlineresourcesanddiscussionwithcolleaguesto

find terminology thatwasas close to theGermanmeaningsaspossible, andalso inuse inEnglish

archaeologicalliterature.

Then AAT was searched for terms that would match the translations and the definitions of the

controlled vocabulary as closely as possible. In some cases the termswere too specific to find an

exactmatchintheAAT.InsuchcasesthearchaeologicalterminologyprovidedbytheAATwasnotas

rich aswhatwas required (e.g. findspot types). The use of broadmatcheswere only necessary in

17.4%ofcases.

The draft version of the mapping was discussed within the work group until a final version was

achieved.TheMSExcelfileofthefinalversionwasthensent.


OEAWhasnotusedastandardisedtimeperiodvocabularyuntilthecreationoftheAustrianPeriod

Table in 2015, which was created for the ARIADNE project data collection in PeriodO

(ARIADNEConsortium.ARIADNEDataCollection.2015.)5

The period vocabulary of the three submitted datasets follows numismatic or archaeological

standards established in numismatic or archaeological literature. UK MaterialPOOL and

Franzhausen-KokoronaremappedtoPeriodO.InthecaseofdFMROeoneentrycouldspanseveral

periods,sotheacdm:Fromandacdm:Tofieldswereusedtoprovidethestartandenddatesavailable

in the source dataset. The DEFC collection with information on Neolithic and Early Bronze Age

periods in Greece and Anatolia will be uploaded to PeriodO in the future. http://defc.digital-

humanities.at/

7.16 SNDdatasets

SNDusesan internallydevelopedmetadatamanagement system toworkwithdata resourcesand

descriptionsofthem.ThesystemisheavilyinfluencedbytheDDI6metadatastandard,andespecially

version 3.2 thereof, although the system is also compatible with earlier versions. Other

formats/standardssupportedbythesystemnativelyareMARC-XMLandDataCite,although,itsvery

5http://n2t.net/ark:/99152/p0qhb66

6DataDocumentationInitiative(http://www.ddialliance.org/)


Deliverable3.4 127

objectifieddatamodelcansupportmanyotherstandardssupportedifneeded.Oneexampleofthis

wouldbeACDMwherenochangestotheunderlyingmodelneededtobedonetodevelopanexport

routinetotheACDMmodel(detailsprovidedintablebelow).

DuringlateryearstheDDIstandardstemsfromSocialSciences,anddescriptionsofquantitativedata

have developed to better facilitate descriptions of qualitative data and geographicalmaterial. DDI

has incorporated features influencedbyotherstandards likeDublinCoreandDCTerms,whichare

fully supported, SDMX7, ISO11179

8, and parts of the ISO19xxx series. Other influences have come

fromtheGSBPMmodel9.

SND has members in several committees in the DDI Alliance and are actively participating in

developingnewfeaturesandextensionsofthestandard.

DDI3.2 ACDMField

/DDIInstance/StudyUnit/Citation/Publisher acdm:publisher

/DDIInstance/StudyUnit/Citation/Contributor acdm:contributor

/DDIInstance/StudyUnit/Citation/Creator acdm:creator

/DDIInstance/StudyUnit/Citation/Contributor acdm:owner

/DDIInstance/StudyUnit/Citation/Contributor acdm:legalResponsible

/DDIInstance/StudyUnit/Citation/Contributor acdm:scientificResponsible

/DDIInstance/StudyUnit/Citation/Contributor acdm:technicalResponsible

/DDIInstance/StudyUnit/Coverage/TopicalCoverage/Subject acdm:providedSubject

/DDIInstance/StudyUnit/Coverage/TopicalCoverage/Subject acdm:derivedSubject

/DDIInstance/StudyUnit/Coverage/TopicalCoverage/Subject acdm:nativeSubject

/DDIInstance/StudyUnit/Coverage/TopicalCoverage/Subject acdm:hasAttachedDocument

/DDIInstance/StudyUnit/Citation/Title|/DDIInstance/StudyUnit/Citation/title

dcterms:title

/DDIInstance/StudyUnit/Abstract|/DDIInstance/StudyUnit/Citation/description

dc:description

/DDIInstance/StudyUnit/Citation/Publicationdate|/DDIInstance/StudyUnit/Citation/issued

dcterms:issued

/DDIInstance/StudyUnit/@versionDate|/DDIInstance/StudyUnit/Citation/modified

dcterms:modified

/DDIInstance/StudyUnit/Archive/ArchiveSpecific/Collection/CallNumber

acdm:originalId

/DDIInstance/StudyUnit/Coverage/TopicalCoverage/Keyword dcat:keyword

/DDIInstance/StudyUnit/Citation/Language| dc:language7StatisticalDataandMetadataeXchange(https://sdmx.org)

8ISO11179(http://metadata-standards.org/11179/)

9GenericStatisticalBusinessProcessModel

(http://www1.unece.org/stat/platform/display/metis/The+Generic+Statistical+Business+Process+Model)


Deliverable3.4 128

/DDIInstance/StudyUnit/Citation/language

/DDIInstance/StudyUnit/Archive/ArchiveSpecific/Collection/URI dcat:landingPage

/DDIInstance/StudyUnit/Archive/ArchiveSpecific/Collection/OriginalArchiveOrganizationReference

dcat:contactPoint

/DDIInstance/StudyUnit/Archive/ArchiveSpecific/Access/AccessPermission

acdm:accessPolicy

/DDIInstance/StudyUnit/Archive/ArchiveSpecific/Access/AccessConditions|/DDIInstance/StudyUnit/Citation/accessRights

dcterms:accessRights

/DDIInstance/StudyUnit/Citation/Copyright|/DDIInstance/StudyUnit/Citation/rights

dc:rights

/DDIInstance/StudyUnit/Citation/audience dcterms:audience

/DDIInstance/StudyUnit/Coverage/TopicalCoverage/Subject acdm:archaeologicalResourceType

/DDIInstance/StudyUnit/Coverage/TemporalCoverage acdm:temporal

/DDIInstance/StudyUnit/Coverage/SpatialCoverage acdm:spatial

/DDIInstance/StudyUnit/Citation/accrualPeriodicity dcterms:accrualPeridocity

/DDIInstance/StudyUnit/Archive/ArchiveSpecific/Collection/DataFileQuantity|/DDIInstance/StudyUnit/Archive/ArchiveSpecific/Collection/CollectionCompleteness|/DDIInstance/StudyUnit/Citation/extent

dcterms:extent

/DDIInstance/StudyUnit/Archive/ArchiveSpecific acdm:distribution

N/A acdm:hasItemMetadataStructure

N/A acdm:hasMetadataRecord

7.16.1 AATmappings

TheterminologicalresourcesmappedtoAATbySNDareinternally-producedlists(withtheexception

ofone)whichareusedfordatamanagementpurposes.Thevocabulariesarethefollowing:

• Archaeologicalinvestigationtype(arkeologiskundersökningstyp)

• FMIS word list (produced by the Swedish National Heritage Board and used internally by

SND)

• SNDkeywords(ArchaelogyandHistory)

• SNDkeywords(TimePeriods)

• Mappingmethodology

SND’sSwedishterminologywasmappedtoAATusinganadhocMSExcelfile.Thefileconsistedof

threetabs:ReadMe,Mappings,andLookups.

The Readme tab consisted of metadata for the mapping exercise – basic information about the

dataset,creator,dates,etc.TheMappings tabcontainedtheactualvocabulariesand itsmappings.

Thefieldsincludedinthetabare:

• sourceLabel–terminSwedish


Deliverable3.4 129

• SourceURI–URIoftermonSND’swebsite

• matchURI–matchtype(exactMatch;closeMatch;broadMatch;narrowMatch)

• targetLabel–AATmapping

• TargetURI–AATmappingURI

• Source-Hierarchy–CategoryofterminSwedish(whichcategory/vocabularyisitin?)

• Source-ScopeNote–Notesdescribingmappedterms(usuallyavailableonlyforFMISterms)

• Source-En–BestEnglish-languagetranslation(usuallymoreexactthanAATmapping)

• Translation,matching,issuesandoutput.

Mappingwasdoneintwosteps.ThiswasduetoSNDreceivingtheoutputmappingtemplateafterl

translationhadcommenced.All termswere first translated toEnglishusingavarietyof resources,

includingtechnicallexicons,dictionaries,archaeologicaltexts,andonlineresources.

TranslationsproducedthiswaywereoftenbettermatchesthanAATmappings.Thisisduetoseveral

factors:AAT isnotarchaeology—oriented, it takesanAmericanapproachtoterminologythatdoes

notalwayscoincidewiththeSwedishapproach,andlanguageandculturaldifferencescanaffectthe

ontologyofaterm.

That said, in themajorityof casesAAT termswere found tobe sufficientlyprecise toallow foran

exactmatchoraclosematch(ca.63%ofallterms).

The resultingMSExcel file containingadraft versionof themappingwasbouncedbackand forth

untilafinalversionwasachieved.Themappingtemplatewasthenautomaticallytransformedtoan

RDFexpressionofthemappings,readyforupload.


SNDusedaninternaltimeperiodvocabularyfordocumentationanddatamanagementpurposes.All

timeperiodsusedareusedwithinaSwedishcontext,whichmeans that somegenericnames (like

IronAge),havelocaldatings.

SND’s internal time-periodvocabularyhasbeenmapped toPeriodO’sEnglish-languagevocabulary.

Startandenddates foreachperiodhavebeenprovided,aswellas spatial coverage (Sweden)and

alternatelabels(English).

At timeofwritingnotall termsarepresent in the2015ARIADNEPeriodODataCollection.The list

mustbeupdatedbeforetheSwedishvocabularycanbedeemedcomplete.

7.17 ZRCSAZU:

7.17.1 ZRCZbivadatabase

ThetablebelowsummarisestheconceptualmappingsbetweentheZRC-SAZUZbivadatabasefields

and the ACDM entities, and provides also a short description of themeaning of each field in the

original archive. Additional mandatory ACDM entities (such as the dcterms:isPartOf,acdm:archaeologicalResourceType andacdm:country), not explicitlymentioned in any fieldof the

legacy archive but having general validity to the whole scope of the database, have been

subsequentlyaddedtotheACDMmetadatarecordsatconversiontime,inordertoenrichtheACDM

descriptionandmakeitsuitableforpublicationontheARIADNEPortal.


Deliverable3.4 130


Arkas_ID ID acdm:originalID

Arkas DatabaseName dcterms:title

Opis Description dcterms:description

Datum_vnosa Entrydate dcterms:issued

Datum_vnosa Lastupdate dcterms:modified

Najdba Find dcat:keyword

Ime_datacije Chronologicaldefinition acdm:temporal

koorX Spatialcoordinates:X acdm:spatial

koorY Spatialcoordinates:X acdm:spatial

Omemba Mentioned acdm:contributorPerson

Vnašalec Dataentryresponsible acdm:technicalResponsible

Opredelitev Findclassification acdm:nativeSubject

7.17.2 ZRCSAZU:Arkasdatabase

ThetablebelowsummarisestheconceptualmappingsbetweentheZRC-SAZUArkasdatabasefields

andtheACDMentities,andprovidesashortdescriptionofthemeaningofeachfieldintheoriginal

archive. Additional mandatory ACDM entities (such as the dcterms:isPartOf,acdm:archaeologicalResourceType andacdm:country), not explicitlymentioned in any fieldof the

legacy archive but having general validity to the whole scope of the database, have been

subsequentlyaddedtotheACDMmetadatarecordsatconversiontime,inordertoenrichtheACDM

descriptionandmakeitsuitableforpublicationontheARIADNEPortal.


Sifra Code acdm:originalID

Zbiva DatabaseName dcterms:title

Opombe Description dcterms:description

Datum_vnosa Entrydate dcterms:issued

Datum_vnosa Lastupdate dcterms:modified


Deliverable3.4 131


Najdba Find dcat:keyword

Datacija Period acdm:temporal

Najprej From acdm:from

Najkasneje To acdm:to

Država Country acdm:country

lat Latitude dcterms:spatial

lon Longitude dcterms:spatial

Najdba Find acdm:nativeSubject

8 Conclusions

This report presents the process of creating the ARIADNE registry in detail, and describes the

standards, metadata systems, thesauri descriptions, and services it contains in its final phase of

development. The registry is an important tool for archaeologists and constitutes a valid tool for

supporting theiractivities,as itprovides themwith theability todiscoverdatasets, standardsand

other similar resources useful for their research. First the report analysed the ACDM model,

developed specifically for the creation of the registry, and the implementation carried out by the

partners to contribute toa common information-sharingplatform,andprovide interoperability for

their information within a complete ecosystem, from which archaeological information can be

selected, extracted and reused in order to extend the horizon of archaeological research, by

spreadingarchaeologicalqueriesacrossdifferentinternationalrepositories.

TheACDMmodelwasoneofthemainvehiclesforthisintegration.Developedfromwell-established

internationalstandards,ithasprovedtobeaflexibleandcapabletoolableforadaptingitselftothe

different facetsof thevariousstandardsusedbycontentproviders toencode theirdata.Acareful

initialanalysiswasthekeytobuildingasolidandreliabledatamodel,abletointeractwithhigh-level

terminology resources, such as the AAT thesaurus and spatiotemporal entities provided by

Geonames and PeriodO, and to foster interpretation of knowledge concerning various datasets of

ARIADNEinanunambiguouswaytominimisethelossofinformationresultingfromthemappingand

conversionoperations.

The solidity of ACDMmodel has definitely helped the activities to be carried out by the content

providers,asdocumentedinthisreport,tofindcorrespondencesbetweentheentitiesusedintheir

legacyarchivesand theentitiesprovidedby themodel itself.Thesupportofwell-knownandwell-

established standards, such as the Getty Thesaurus, has also pushed the integration beyond the

limits imposed by the heterogeneity of the archaeological data and to overcome the undoubted

differences inoriginbetween thedifferent informationheldbypartners. Themappingoperations,

enrichment, conversioncarriedout throughasetof toolsprovidedby theARIADNE infrastructure,

havebeen completed in anoptimalwayand this has allowed ingestion into the registryof all the


Deliverable3.4 132

archaeological information provided to the project, and its publication in theARIADNEportal, the

trueheartofintegrationwhereinteroperabilityhasbecomereal.

ariadne: final report on standards and project registry

Data & Analytics