Ariadne: Initial Infrastructure Testing Report

Authors: Anthony CornsLouise KennedyEvie Monaghan

The Discovery Programme

Ariadne is funded by the European Commission’s 7th Framework Programme.

D12.4: Initial Infrastructure Testing Report

ARIADNE–D12.4:InitialInfrastructureTestingReport

ARIADNE isaproject fundedby theEuropeanCommissionunder theCommunity’sSeventhFrameworkProgramme,contractno.FP7-INFRASTRUCTURES-2012-1-313193.Theviewsandopinions expressed in this report are the sole responsibility of the authors and do notnecessarilyreflecttheviewsoftheEuropeanCommission.

Version:1.0 31March2016

Authors: AnthonyCornsLouiseKennedyEvieMonaghanTheDiscoveryProgramme

Version Content Author Date

0.1 Initialdraftbasedonactivitiescarriedoutbythe

DiscoveryProgramme

A.Corns,L.Kennedy,E.Monaghan(DISC)

23/03/2016

0.2 Commentsforedit H.Wright(ADS) 28/03/2016

0.3 UpdatedbasedoncommentsfromH.Wright

(ADS)

A.Corns,L.Kennedy(DISC)

31/03/2016

0.4 Formattingedits A.Corns(DISC) 04/04/2016

ARIADNED12.4

3

Table of Contents

1 ExecutiveSummary.........................................................................................................6

2 Objectives........................................................................................................................7

3 UseRequirements,ServiceDesignandImplementation..................................................83.1 GeneralRequirements..................................................................................................................10

3.1.1 DataTransparency...............................................................................................................................103.1.2 DataAccessibility.................................................................................................................................113.1.3 MetadataQuality.................................................................................................................................123.1.4 DataQuality.........................................................................................................................................143.1.5 InternationalDimension......................................................................................................................14

3.2 SpecificRequirements..................................................................................................................163.2.1Crossborderperiodsearch.......................................................................................................................163.2.2Crossbordersubjectsearch......................................................................................................................163.2.3Mapdrivensearchingorvisualisation.......................................................................................................173.2.4Bibliographicmetadatafromgreyliterature.............................................................................................173.2.5Integrationandinteroperabilityfromscientificdatasets..........................................................................183.2.6Integrationofparticularkindsofartefactdata.........................................................................................18

4 ARIADNERegistry..........................................................................................................184.1.1 Signupandlogin.................................................................................................................................184.1.2 Addingresources.................................................................................................................................204.1.3 AddDataset.........................................................................................................................................214.1.4 Addingtemporalinformationtoaresource........................................................................................224.1.5 AddingDataFormattoaDataset........................................................................................................234.1.6 AddVocabulary...................................................................................................................................244.1.7 AddMapping.......................................................................................................................................254.1.8 AddDistribution..................................................................................................................................254.1.9 AddMetadataSchema........................................................................................................................264.1.10 AddDigitalObjectDescription............................................................................................................264.1.11 AddService..........................................................................................................................................284.1.12 AddLicence..........................................................................................................................................284.1.13 AddGIS................................................................................................................................................284.1.14 AddCollection.....................................................................................................................................314.1.15 OtherRegistryfeatures.......................................................................................................................32

4.2 ConclusionsandRecommendations.............................................................................................33

ARIADNED12.4

4

5 Aggregation Service, Validation Services, Metadata Enrichment Services: the MOReaggregationtool...................................................................................................................36

6 SupportPortalandDocumentation...............................................................................38

7 Strategyforfurthertesting............................................................................................40

8 ConclusionsandRecommendations...............................................................................41

9 References.....................................................................................................................45

ARIADNED12.4

5

Acronymsandabbreviations

API ApplicationProgrammingInterfaceACDM ARIADNECatalogueDataModelRESTAPI RepresentationalStateTransferApplicationProgrammingInterface

ARIADNED12.4

6

1 Executive Summary

This document is a deliverable (D12.4 Initial Infrastructure Testing Report) of the ARIADNE project(“AdvancedResearchInfrastructureforArchaeologicalDatasetNetworkinginEurope”),whichisfundedunder the European Community’s Seventh Framework Programme. It presents results of the workcarriedoutinTask12.4Testing.

The tasks ofWP12 Implementing Interoperability aim to specify use requirements and design for theARIADNE infrastructure and to implement and test that design. Task 12.4 is comprised of testing theintegrated infrastructure built in Task 12.3 Implementing Integration, basedon the requirements anddesign specified in Task 12.1 Use Requirements and 12.2 Infrastructure Design. This documentaugmentsthesynthesisofrequirementsanddesigngiveninD12.2withtheinfrastructureimplementedinD12.3andteststheimplementationagainsttherequirementsspecified.Eachrequirementisoutlinedwith the infrastructural tools and/or services designed to meet it and a brief overview of theimplementationdocumented in12.3.Recommendationsaremadebasedonthisanalysis.Thegeneraluserequirementsareaddressedinthefirstinstance,followedbymorespecificrequirementsaddressingintegrationactivities.

Theinitialinfrastructureimplementationhasmetmanyoftherequirementsspecified.Someaspectsnotyet visible will require further testing in Task 12.6 Final Testing Report. Some clarification of userequirements for thePreviewServicemaybenecessary:D12.2designsa service thatpreviewssearchresults, as described above and illustrated in the prototype portal, as a list, on a map and timeline(D12.2, 24) butwhich can also preview individual records. D12.3 has implemented a Preview Servicethroughwhichresearcherscanpreviewtheirowndatasetsinanumberofformats,whichseemstobemorecloselyalignedwiththeRegistry(17).

The Support Portal, which includes documentation and user guidance, needed to be approachedholistically inorder toprovideclearandcoherentguidance toavarietyofusersatdifferentpointsofinteraction with the infrastructure. Documentation is required for each major component of theinfrastructure. The Registry input tool provides the necessary functionality to enable depositing ofmetadata.TheuserexperienceoftheRegistrycouldbeimprovedandmorecloselyguidedwithchangesindesign.Atableofrecommendationsfortheinfrastructureisincludedattheendofthisdocument.

ARIADNED12.4

7

2 Objectives

Theobjectivesofworkpackage12are:• ToadaptinfrastructuresprovidedtoARIADNEforintegration.• Todesignandsetupthenecessarytools(crosswalks,mappings)andresourcesfor

interoperability.• Tosetuptheinternal(APIs)andexternal(human)interfacestoaccesstheintegratedresource.

WorkPackage12iscomprisedofthefollowingtasks:

• 12.1Userequirements• 12.2DesignandSpecifications• 12.3ImplementingIntegration• 12.4Testing

Task 12.4 is comprised of testing the integrated infrastructure built in Task 12.3 ImplementingIntegration, and based on the requirements and design specified in Task 12.1Use Requirements and12.2 Infrastructure Design. The implementation is examined in light of the requirements and designdocumentedindeliverables12.1and12.2.Infrastructuralelementswithuserinterfacesweretestedforthistask.ThisdeliverablereportsontheresultsofTask12.4.Itcomprisesacomparisonoftheuserequirementswith the service design and implementation, with recommendations. As the first point for dataintegration,ARIADNE’sRegistrywastested.DocumentedinD12.2,theRegistryisakeyelementoftheinteroperabilityframeworkanddrivesresourcediscoverywithinthepublic-facingARIADNEportal.

Figure1:ConceptualframeworkwithoutliningofWP12rolebyAchilleFelicetti,D12.1,p7.

ARIADNED12.4

8

3 Use Requirements, Service Design and Implementation

Thework ofWP12 has been to specify use requirements for the ARIADNE infrastructure (noting theextensive work of WP2 on user needs and WP3 on the Registry), and design and implement aspecificationforthatinfrastructurebasedontheuserequirements.

Use requirements specified in D12.1 focused on three areas: datasets,metadata standards, schemasandvocabulariesandaccessandsharingpolicies.Theuserequirementsreflectthedataavailableinthearchaeological sector, and priorities for the integration activities for different types of data. Userequirementsfortheinfrastructurehavebothpracticalandpolicyimplications,bothofwhichmustbereflectedintheimplementationasappropriate(D12.1,4,5).

Thedesignspecificationfocusedonanintegrationstrategywhichaddressedmetadataintegrationanddata integration, and in the first instance, enabled cross-search of resources throughWhat, Where,WhenandResourceTypefacets.ConsistencyandqualityarekeyrequirementsforcontentaddedtotheARIADNEinfrastructure(D12.2,16,17).

Theinitialinfrastructureimplementationaddressedthecoreservices,withfurtherimplementationandtestingto follow inWP12.Keycomponentsof thearchitecturedescribed in12.3areanRDFstore,anElasticsearch index and the Registry service (together, the Data Access Layer of the integrationarchitecture,D12.2,Fig.2,10),andtheMOReaggregationservicewhichalsocontainsvalidation,qualityandenrichmentservices(D12.3,7).

D12.2InfrastructureDesignprovidedatableofconformance,reproducedinTable1below(D12.2,12),withtheuserequirementsspecified inD12.1.Thisdocumentaimstoaugmentthatsynthesiswiththeinfrastructure implemented inD12.3and test the implementationagainst the requirements specified.Each requirement is outlinedwith the infrastructural tools and/or services designed tomeet it and abriefoverviewoftheimplementationdocumentedinD12.3.Recommendationsaremadebasedonthisanalysis. The general use requirements are addressed in the first instance, followed bymore specificrequirementsaddressingintegrationactivities.

ARIADNED12.4

9

Requirements DataAc

cessLayer

Integration&In

terope

rability

Dep

ositService

Metad

ataEn

richm

ent

Vocabu

laryM

anagem

ent

Qua

lityService

Preservatio

nService

Digita

lAssetsMan

agem

ent

ARIADNEPo

rtal

PreviewService

ResourceDiscovery

DataTransparency • • ••

DataAccessibility • •• •••

• • •

MetadataQuality • •

• •••

DataQuality

•

•••

InternationalDimension •

••

••

• ••

Cross&borderperiodsearch •

••

• • •

Cross&bordersubjectsearch •

••

• • •

Mapdrivensearchingorvisualisation

•

•• •••

Bibliographicmetadatafromgreyliterature

•

• • •

Integrationandinteroperabilityfromscientificdatabases

•••

•

•

Integrationofparticularkindsofartefactdata

•••

Datasetassessmentrequired

•••

Table1:ConformanceoftheARIADNEInfrastructuretoUserrequirements(D12.2,12)withnumberofdotsindicatingthedegreeofrelevance,i.e.•low,••medium,•••high.

ARIADNED12.4

10

3.1 General Requirements

3.1.1 Data Transparency

Requirement: From D2.1 First Report on User’s Needs, the requirement centres on resolvingfragmentation of the archaeological record to provide “a good overview (D12.1, p13)” of thearchaeologicaldatainexistenceandavailableonline.

Design:D12.2designsthreeservicestomeetthisneed:theDataAccessLayer,theARIADNEPortalandthePreviewService (D12.2,p12). TheDataAccess LayerprovidesaRESTAPI to return, edit, addanddelete records in the ARIADNE Catalogue. The authentication required to perform these tasks isprovidedthroughtheARIADNECatalogue,usingAPIkeysforthemachineinterfaceanduser/passwordchallengeonthehumaninterface(D12.2,p34).ThePreviewserviceenablespreviewsofsearchresultsandindividualrecordsasalist,onamaportimelineorusingacombinationofmap,timelineandothercriteria(D12.2,p24).

Implementation:TheDataAccessLayerdocumentedinD12.3(Section5DataAccessandManagementServices, p18) is composedof theRegistry, anRDF triplestore and Elasticsearch indexing service. Thedesignmeets the requirement by providing input tools for data resources, which in turn reflect therequirementsof theACDM,anda suiteof toolswhich should facilitatedynamic (integrated) resourcediscovery.

TheARIADNEPortal is theuser interface foraccess todata resources,and itsdesign iscrucial touserperception of need fulfilment.What,Where andWhen browsing as outlined in the portalmock-upspresentedinD12.3answertheneedfordynamicoverviewsimplyandclearly(p38-40).

With regard to the preview service, D12.3 states “through the data access management services,researcherscanpreviewtheirdatasetsindifferentformats,suchasRDF,JSONorXML”(D12.3,p18).

Recommendation: Resolve the use of language around the terms ‘Registry’ and ‘Catalogue’ in anysupport documentation and user interfaces [R31]. D12.3 refers to the Registry as “is a single pointwhere all ARIADNE resources are stored and made available.” (D12.3, p20). ARIADNE Catalogue:EnteringDataResourcesreferstotheCatalogueasthestore(p3)andtheRegistryastheinputtoolformetadatarecords(p3).

TheimplementationoftheACDMbyusersinputtingmetadatawithinthistooliscrucialtomeetingtheneeds around a transparent overview of existing available data. Effective support and guidance isrequired (see Support Portal and Documentation, p32). The needs aroundmetadata quality are alsorelevantasincorrect,incompleteorpoorqualitymetadatawillobstructtrustin,andusefulnessof,theoverview.

IntheprototypeARIADNEPortal,thePreviewServicemakesavailablepreviewsofsearchresultsinmapandtimelineviews:theusercanexploreamaportimeline,refinethoseaccordingtotheirinterestanda

ARIADNED12.4

11

preview of the results for that refinement is produced on the fly. Similar map and timeline basedpreviews are available alongside a list of search results on the search results landingpagewithin theprototype portal. Further comments on visual overviews relevant to this requirement can be foundusing?mapdrivensearchingorvisualization(3.2.3,p15).

Someclarificationoftheuserequirements for thePreviewServicemaybenecessary:D12.2designsaservicethatpreviewssearchresults,asdescribedaboveandillustratedintheprototypeportal,asalist,on a map and timeline (D12.2, p24) but which can also preview individual records [R32]. D12.3documents implementation of a Preview Service through which researchers can preview their owndatasetsinanumberofformats,whichseemstobemorecloselyalignedwiththeRegistry(p17).WithintheRegistry,whiledocumentsorobjectscanbeattachedtoresources,itisunclearwhetherthesecanbemadeavailabletogeneratepreviewsoftheresource.D2.2(p108)andD13.1(30-32)bothrefertothehighprioritygiventothisfeatureforquicklyassessingrelevancebyusers.

3.1.2 Data Accessibility

Requirement:Datasetsshouldbeavailableinanuncomplicatedway,costshavebeenandareabarriertoaccess,datais‘dark’(D12.1,p?).

Design:D12.2designs six services tomeet theuser requirementsarounddataaccessibility.ThesearetheDataAccessLayer,Integrationandinteroperabilityservice,Depositservice,theARIADNEPortal,thePreviewServiceandResourceDiscovery.

TheDataAccessLayer,theARIADNEPortalandthePreviewServicearediscussedin3.1.1above.

TheIntegrationandInteroperabilityserviceisdesignedtointegrateelementsoftheARIADNECatalogue,“anddevelopsthetoolsandcomponentstoenabletheintegrationofarchaeologicalresources.”(D12.2,p26). It is informedbythe integrationstrategyoutlined inD12.2,whichoutlinesmetadata integrationusingthethreeresourcetypesspecifiedintheACDM,twopropertiesforthematicdescription,facetedcross-search and vocabularymapping. Data integrationwill be implemented on a phased basis, fromidentifyingdatasetswithpotentialforusefulintegrationthroughtodemonstration.

The Deposit service is designed to allow users to deposit metadata which conforms to the ACDMschemaand includesvalidation (mandatory requirements, integrity checks); as such it also referencestheQualityservice.

The Resource Discovery Service enables access to data through searches on the Catalogue based onvarious criteria including the subject, geographical and temporal facets specified in the userrequirements.

Implementation: TheDeposit Service, realized as amanual inputweb tool in theRegistry, has beentested,seeSection4ARIADNERegistry,p17.

ARIADNED12.4

12

Early stages of user interface implementation of the Resource Discovery Service are documented inD12.3(35-42).

Recommendation:

Appropriate,targetedguidancefortheuserintheuseoftheRegistrytoadddataresourcesisrequired[R33].Thetoolitselfiseasytonavigateanduse.SomeofthestructuresexpectedbytheACDMarenotintuitive and shouldbeexplained clearly, briefly and simply to theuser.Moredetailed commentsontestingoftheRegistryareatSection4ARIADNERegistry(p17).

Theuserequirementsanddesignhavemainlyfocusedontheend-userorresearcheruser’sneedsandexperiencewiththeinfrastructure.Theproject’sabilitytoaddressfragmentationofthearchaeologicalrecordisgreatlyinfluencedbytheexperienceofthedepositoruserandtheirsatisfactionwiththetools,servicesandrepresentationoftheircontent.TheSupportPortalanddocumentationarekeyaspectsofthisrelationshipandarefurtherdiscussedinSection6SupportPortalandDocumentationbelow(p32).

Costissuesneedtobeaddressedatthepolicylevel;asmentionedinD2.1,abusinessandsustainabilitymodelisrequired(13)[R34].

3.1.3 Metadata Quality

Requirement: ARIADNE should demonstrate good practice, raise awareness about metadata andusefulnessandstandardsforinteroperability.D12.1specifiedmetadatamappingtools,metadatainputand description tools and a SKOSifier tool. Appropriate metadata standards can also addressrequirementsintheareasofdatatransparencyandaccessibilityandtheinternationaldimension.

Design: D12.2 uses four services to meet this requirement, the Data Access and Integration andinteroperability layers, theMetadata Enrichment service and theQuality service. TheDeposit servicediscussedin3.1.2aboveisrelevanttotheinputanddescriptionofmetadata.

5.4 Catalogue Record Quality Service of Functional requirements (D12.2) specifies checks oncompleteness and correctness of metadata as functions of the aggregation service. In addition,metadata in native repositories should be evaluated through endpoints described inariadne:distribution,whichentityshouldincludeinformationonmetadataformatsandschemas.

5.8 Catalogue Record Enhancement specifies relationshipmining and automatic linkingwith thesauriandvocabularies.

TheARIADNEDataCatalogueModel specification, and the communicationof it through theARIADNEtools and services is central to themetadata quality requirements in the areas of raising awareness,demonstratinggoodpracticeandtheusefulnessofstandardsforinteroperability.

ThetooltoSKOSifyvocabulariesisdesignedwithintheVocabularyDirectoryManagementservice.

ARIADNED12.4

13

Implementation:D12.3documentstheimplementationoftheMOReaggregator,whichisakeyservicefortheIntegrationandInteroperabilityserviceandtheMetadataEnrichmentandQualityservices.

The Quality service is implemented within MORe and measures completeness, correctness andconsistencyof themetadatavaluesagainstparameters forACDM, returninggraphedvalues to signifyquality.

The Validation service implemented inMORe is also key to metadata quality. Validation against theACDM XSD takes place automatically within MORe during ingest. The datasets are normalised, linkchecksareperformedwhereURLsarepresentandschematronrulevalidationisalsocarriedout.

Theenrichment servicesuse vocabularymatching, geo-location andothermicro-services to tailor theenhancementofcataloguerecordsaccordingtotheneedsoftheuserand/ordataresource.Themicro-servicescanbeusedwithinMOReordirectly.

Enrichmentservicesarefocusedaroundfourareas:subject,space,timeandother.

ThematicorsubjectenrichmentisservicedbybothmanualandautomatictoolswithinMORe.Accesstoa wide variety of vocabularies is provided within the tool, which should reduce barriers to use andintegratesubjectenhancementintothedeposit/ingestworkflow.EnrichmentwithDBPediaURIsisalsoavailablewithinthetool.

Vocabularymanagement tools and services arediscussedunder3.1.5below, InternationalDimension(13).

Task 12.3 did not implement any services which answer the design specification around mining ofrelationships.

Recommendation: The quality services are crucial to developing trust in the (usefulness of the)infrastructure. D12.3 does not specify whether specific parameters for quality (beyond mandatoryelements)canbeusedasgatewaysfordepositand/or ingest.Guidanceforusersonthenatureoftheerrorsthrownduringthedepositandingestprocesswouldbehelpful[R35].

Subject enrichment with terms from SKOSified vocabularies answers the need for ARIADNE todemonstrate best practice, providing a means to demonstrate the benefits of Linked Data forarchaeologyinfuture.

Portal:Subjectbrowsing(‘What’)hasbeenimplementedintheprototypeportalwithawordcloud.Themostpopularsubjecttermsarelargestinthedisplay,theleastpopularthesmallest.Thesmallesttermsaredifficulttoread.Thewordcloudgivesagoodvisualoverviewofthesubjectscurrentlycoveredintheprototypeportal,withdirect links to listsof resources taggedwithany termdisplayed in thecloud. Itmaybeusefultoalsodisplayawordcloudofthe‘derivedsubject’facetorGettyAATterms,eitherasafilterorasecondwordcloudinthe‘What’browsingarea[R36].

ARIADNED12.4

14

3.1.4 Data Quality

Requirement:Balancedataqualityandquantity

Design: D12.2 designed two services to answer data quality needs, the Data Access Layer and theQualityservice.

Implementation:D12.3implementsmetadataqualityservicesratherthandataquality.

Recommendation: As perspectives on which datasets constitute data and which metadata can besubjectiveorfluid,dependingonuse,theprojectshouldcommunicateclearlytousers itsapproachtodataandmetadata, ifpossible [R37].Forexample,dataaddedasmetadata forasingledataresourcecanbecomepartofadatasetforresearchwhichsynthesizesoranalysesaspectsofarchaeologybroadly.Thismayneedtobedefinedindependentlyfordifferenttypesorcategoriesofdata.

3.1.5 International Dimension

Requirement:FromD2.1,D12.1highlightedthedesireamongusersforeasyaccesstointernationaldataandtherelativelyhighlevelofdissatisfactionamonguserswithcurrentaccess.D12.2specifiedworkonmetadata schemas and vocabularies to meet the needs around availability (and integration) ofinternationaldataresources.

Design:D12.2designsfiveservicestomeettheneedsaroundInternationalDimension:theDataAccesslayer,theIntegrationandInteroperabilityService,VocabularyManagement,theARIADNEportalandthePreviewservice.

Implementation: Thoughnotdocumented inD12.3 theACDMschemawillbecrucial tomeetinguserneedsforinternationaldataandintegrationofmetadataacrossborderswithintheARIADNEportal.TheVocabulary Management Service, which is described and implemented in the subject area of theMetadataEnrichmentServicewithintheMOReaggregator,providesaccessto27relevantvocabulariesto enable subject enrichment, which should enhance user experience of cross border subject searchwith the ARIADNE Portal (continuingwork on extensions of the CIDOC CRM inWP 14 is essential todeveloping availability and integrationacross international datasets). TheVocabularyDirectory is alsoavailable through a REST API. The Vocabulary Matching Tool designed by the Hypermedia ResearchGroup at the University of South Wales will also be available as a service through the ARIADNEinfrastructure.

Recommendation:GiventheEuropeanaimsofARIADNE,thesourcevocabulariesavailablethroughtheVocabulary matching tool could be expanded to allow broader mapping to AAT [R38]. Guidancedocumentation on how to prepare vocabularies for inclusion in the tool and for mapping would berequired[R39].Thisworkcouldbetargetedatdatacentres,institutionalrepositoriesanddatamanagersandmade available on a semi-public basis or to ARIADNE participants only.Multilingual thesauri areaddressedinWP13.

ARIADNED12.4

15

ARIADNED12.4

16

3.2 Specific Requirements

User acceptance of portal features will be reported in WP13, so are therefore described here forcompleteness,butwerenotsubjecttothesamelevelofevaluation.Recommendationshavebeenmadehowever,inseveralinstanceswhereitwasrecognisedthatimprovementswereneeded.

3.2.1 Cross border period search

Requirement:D12.1 specified crossborderperiod search for sites andmonumentsdata, interventiondataand fieldworkdata.The feasibilityof integrationof scientificdata for crossborderperiodsearch“mustbeestablishedcasebycaseaccordingtocontenttype”(p5).

Design: D12.2 designed five services tomeet the needs of cross and border period search: the DataAccess layer, the Integration and Interoperability Service, the ARIADNE Portal and the Preview andResourceDiscoveryservices.

Implementation: D12.3 describes the PeriodO project, a gazetteer of period assertions, which willprovideaSKOSifiedcollectionofperiodnames.Theperiodgazetteerwillbeimplementedasametadataenrichment service inMORe, and should enable cross border period discovery through the ResourceDiscoverylayer.

Portal: In theARIADNEprototypeportal, users canuse the ‘Period’ facet to filter their search resultsbasedonthetemporaltermssuppliedwiththecontent.WithinMORe,usersmaycreatecollectionsoftemporalmappings for usewith their content. Theymust supply the sourceperiod’s label, beginningandenddatesandatermtosearchfor.

Recommendation: The targets of this search are not visible within the enrichment service currently.Documentationisrequiredforthisenrichmentservice[R40].

3.2.2 Cross border subject search

Requirement:D12.1requiredacross-bordersubjectsearchforsitesandmonuments,interventionandfieldworkdata.Thefeasibilityof integrationofscientificdataforcrossbordersubjectsearch“mustbeestablishedcasebycaseaccordingtocontenttype”(p5).

Design:D12.2designedfiveservicestomeettheneedsofcrossbordersubjectsearch,theDataAccesslayer, the Integration and Interoperability service, theARIADNEPortal and thePreviewandResourceDiscoveryservices.

Implementation:Asdiscussedin3.1.5InternationalDimensionabove,D12.3implementssubjectmicro-servicesformetadataenrichment.Integrationofdatawillbeimplementedonaphasedbasis.

ARIADNED12.4

17

Portal:SubjecttermsforcontentprovisionhavebeenmappedtothespineoftheGettyAATtoenablesearchingacrossresources.Thisenablestheinclusionofboththecontentprovider’sownsubjecttermsandtheequivalenttermsfromGettyAAT,whichappearas‘NativeSubject’and‘DerivedSubject’facetsinthesearchresultsviewintheprototypeportal.CrossbordersearchingofsubjectsfrommetadataarealsobeavailableinthePortalthrougha‘What’browsinginterface.

3.2.3 Map driven searching or visualisation

Requirement:D12.1 specifiedmapdrivensearchingorvisualisationofdata for sitesandmonuments,interventionandfieldworkdatabases.Thefeasibilityof includingburialandscientificdatasets inthesetoolsmustbeexaminedonacase-by-casebasis(12.1,p5).

Design:D12.2specifiesthreeservicesforthisrequirement:theDataAccess layer, theARIADNEPortaland the Preview service. The Data Access layer pulls results from the catalogue to present in thepreviewingserviceassearchresultsorindividualrecords.Presentationonamapisonlyonemethodofdisplayofferedwithinthepreviewservice.

Implementation:D12.3presentedmock-upsofmapbrowsingandsearchingcapabilities implementedinthePortal.

Portal: Map driven searching is available through the ‘Where’ browsing feature of the prototypeARIADNE portal. Any resources which have spatial information are included in this view. Users canrefine a spatial area and return a list of results which reference that area. The map-based ‘Where’searchfacetcanbeusedalongsidethislisttoprovidefurtherrefinements.

3.2.4 Bibliographic metadata from grey literature

Requirement:Integratebibliographicmetadatafromgreyliterature.

Design:D12.2designedfourservicestomeettherequirementtomakemetadatafromgrey literaturemore accessible, the Data Access layer, the ARIADNE Portal, the Preview Service and the ResourceDiscoveryService.Assuch,therearenoservicesdesignedonlyforthisrequirement,theinfrastructureshouldmeetitthroughtheservicesdevisedalsoforotherrequirements.

Implementation:As thedesigndidnot specify specific services for this requirementonly,D12.3doesnotrefertoitdirectly.

Portal: The prototype portal demonstrates the integration of bibliographic metadata from greyliteraturethroughtheArchaeologyDataService’sGreyLiteratureLibrary.

ARIADNED12.4

18

3.2.5 Integration and interoperability from scientific datasets

Requirement:IntegrationofscientificdatasetsisaspecifiedrequirementfordatainD12.1.Analysesinsimilarareasofstudymaysharesimilarstructures,whichwouldaidintegration(D12.2,p23).

Design: D12.2 designed three services tomeet this requirement: the Integration and Interoperabilityservice,theDepositServiceandtheResourceDiscoveryservice.

Implementation:“TheDepositserviceallowsregistereduserstodepositmetadatafollowingtheACDMschema.”(D12.2,p25).ThedepositserviceiscurrentlyimplementedintheRegistry.

Recommendation: It is not clear fromD12.1orD12.2what kindof integrationand interoperability issought [R41]. Thus D12.3 does notmention Integration and interoperability from scientific datasets.Metadataintegrationisthefirststeptowardsmeetingthisrequirement.DataintegrationisaddressedinWP16.

3.2.6 Integration of particular kinds of artefact data

Requirement: D12.1 requires the integration of particular kinds of artefact data, including data onburials.Artefactdataonstonetoolsandceramicsmaybemostamenabletointegration.

Design:D12.2designedoneservicetomeetthisneed,theIntegrationandInteroperabilityservice.

Implementation:TheMOReAggregator.

Recommendation:TheaggregatorservesthesearchcapabilitiesrequestedintheuserrequirementsbytransformingallmetadatarecordstoACDMandpushingthemtoanRDFstore,whichenablesindexedsearch. Data integration is not implemented in D12.3; according to the data integration strategyoutlined inD12.2,thepreparationphasefocuseson“accessfunctionality”(p18)andpresentingwhichdatasetsaregoodcandidatesforintegration.IntegrationisplannedforthethirdphaseandisaddressedinWP16.

4 ARIADNE Registry

4.1.1 Sign up and login

The registration and login at theRegistry homepage is a very simple and fast process; aminimumofinformation was required and confirmation emails were received quickly. While the low barrier toaccess isuser-friendly, it raisesquestionsaroundmanaging inputs andquality.Anofferof trainingorguidanceonfirst login(forexamplewithawalkthroughvideo,orhighvisibility forthesupportportal)mightbehelpfultointroducenewuserstothestandardsandqualityexpected,thoughtheaggregationserviceswillalsofilteroutlowqualityinputs.

ARIADNED12.4

19

Following login, the registry homepage is simple, but it may benefit from a clearer visual structure.Sevenoftheavailableresourcetypesarenotvisibleonthispage,includingthemandatoryfoaf:agent.Key data resource classes could be grouped together, and language resources grouped separately,reflecting the resource types listed in D12.2 (16). A basic visualisation may help the user to betterunderstand the relationships between data resources and language resources, and illustrate whichlanguageresourcesaremandatoryorrecommendedforparticulardataresources.

Shortdescriptionsofeachresourcetypewouldreduceanyambiguityandguidetheuserquicklytotheappropriateclassofresource.Theusers’firstexperienceofthetoolmayalsobeimprovedbyaddinganotificationthatanagentismandatorybeforeaddinganyotherresource.

Figure2:Registryhomepageonlogin.

Recommendations[R1-4]:

• Includetheadditionofaninstanceoffoaf:agentaspartoftheregistrationprocess,oraspartofnavigationduringfirstadditionofadataresource.

• Includepagenavigationorpop-upwhichdirectsuserstoguidanceforcontentprovisiononfirstonetofivelogins.

• Onesentencedescriptionsofeachdataresourcewheretheuserchooseswhichresourceclassissuitableforhis/hercontent.

• Includeabasicvisualisationoftherelationshipsbetweendataresourcesandlanguageresourceswithinuserguidance,includinghighlightingofmandatorylanguageclassesfordataresources.

ARIADNED12.4

20

4.1.2 Adding resources

Testingwas carried outwith a collection of digital assets comprised of textualmetadata, 3Dmodels,videoandimages.Thecollection-levelmetadatawasexportedtoanxmlfilestructuredaccordingtotheCARAREmetadata schema.Theassets areavailableonlineand themetadata containsaURL link toarepresentationofeachasset.FollowingconsultationwiththeACDMspecification,thefilewasaddedasadataset.

Manyofthefieldnameswithinthewebformshavesmallpop-upsexplainingthepurposeofthefieldortheexpectedcontent.Theuser comes toexpect thesewhilenavigating through the sitebut theyaremissingforsomeelements.

The URL for the online versions of the data referred to in the metadata set was added as anAriadne:Distributionassociatedwiththedataset,thoughitdoesnot includeanOAI-PMHrepositoryoranRSSfeedandisnotstrictlyawebservice.

Recommendation[R5]:

• Expandtheuseofpop-upelementdescriptionstoallelementsintheinputforms.

Figure3:RegistryDatasetinputform.

ARIADNED12.4

21

4.1.3 Add Dataset

Somequestionswereraisedbythewebformfordatasetandareapplicabletootherresources.Theseinclude:

• Temporal,subjectandothers:additionalelementscanbeaddedbutnotremoved,thoughextraelementsaddedinerrorareremovedwhenthepageisrefreshedonsave.

• Thedropdownondct:publisher isdauntingly largeanddoesnot alwaysdisplayon first click.Exposingthefull listofagentstoalluserspresentsthepossibilitythatitemscanbeincorrectlyattributed, intentionally or unintentionally. An auto-completemay be helpful: itmay not beimmediately clear to users that typing will bring them to matches in the existing list. Someguidance, policy or control on the recording of names in foaf:agent may be helpful to thetransparencyandaccessibilityofthesystem.

• If theuser has not added an agent on first login, this stepmustbe completedbefore addinginformationtodct:publisher,creatorandowner. Iftheagentstepiscompletedwhileaddingaresource, the usermustwait for the system to update before the agent is available to otherrelevant fields. Information inother fieldsof theweb formwas lostas the system logged theuserouttocompletetheupdate.Theagentwasavailabletoallfieldsonthenextlogin.

• In the dcat:keyword and dct:subject fields, users may be confused by the presence of twodifferentfieldsforwhatappeartobeverysimilarpurposes.TheRegistryFAQprovidesguidanceontheapplicationof thedifferentaccess fields; similarguidance forsubjectelementsmaybehelpful.


• Implement an auto-complete function on the dct:publisher element as an alternative toexposingthefulllistofagentstoallusers.

• StandardisetherecordinganddisplayofpersonalandorganisationalnameswithintheRegistry.• Eliminate the potential to circumvent adding an agent before adding metadata on a data

resource.• ExpandguidanceontheuseofelementscurrentlyavailableintheRegistrytoincludeguidance

ontheuseofthedifferentfieldswhichrelatetosubjects.

ARIADNED12.4

22

4.1.4 Adding temporal information to a resource

Thereweresomeunexpectedbehaviourswhenaddingtemporalinformationtoagivenresource.Figure4belowshowstemporalinformationaddedtotheappropriateinputform.Figure5showsthedisplayofthatinformationafterclickingtheSavebuttonontheinputform.Asimilarerroroccurredwithanotherresourcewhichhadasmallerspecificdaterange.Thereisnoerrormessagetoindicatetotheuserthatinappropriatevalueshavebeenentered,orthatrequiredvaluesaremissing.

Figure4:Inputtingtemporalinformation.

Figure5:TemporalinformationfromFigure4aftersaving.

Figure6:Aseconderrorontemporalinformation.

ARIADNED12.4

23


• Indicatemandatoryelementsintheinputformfortemporalinformation.• Provideafailwarningforinappropriateormissingvalues.

4.1.5 Adding Data Format to a Dataset

AsthetestdatasetwascomprisedofmetadatastructuredaccordingtoCARARE,theAssociationsareaofthewebformpresentedsomequestions.TheCARAREschemawasassociatedwiththerecordthrough:hasRecordStructure by adding CARARE as a Data Format resource. However, the schema could alsohavebeenaddedasaMetadataSchema.

Recommendation[R12]:

• Include appropriate examples of the use of the Associations area in the different resourceclassesinuserguidance.

Figure7:RegistryDataFormatinputform.

ARIADNED12.4

24

4.1.6 Add Vocabulary

TestingtheadditionofavocabularytotheCatalogueraisedthefollowingissues:

:status: This is currently a free text field, a drop down might be helpful. It is not clear to the userwhether the expected information is related to the publication status (i.e. a public or projectvocabulary),whetherthevocabularyisactivelymaintainedorupdated,indraftorsomeothervalue.

TheACDMsuggests someof theseelementsarestrongly recommended: itmaybeuseful tohighlightstronglyrecommendedelementstotheuserinadditiontothemandatoryelements.

It isalsounclearwhatvaluesareexpected in :hasVersion.TheRegistrydoesnotprovideapop-outtosupplythevaluesdocumentedforthisclassintheACDMv2.6.

Figure8:RegistryVocabularyinputform.


• Updatethe:hasVersionelementtoincludeapop-outwhichreflectsthevaluesexpectedintheACDMv2.6.

ARIADNED12.4

25

4.1.7 Add Mapping

Sourceandtargetfieldsaremandatoryandusedrop-downlists:schemasmustbeaddedasMetadataSchemaresourcesbeforeaddingamapping.Anyschemaadded to theCatalogue isavailable in thesedrop-downlistsintheRegistry.

Figure9:Addingamappingbetweenmetadataschemas.


• Considernavigationalchangeswhichreflecttherequiredworkflowofaddingmetadataschemasbeforeaddingamapping.

4.1.8 Add Distribution

ADistributionwasaddedforthe3DIconsIrelandproject.Thereareonlythreemandatoryfields,dct:title,dct:issuedanddct:modified.Therewasnovaluefordct:modifiedbuttheresourceaddedwithoutindicatinganerror.AwebaddresswasaddedtoDcat:accessURLandtheorganisationnametodct:publisher.


• HighlightinuserguidancethattheDistributionclassismandatory.• Introduceafailwarningorcompletenessindicatorwheremandatoryelementsaremissing.

ARIADNED12.4

26

4.1.9 Add Metadata Schema

ThetestschemawasMARCXML.ThewebformforMetadataSchemacomprisesmanyfields,andthoughnotmanyaremandatory,whenaddingamappingthismaybeadeterrentforusers:theymustrepeatthesestepstwicebeforeturningtotherelevanttask.The‘managemappingsforthisschema’buttonontheMetadataSchemacanbeused,butbothsourceandtargetschemasmustbepresent.

Figure10:RegistryMetadataSchemainputform.


• SeeAddMapping(25)above.

4.1.10 Add Digital Object Description

Fortheelementdct:format, thepop-upspecifiestheuseof IANAMIMEtypes,whichsomeusersmaynotbe familiarwithandpossibly shouldbeexplained.TheACDMV5.5specifiesanauto-complete forthisfield,whichwillbehelpfulwhenimplemented.

ARIADNED12.4

27

Within :identifierType, the pop-up suggests DOI and NBN as values. A drop down list may be moreappropriateifthedesignrequiresspecificvalues(thisisnotspecifiedintheACDM).

Figure11:AddingaDigitalObjectDescriptiontotheRegistry.


• Implement an auto-complete operation with values from IANA’s MIME Media Types fordct:format.

• Implementadrop-downon:identifierTypewithacceptablevaluesforthiselement.

ARIADNED12.4

28

4.1.11 Add Service

Example1:OnlineWebresourceMappingDeath,databaseserviceofinhumationsandcremations.

MappingDeath,according to theACDM latest versionand theDataResourcesUserGuide, shouldbeaddedasaServiceforHumans.BecausetheRegistrydoesnotreflectthisaspectoftheACDMit’snotpossibletospecifythisclasswhenaddingtheresourcetotheRegistry.

Example1:OnlineWebresourceWODANdatabaseserviceofpalaeo-environmentalscientificdata.

Similarly,WODANshouldbeaddedasanInstitutionalServiceasitrequiresalogintoaccessitsdata.ItisnotpossibletospecifythisintheRegistry.

According to the guidance, these services, which are built on databases should be added as singleentriesintheRegistry,anddisplayedassuchintheportal.InthecaseofMappingDeath,itispossibletoprovide spatial metadata and unique landing pages which represent entries in the database. AsTextualDocument is the only ACDM class, which provides for item level descriptions, these cannotcurrentlybeprovidedtothecatalogue.

Recommendations[R19]:

• AllowuserstospecifywhichoftheACDMServicetypes(describedinACDMv2.6)theirServicedataresourcerepresents.

4.1.12 Add Licence

ACreativeCommons4.0licencewasaddedtotheRegistry.Thenamefieldistheonlymandatoryone.DistributionistheonlyresourcetowhichtheLicenceclassbecomesavailablewhenadded.WhiletheportalmayrequireLicenceasaclass,itmaybefrustratingfortheRegistryuserthatLicencecannotbeaddedfromwithintheDistributionwebformas,forexample,withfoaf:agentinCollection.


• EnabletheadditionofaninstanceoftheLicenceclassfromwithintheDistributionclass,throughapop-outorotherwise.

4.1.13 Add GIS

The WMS GetCapabilities operation for Ireland’s sites and monuments inventory was added fromIreland’sgovernmentOpenDataportal.Aswithotherclassesof resource in theRegistry, there isnotenoughguidance in the input form forusersonhoweachelement,oreven themandatoryelementsshouldbefilled:pop-upsarepresentforsomeofthem,andthesecouldbeusedmoreeffectively.

ARIADNED12.4

29

TheshapefilefortheGISwaslateraddedtotheRegistryentry.Itisveryeasytoaddaresourcewithoutanyattacheddocumentationor landingpages,resultinginaveryscantyentryintheportal.Validationservicesneedtoaddresstheinclusionofmandatoryandrecommendedelements,andsomeimmediatefeedbacktotheuseroncompliancewiththerequirementsoftheACDMinrelationtotheclasstheyareworkinginisexpected,giventhelevelofspecificityintheACDM.


• Includeanexamplevalueintheelementguidancepop-upsorlinktoguidanceontheinputformpage.

• Include failwarnings or completeness indicator formandatory and/or strongly recommendedelements.

ARIADNED12.4

30

Figure12:AddingaGIStotheRegistry.

ARIADNED12.4

31

4.1.14 Add Collection

Leo Swan Aerial Archaeological Photography Collection and Discovery Programme Image CollectionwereaddedasCollections.

From a depositor perspective, it’s difficult to determine what is expected in this resource. The DataResourcesuserguidespecifiesthatonlytextualdocumentsshouldbeaddedasitemsincollections,andassociatedwiththeparentcollection(descriptionof)usingdct:isPartOf.WithintheRegistry,thelandingpageforthecollectionasawholeisincluded.Forthiscontentitisalsopossibletoprovidelandingpagesforalloftheindividualimagesinthecollection,withthepotentialtoincludethumbnails.

Figure13:AddingaCollectiontotheRegistry.

ARIADNED12.4

32


• Indicatetouserswhereobjectswhichcanbeusedtogeneratethumbnailsforitemswithinthecollectionshouldbeprovided.

• Includeadescriptivepop-upforthe:hasAttachedDocumentselement.

4.1.15 Other Registry features

Excel/XMLIngest

Currentlythere isnouser interfacewithintheRegistryforuploadingExcelorxmlfilesandnothingonthepageswherethetemplatesareprovidedto indicatetousers thata fileuploadservice isavailablewithinMORe.FromtheRegistryuserscanonlyseethewebformandtheAPI. Inthiscase it iscrucialthatusersarewellinformedabouttheworkflowavailableforcontentprovision,eitherfromnoteswiththetemplatesorthroughtheSupportPortal.

Recommendations[25-26]:

• ExpandnotesonthisresourcestoexplaintousersthatfileuploadisavailablewithinMORe.• Consider a content provision workflow diagram which shows the path through the different

partsoftheinfrastructure.

Exceltemplaterecord

The ACDM Excel templatewas testedwith a collection of archaeological grey literature reportswithassociatedmetadatainanexistingExcelspreadsheet.Asthereportsarenotavailableontheweb,themetadata is added as a dataset. Each row in the spreadsheet contains themetadata record for onereport.AsthereportmetadataismarkedupinDublinCore,followingtheARIADNEtemplatedocumentis relatively straightforward. Some users may require guidance or support to map from existingmetadata in other standards to the template. Expanding the examples available for the differentresourceclasseswouldfacilitatethis.

Recommendations[27]:

• Includefurtherworkedexamplesoftheuseofthetemplatefordifferentresourceclasses.

ResourceclassesontheRegistryhomepage

ThereareanumberofresourceclassesthatarenotvisibleontheinterfaceonloggingintotheRegistry.TheresourceclassesthatareavailableinRegistry,fromthehomepageorfromthe‘Objects’dropdown,do not reflect the current content of the ACDM. The ‘Objects’ drop-down could also be renamed toreflectthedescriptionsofresourceclassesintheACDM:dataresources,languageresources,services.

ARIADNED12.4

33

Recommendations[28-29]:

• Renamethe‘Objects’drop-downtoreflectthelanguageoftheACDM.• EnsurenodataresourcesclassesarehiddenfromtheuserbythevisualstructureoftheRegistry

interface.

Usermanagement

Considerationshouldbegiventomanagementofuseraccounts intheRegistry. It iscurrentlypossiblefor several staff members of one organisation to register, login and add resources to the Registry,without any visibility or oversight of that content at the organisational level. Thus it is possible, forexample,forasingleorganisationtobeaddedinfoaf:agentmultipletimesbydifferentusers.Thereareseveral classes of resourcewhere this duplicationmayoccur. It is unclearwhether this duplication isresolvedwithintheRegistryorCatalogue.Implementinganorganisationalaccountwhichhasoversightandroleassignmentformemberusersisafurtheropportunityforqualitycontrol.


• ConsiderimplementingorganisationalleveluseraccountsintheRegistry.

4.2 Conclusions and Recommendations

The relationshipbetweenuser guidance, theACDMand theRegistry shouldbe strong. Currently, theguidance, while reflecting the ACDMwell and describing useful workflows, serves to confuse, as thestructureswithin theRegistry donot reflect the content of eitherARIADNECatalogue: EnteringDataResourcesorthelatestversionoftheACDMSpecification.Forsomeclassestherearealargenumberofinput fields, and the formmaybenefit frommore visual prioritisation of themandatory and stronglyrecommendedelements.ThisisparticularlyrelevantforelementswhichprovideaccesstotheresourcesthroughURLs:withintheRegistryinterface,itisnotobviousthatDistributionisarequiredclass.

Pop-upsassociatedwithindividualelementsareuseful,butcouldbeoptimisedtoprovidemorehelpfulguidancetousers,perhapswithlinkstoexpandedguidanceandexamples.WorkingwithintheRegistrycanbeafrustratingexperience,withvaryingfeedbacktotheuseronwhethertheirentrieswillcomplywith the standard requiredandvalidateagainst theACDM.Somewarningsareprovidedand inothercasestheuserisunabletosavetherecord.Apreviewofhowtherecord/entrywilllookintheARIADNEPortalmayprovidesomeencouragementtoproviders to improvethequalityorquantityofmetadatatheyprovideforaparticularresource.

AstheRegistryisthefirstpointofcontactforcontentprovisionforARIADNE,itsdesignshouldcloselyreflectcontentprovisionworkflow.

ARIADNED12.4

34

RecommendationsfortheARIADNERegistry

R1 4.1.1 Includetheadditionofaninstanceoffoaf:agentaspartoftheregistrationprocess,oraspartofnavigationduringfirstadditionofadataresource.

R2 4.1.1 Include page navigation or pop-up which directs users to guidance for contentprovisiononfirstonetofivelogins.

R3 4.1.1 One sentence descriptions of each data resource where the user chooses whichresourceclassissuitableforhis/hercontent.

R4 4.1.1 Include a basic visualisation of the relationships between data resources andlanguage resources within user guidance, including highlighting of mandatorylanguageclassesfordataresources

R5 4.1.2 Expandtheuseofpop-upelementdescriptionstoallelementsintheinputforms.

R6 4.1.3 Implementanauto-completefunctiononthedct:publisherelementasanalternativetoexposingthefulllistofagentstoallusers.

R7 4.1.3 Standardise the recording and display of personal and organisational nameswithintheRegistry.

R8 4.1.3 Eliminatethepotentialtocircumventaddinganagentbeforeaddingmetadataonadataresource.

R9 4.1.3 ExpandguidanceontheuseofelementscurrentlyavailableintheRegistrytoincludeguidanceontheuseofthedifferentfieldswhichrelatetosubjects.

R10 4.1.4 Indicatemandatoryelementsintheinputformfortemporalinformation.

R11 4.1.4 Provideafailwarningforinappropriateormissingvalues.

R12 4.1.5 Include appropriate examples of the use of the Associations area in the differentresourceclassesinuserguidance.

R13 4.1.6 Update the :hasVersion element to include a pop-out which reflects the valuesexpectedintheACDMv2.6.

R14 4.1.7 Consider navigational changes which reflect the required workflow of addingmetadataschemasbeforeaddingamapping.

ARIADNED12.4

35

R15 4.1.8 HighlightinuserguidancethattheDistributionclassismandatory.

R16 4.1.8 Introduce a failwarning or completeness indicatorwheremandatory elements aremissing.

R17 4.1.10 Implementanauto-completeoperationwithvaluesfromIANA’sMIMEMediaTypesfordct:format.

R18 4.1.10 Implementadrop-downon:identifierTypewithacceptablevaluesforthiselement.

R19 4.1.11 Allow users to specifywhich of the ACDM Service types (described in ACDM v2.6)theirServicedataresourcerepresents.

R20 4.1.12 Enable theadditionofan instanceof theLicenceclass fromwithin theDistributionclass,throughapop-outorotherwise.

R21 4.1.13 Includeanexamplevalueintheelementguidancepop-upsorlinktoguidanceontheinputformpage.

R22 4.1.13 Include fail warnings or completeness indicator for mandatory and/or stronglyrecommendedelements.

R23 4.1.14 Indicatetouserswhereobjectswhichcanbeusedtogeneratethumbnailsforitemswithinthecollectionshouldbeprovided.

R24 4.1.14 Includeadescriptivepop-upforthe:hasAttachedDocumentselement.

R25 4.1.15 ExpandnotesonthisresourcestoexplaintousersthatfileuploadisavailablewithinMORe.

R26 4.1.15 Consider a content provisionworkflow diagramwhich shows the path through thedifferentpartsoftheinfrastructure.

R27 4.1.15 Include furtherworked examples of the use of the template for different resourceclasses.

R28 4.1.15 Renamethe‘Objects’drop-downtoreflectthelanguageoftheACDM.

R29 4.1.15 EnsurenodataresourcesclassesarehiddenfromtheuserbythevisualstructureoftheRegistryinterface.

R30 4.1.15 ConsiderimplementingorganisationalleveluseraccountsintheRegistry.

Table2:RegistryRecommendations

ARIADNED12.4

36

5 Aggregation Service, Validation Services, Metadata Enrichment Services: the MORe aggregation tool

TheMOReaggregationworkflowhasbeenproventhroughexperience inLoCloudandotherEuropeanprojects.DocumentationforuseofthetoolwithintheARIADNEinfrastructureisnotavailablefromtheSupportportalorwithinMORe.

It is unclearhow theValidationService is validating content against theACDMbasedon the recordsavailableintheprototypeportal:therearedifferentapproachestoitemandcollectionlevelmetadatarepresented. The ARIADNE Catalogue: Entering Data Resources, a short user guide and guidancereceived during content provision suggests that the only class of resource utilising item leveldescriptionswithintheCollectionclass isTextualDocument,whose instancesareassociatedwiththeirparent collection by dct:isPartOf. There are resources within the prototype portal which reflect thisrelationshipwhicharenotcomposedofTextualDocuments.Clearguidancefor(meta)datadepositorsonARIADNE’s expectations and the ACDM specifications on the appropriateness of providing item leveldescriptionswillshapeexpectationsforhowcontentappearsintheportal.

Within theMOReweb tool the content provision workflow is strong: the user is guided by the toolthroughthestepstowardspublicationtotheportal.

Metadata enrichment services are also similar to those experienced in other projects, with theexceptionof theperio.domappingservice.Testing inTask12.6shouldbecarriedout incollaborationwithpartnerswhohavenotusedthetoolsandservicesavailablethroughtheLoCloud,CARAREand3D-Iconsprojectsinthepastasthismayinfluencetheresultsofthetrueuserexperienceastheywillhavegainedprevioususerexperiencefromtheseprojects.The Registry web input tool was designed for ‘Users without any content in an existing format andavailable through a repository [so that they] can use the registry service to catalogue content fromscratch,manuallyorthroughtheRESTAPI’(D12.3,21).WiththeavailabilityofafileuploaddirectlytoMORe, and spreadsheet and xml templates within the Registry, content providers have a variety ofoptions for supplying metadata. In this context, particular attention could be paid to ensuring thatmanualentryworkflowintheRegistryissuitableforthosewhowilluseit.ForthosewithoutcontentinanexistingformatwhoareusingtheRegistryasacataloguingtool,ARIADNE’sintegrationofmetadataandpositiononuploadingofcontenttotheinfrastructureshouldbemadeclear.ThelevelsofusersupportrequiredformaintainingthequalityofthecontentinputintoARIADNEshouldbeconsidered.Stronguserguidancedocumentation,inavarietyofformats,wouldprovideameansofaddressingthisneedonanongoingbasis.


• Documentation for the use of MORe should be available within the Support Portal andaccessiblefromwithinMORe.

ARIADNED12.4

37

• Include worked examples of provision of the Collection class in user guidance, includingmetadataprovisionfortheitemsordataresourcesofwhichthecollectioniscomposed,wouldillustrateforusershowtheircontentwillberepresentedintheportal.

• FurthertestingshouldbecarriedoutwithapanelofuserswhodonothavepreviousexperienceofMOReandassociatedtools.

• ManualentryworkflowintheRegistryshouldbeharmonisedwithuserguidanceandthelatestversionoftheACDM.

ARIADNED12.4

38

6 Support Portal and Documentation

The Support portal, documentation and user guidance need to be approachedholistically in order toprovide clear and coherent guidance to a variety of users at different points of interaction with theinfrastructure.

The documents listed under Mapping Guidelines in the Support Portal are the ACDM specificationsrather thanaguide tousersonhowtomaptheircontent to theACDM.Examples listed in the tableswhichoutline the requirements foreach resourcewithinthemodelarehelpful,howeverbringing theACDM and the short user guideARIADNE Catalogue: Entering Data Resources together into a set ofguidelineswhichexplaintheworkflow,thestructureofACDMrecordsandalsoexpandontheexpectedvalueswouldprovideavaluableresourcetousers.Examplesforeachclassofresourcewithinthemodelwouldhelpuserstounderstandtherelationshipsbetweendataresourcesandlanguageresourcesmoreclearly.

AstepbystepprocessdescriptionforusingtheRegistryisavailabletoguidetheuserthroughthetool,the60slideARIADNERegistryToolManualavailablefromtheWebtoolareaoftheHelpsectionwithintheRegistry.ThemanualexplainshowtoenterresourcesintheRegistrybutdoesnotguideusersonthekind of content expected in the given classes. For example, under Import the Collection (10), themanual describes adding an association, :hasItemMetadataStructure, to the entry for a collection,withoutreferencingthetypeofcontentexpectedinthisassociation,orreferringtheusertowheretofind that information. It isalsonotclearwhether theassociation is requiredoroptional.TheRegistryFAQ,alsowithinitsHelpsection,hasusefulrelevantcontentandcouldbeexpanded.

Inaddition,someresourcesorelementshavedependencieswhicharesomewhathiddenfromtheuserexperienceofthewebformswithintheRegistryandarenotintuitive.Forexample,therequirementtoadd an agent before adding a resource needs to be highlighted. Given that the initial creation of anagent ismandatory, this feature should be presented to the user on first login – users currently cancircumventthisrequirementandbegintoaddresource,aprocesswhichfailswheretherearenoagentsavailableandthenreturnstheusertotheagentclass.

Correct workflows at the time of ingest will have an impact on all of the integration activities; forexample,thereislittleguidancecurrentlyavailabletousersformappingperiodterms,andnoguidancefor this operation available fromMORe,where the Perio.domapping enrichment service is available.D2.1foundthat‘workeffortfordepositingdataintherequiredformat’wasthesecondmostcommonbarrier for researchers to deposit their research data (106). Availability and visibility of clear andcomprehensive support documentation would also address concerns mentioned in D2.1 around theworkeffortforprovidingmetadataintherequiredformat.

ARIADNED12.4

39

ARIADNE’sSupportPortalshouldholdallofthedocumentationrelevanttotheuseoftheinfrastructureanditscomponents,organizedtoreflectusers’interactionwiththeinfrastructure,frombasicguidanceonusingtheARIDANEPortal throughtotheuseofAPIs forcontentprovisionand investigationoftheCatalogueandallFAQsrelevanttoARIADNE.


• Userguidanceshouldincludeexampleofalldataresourcesclassesworkedwiththeirlanguageresourceassociations.

• ExpandtheRegistryFAQ.• Changenavigationaroundadding an instanceof foaf:agent fromwithin adata resource. (See

recommendationunder‘AddDataset’(20)above).• Comprehensive step-by stepworkflow andmapping guidance could be provided both in one

resourceandbrokenintopartswhichreflectvarioususerinteractionswiththeinfrastructure.

ARIADNED12.4

40

7 Strategy for further testing

Following the adjustment and alteration of the different services and tools based upon the series ofrecommendations outlined in this report, feedback will be gathered from the other data providerswithintheprojecttogaugetheirexperiencesduringtheproject.

SurveyInstrument

The feedback from the wider ARIADNE user group will be carried out using online survey tool(surveymonkey.com)acrossaperiodofonemonth(May,2016)andcanbecompletedbyparticipantsinarelativelyshorttimeperiod(10–15minutes).Thisonlineusersatisfactionsurveywillbedevelopedbaseduponthestructureofthisreportandadvanceadditionalunderstandingofthedesignedservicesandtoolsbaseduponthefollowingcriteria:

InitialARIADNEInfrastructuretoUserRequirements

• RatingofthehoweachdifferentARIADNEservicesandtoolsresolvetheissuesandchallengesoutlinedintheinitialtheARIADNEInfrastructuretoUserRequirements

UserDesignInteractionSatisfaction

• Verifyconsistencyacrossfamilyofinterfaces• Checkterminology,fonts,color,layout,i/oformats• Assessmentofdesignacrosswebbrowseranddevices

ExperienceandassessmentofRegistrytool

• Eachspecificservice(addresource,adddatasetetc..)willbeassessedbaseduponeaseofuseandevaluationoftheexpectedresults

• UtilisingtheSystemUsabilityScale(SUS)theregistryservicewillbegenerallyassessed

DocumentationofPortalandTools

• Overallsatisfactionwithguidance• Identificationofadditionalgapsormisdirectionwithinexistingdocumentation• Assessment of documentation based upon potential users within the wider archaeological

community

TechnicalSupportFunctionality

• Responsivenessofsupport

ARIADNED12.4

41

• Resolution(quality&timeliness)• Overallsatisfactionwithsupport

8 Conclusions and Recommendations

TheinfrastructureimplementedinWP12hasmetmanyoftheuserequirementsspecified.Someaspectsnotyetvisiblewill requirefurthertesting inTask12.6. SomeclarificationofuserequirementsforthePreviewServicemaybenecessary:D12.2designs a service thatpreviews search results, as describedaboveandillustratedintheprototypeportal,asalist,onamapandtimeline(D12.2,p24)butwhichcanalsopreview individual records.D12.3has implementedaPreviewService throughwhich researcherscanpreviewtheirowndatasetsinanumberofformats,whichseemstobemorecloselyalignedwiththeRegistry (p17).D2.2 (p108)andD13.2 (p30-32)bothrefer tothehighprioritygiventothis feature forquicklyassessingrelevancebyusers.

The Support portal, documentation and user guidance need to be approachedholistically in order toprovide clear and coherent guidance to a variety of users at different points of interaction with theinfrastructure.Depositor userswill bemost affected by the quality and availability of documentationandsupport.DocumentationfortheMORetoolandenrichmentserviceswouldbehelpfuladditionstotheSupportPortal.

TheRegistryinputtoolprovidesthenecessaryfunctionalitytoenabledepositingofmetadata.Theuserexperiencecouldbe improvedandmorecloselyguidedwith changes indesign.ThereareveryusefulfeaturesforguidancewithintheinputformsintheRegistry;optimizingthesecouldpositivelyimpacttheboththequalityofmetadataprovisionandtheuserexperience.ExpansionoftheFAQavailablewithintheRegistry,andtheintegrationofalldocumentationintotheSupportPortalisalsorecommended.

Recommendations 3 12.1RequirementsR31 3.1.1

Resolvetheuseoflanguagearoundtheterms‘Registry’and‘Catalogue’inanysupportdocumentationanduserinterfaces.

R32 3.1.1

ClarificationoftheuserequirementsforthePreviewService.

R33 3.1.2

Appropriate,targetedguidancefortheuserintheuseoftheRegistrytoadddataresourcesisrequired.

R34 3.1.2 Abusinessandsustainabilitymodelisrequired.R35 3.1.3 Guidanceforusersonthenatureoftheerrorsthrownduringthe

depositandingestprocesswouldbehelpful.R36 3.1.3 Awordcloudofthe‘derivedsubject’facetorGettyAATterms,

eitherasafilterorasecondwordcloudinthe‘What’browsingarea.

R37 3.1.4 Theprojectshouldcommunicateclearlytousersitsapproachto

ARIADNED12.4

42

dataandmetadata.R38 3.1.5 ThesourcevocabulariesavailablethroughtheVocabularymatching

toolcouldbeexpandedtoallowbroadermappingtoAAT.R39 3.1.5 Guidancedocumentationonhowtopreparevocabulariesfor

inclusioninthetoolandformappingwouldberequired.R40 3.2.1 Documentationisrequiredfortheperio.doenrichmentservice.

R41 3.2.5 Clarify,fromD12.1andD12.2,whatkindofintegrationandinteroperabilityissoughtforscientificdatasets.

4 Registry

R1 4.1.1 Include the addition of an instance of foaf:agent as part of theregistrationprocess,oraspartofnavigationduringfirstadditionofadataresource.

R2 4.1.1 Includepagenavigationorpop-upwhichdirectsuserstoguidanceforcontentprovisiononfirstonetofivelogins.

R3 4.1.1 One sentence descriptions of each data resource where the userchooseswhichresourceclassissuitableforhis/hercontent.

R4 4.1.1 Include a basic visualisation of the relationships between dataresources and language resources within user guidance, includinghighlightingofmandatorylanguageclassesfordataresources

R5 4.1.2 Expand the use of pop-up element descriptions to all elements intheinputforms.

R6 4.1.3 Implementanauto-completefunctiononthedct:publisherelementasanalternativetoexposingthefulllistofagentstoallusers.

R7 4.1.3 Standardise the recording and display of personal andorganisationalnameswithintheRegistry.

R8 4.1.3 Eliminate the potential to circumvent adding an agent beforeaddingmetadataonadataresource.

R9 4.1.3 Expandguidanceontheuseofelementscurrentlyavailable in theRegistrytoincludeguidanceontheuseofthedifferentfieldswhichrelatetosubjects.

R10 4.1.4 Indicate mandatory elements in the input form for temporalinformation.

R11 4.1.4 Provideafailwarningforinappropriateormissingvalues.

ARIADNED12.4

43

R12 4.1.5 IncludeappropriateexamplesoftheuseoftheAssociationsareainthedifferentresourceclassesinuserguidance.

R13 4.1.6 Updatethe:hasVersionelementtoincludeapop-outwhichreflectsthevaluesexpectedintheACDMv2.6.

R14 4.1.7 Considernavigationalchangeswhichreflecttherequiredworkflowofaddingmetadataschemasbeforeaddingamapping.

R15 4.1.8 HighlightinuserguidancethattheDistributionclassismandatory.

R16 4.1.8 Introduce a fail warning or completeness indicator wheremandatoryelementsaremissing.

R17 4.1.10 Implement an auto-complete operation with values from IANA’sMIMEMediaTypesfordct:format.

R18 4.1.10 Implement a drop-downon :identifierTypewith acceptable valuesforthiselement.

R19 4.1.11 AllowuserstospecifywhichoftheACDMServicetypes(describedinACDMv2.6)theirServicedataresourcerepresents.

R20 4.1.12 EnabletheadditionofaninstanceoftheLicenceclassfromwithintheDistributionclass,throughapop-outorotherwise.

R21 4.1.13 Includeanexamplevalue in theelementguidancepop-upsor linktoguidanceontheinputformpage.

R22 4.1.13 Include fail warnings or completeness indicator for mandatoryand/orstronglyrecommendedelements.

R23 4.1.14 Indicate to users where objects which can be used to generatethumbnailsforitemswithinthecollectionshouldbeprovided.

R24 4.1.14 Include a descriptive pop-up for the :hasAttachedDocumentselement.

R25 4.1.15 ExpandnotesonthisresourcestoexplaintousersthatfileuploadisavailablewithinMORe.

R26 4.1.15 Consider a content provision workflow diagram which shows thepaththroughthedifferentpartsoftheinfrastructure.

R27 4.1.15 Include further worked examples of the use of the template fordifferentresourceclasses.

ARIADNED12.4

44

R28 4.1.15 Rename the ‘Objects’ drop-down to reflect the language of theACDM.

R29 4.1.15 Ensurenodata resources classesarehidden from theuserby thevisualstructureoftheRegistryinterface.

R30 4.1.15 Consider implementing organisational level user accounts in theRegistry.

5 AggregationservicesR42 DocumentationfortheuseofMOReshouldbeavailablewithinthe

SupportPortalandaccessiblefromwithinMORe.R43 IncludeworkedexamplesofprovisionoftheCollectionclassinuser

guidance,includingmetadataprovisionfortheitemsordataresourcesofwhichthecollectioniscomposed,wouldillustrateforusershowtheircontentwillberepresentedintheportal.

R44 FurthertestingshouldbecarriedoutwithapanelofuserwhodonothavepreviousexperienceofMOReandassociatedtools.

R45 ManualentryworkflowintheRegistryshouldbeharmonisedwithuserguidanceandthelatestversionoftheACDM.

6 SupportPortalR46 Userguidanceshouldincludeexampleofalldataresourcesclasses

workedwiththeirlanguageresourceassociations.R47 ExpandtheRegistryFAQ.R48 Changenavigationaroundaddinganinstanceoffoaf:agentfrom

withinadataresource.(Seerecommendationunder‘AddDataset’4.1.3above).

R49 Comprehensivestep-bystepworkflowandmappingguidancecouldbeprovidedbothinoneresourceandbrokenintopartswhichreflectvarioususerinteractionswiththeinfrastructure.

Table3:Recommendationsfortheinfrastructure

ARIADNED12.4

45

9 References

Bhreathnach,E.,O’Brien,E.,MappingDeath1st-8thCenturiesAD:People,BoundariesandTerritoriesinIreland,2010,http://www.mappingdeathdb.ie/

Gavrillis, D., Papatheodorou, C., Canstantopoulos, P., D12.2: Infrastructure Design, February 2015,http://www.ariadne-infrastructure.eu/Resources/D12.2-Infrastructure-Design

Gavrillis, D., Papatheodorou, C., Afiontzi, E., Makri, D.N., Dallas, C., D12.3: Initial InfrastructureImplementation Report, June 2015, http://www.ariadne-infrastructure.eu/Resources/D12.3-Initial-Infrastructure-Implementation-ReportHollander,H.,Hoogerwerf,M.,D13.1:ServiceDesign,December2014,http://www.ariadne-infrastructure.eu/Resources/D13.1-Service-DesignRichards,J.,Makri,D.N.,ARIADNECatalogue:EnteringDataResources,AshortUserguide,September2015.

Selhofer, H., Geser, G., D2.1: First Report on Users’ Needs, April 2014, http://www.ariadne-infrastructure.eu/Resources/D2.1-First-report-on-users-needs

Selhofer, H., Geser, G., D2.2: Second Report on Users’ Needs, February 2015, http://www.ariadne-infrastructure.eu/content/view/full/1188

Stuijts,I.,O’Donnell,L.,Bunce,A.,McAuley,J.,Corns,A.,WODANArchaeologicalWood&CharcoalDatabase,2010,http://www.wodancharcoal.ie/

TheARIADNERegistryTool,

http://ariadne-registry.dcu.gr/manual/The%20ARIADNE%20Registry%20tool_manual.pdfWright,H.,Fernie,K.,Geser,G.,D12.1:UseRequirements,July2014,http://www.ariadne-infrastructure.eu/Resources/D12.1-Use-Requirements.

Data & Analytics

Ariadne: Initial Infrastructure Testing Report