Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

The Ariadne Project


Published on

Presentation by Franco Niccolucci, PIN

"Facing the future" workshop

Berlin, Germay
21-22 November 2013

Published in: Data & Analytics
  • Be the first to comment

  • Be the first to like this

The Ariadne Project

  1. 1. The ARIADNE project Advanced Research Infrastructure for Archaeological Data Networking in Europe Franco Niccolucci – PIN Project Coordinator Facing the future, Berlin 21-22 November 2013 ARIADNE is funded by the European Commission's Seventh Framework Programme
  2. 2. What is ARIADNE • ARIADNE is a EU-funded project aimed at integrating the European Research Infrastructures on archaeological datasets • Its overall goal is to overcome the fragmentation of archaeological data repositories and to foster a culture of archaeological data sharing and re-using • Start date: 1st February 2013 •
  3. 3. The ARIADNE partnership • Coordination – PIN – UoY-ADS • 24 partners • 17 countries
  4. 4. ARIADNE focus • ARIADNE is focused on archaeology and, in general, on tangible heritage • Its disciplinary scope has very specific methods and needs for integraGon: it deals with ‘things’ • There are common interests with digital humaniGes (texts) and history, so we are collaboraGng with DARIAH on content, methods and tools • Very important overlap with conservaGon and restoraGon, so we are establishing strong collaboraGons with projects in this domain
  5. 5. Project activities • Networking activities – Community building: involving researchers and institutions in sharing data and establishing together guidelines – Standardization and good practices • Trans-National Access – Training – Access to on-line resources • Research activities – Knowledge organization – Data management – New or improved tools to extract information – Advances in methodology
  6. 6. Progress in the iniGal nine months Networking • Set up users’ needs survey and SIGs • Collected detailed informaGon on partners’ datasets TNA • Outlined the training program for 2014 – Summer schools
  7. 7. Progress in the iniGal nine months Joint Research • Started the design of integraGon – Mapping metadata schemas to CIDOC-­‐CRM • Working on an extension of CIDOC-­‐CRM suitable for archaeological documentaGon – DraZ proposal for excavaGon data in preparaGon • CreaGon of the ACDM (ARIADNE Catalog Data Model)
  8. 8. Overview of partners’ datasets DBMS Structured data Collec0ons MM Sparse files GIS ZRC-­‐SAZU X X OEAW X X DISCOVERY X X X ARHEO X INRAP X X ARUP-­‐CAS X NIAM-­‐BAS X SND X X ADS X X X X X X DANS X X X X MIBAC-­‐ICCU X X X X MNM-­‐NOK X ATHENA RTC-­‐ CETI X AIAC X Cyi-­‐STARC X X DAI X • DBMS: RDBMS, MySQL, Access • Dataset: repository of digital objects with the same structure • Collec0on: set of text files/images stored in a hierarchical system • Mul0media: 3D, images, videos • Sparse files: mostly grey literature, no (common) schema • GIS: informaGon layers, coordinates Content includes: • ExcavaGon data • Monuments and sites • ScienGfic analyses
  9. 9. • 20 countries • 24 languages • 1,500,000+ database records • 40,000+ grey literature files ARIADNE in numbers 38% DBMS 20% Structured data (datasets) 9% CollecGons 9% MulGmedia 9% Sparse files 15% GIS 1 2 3 4 5 6 DBMS Structured data CollecGons MM Sparse files GIS
  10. 10. Metadata schemas Eight partners (SND, KNAW-­‐DANS, DISCOVERY, MiBAC-­‐ICCU, INRAP, ADS, CYI-­‐ STARC) have adopted formal metadata standards for their datasets. The metadata standards reported are: • DDI, DataCite, MARC/UNIMARC, TriDAS, Dublin Core applicaGon profiles, INSPIRE, ISO 11915, CARARE, LIDO, CIDOC-­‐CRM. Ten partners (ZRC SAZU, MiBAC-­‐ICCU, ADS, AIAC, MNM-­‐NOK, CYI-­‐STARC, ARUP-­‐CAS, ATHENA RC, NIAM-­‐BAS) have developed proprietary metadata schemas for some of their datasets. However, all these can be mapped onto CIDOC-­‐CRM. Four partners (DISCOVERY, INRAP, ARHEO, OAEW) reported some datasets for which a metadata definiGon is not currently available but could be derived from the database structure.
  11. 11. ARIADNE Users Framework Interoperability Framework Meta/data records => collect/transform2RDF SND Other… Data Centers (naGonal) Domain/Subject-­‐based Repositories & Portals (nat./InsGtuGonal Repositories / DBs Research Projects Domain/Subject-­‐based Referatories & Portals (nat./ARIADNE e-­‐Infrastructure and Integrated Services LOD cloud diagram, by R. Cyganiak & A. Jentzsch, hop://lod-­‐ ADS ARACHNE FasG Online … ARIADNE Registry Datasets, metadata schema, KOSs, mappings,…, CRM Several ARIADNE partners ARIADNE Portal Cross-­‐search and other applicaGons L4: infra & integrated services L3: Higher-­‐ level data managers L2: Ins6tu6ons, ins6tu6onal repositories/DBs L1: Projects, research groups … … Search, bro…w se, Legend: dep=deposit, coll=collect, acc=access; D= Data, M=Metadata collM eDNA Data Centers (nat./int., archaeology or general) Subject/Domain-­‐(nat./internaGonal) Subject/Domain-­‐(nat./internaGonal) ARIADNE Infrastructure and Integrated Services transform to/RDF accData Other Infra & Services ARIADNE aggregators (nat./ themaGc)? LLODD CClloouudd collM collM collM collM depD+M depD+M
  12. 12. The ACDM • The ARIADNE Catalog Data Model (ACDM) aims at describing datasets, services, and resources in the archaeological domain – So far it addresses databases, collecGons, thesauri, with plans for covering all relevant resource types • Based on DCAT (W3C recomm.) and other widespread ontologies • Data collected into a registry, using a data acquisiGon tool • To be used internally to support integraGon design • Conceived to became a publicly available service and to be offered/ extended to other domains (e.g. conservaGon/restoraGon)
  13. 13. ACDM Model dcat:Catalog The catalog of the ARIADNE datasets is an instance of this class 1 dcat:Dataset dcat:Distribution Represents an accessible form of a dataset as for example a downloadable file, an RSS feed or a web service that provides the data. 1 dcat:dataset * 1 dcat:distribution * :ARIADNEDistribution :numOfRecords :OAI-PMHServerURI: :platformDescription skos:Concept dcat:theme :ARIADNEDataset :accessPolicy An instance of this class represents an ARIADNE dataset, independent of any specific distribution of the dataset. A dataset is defined as a set of archaeological records having all the same structure ArchaeologicalRecordStr ucture :simpleOrComplex? :standardUsed: :proprietaryFormatDesc: :mappingTo: :characterSet :XSDAvailable? An instance of this class describes the structure of the archaeological records of the associated dataset :hasRecordStructure * 1 1 :usesVocabulary :usesVocabulary :hasAttachedObject * 1 :DigitalObject dct:Description dct:Format [MIME] dct:Identifier :IdentifierType :persistentIdentifier? An instance of this class describes a type of digital object An instance of this :hasMetadataStructure association captures the fact that the archaeological record of a dataset may have attached digital objects MetadataRecordStructure :standardUsed: :proprietaryFormatDesc: :mappingTo: :characterSet :XSDAvailable? Represents an accessible form of a dataset as for example a downloadable file, an RSS feed or a web service that provides the data. An instance of this class describes the structure of the metadata records of the associated dataset Vocabulary dct:description dct:identifier dct:format * 0 * * * * An instance of this class represents a vocabulary or authority file, used in the associated structure * :uri AttachedDocuments * 1 foaf:Agent Documents useful to understand the complexity of database made available to ARIADNE. Provides: 1) database schema, 2) sample of records for each database. * dct:publisher * dct:publisher * 1 :hasSimpleDigitalType * An instance of this association captures the fact that the archaeological record has a simple structure and every record is a digital object of the same type :ARIADNEService :applyTo * 0 This class is described in a separate figure
  14. 14. ARIADNE Required Services • Services for resource discovery • Services integraGng datasets on a geographic base, enabling access according to geographic criteria • Services integraGng datasets on a temporal base, enabling access according to temporal criteria and using a complex Gmeline • Services implemenGng interoperability among different datasets • Metadata management (semanGc repositories with advanced query and retrieval funcGonaliGes) • Repository infrastructures and ingesGon services • VisualizaGon services for – Images – Videos – 3D Single Objects & Large Scenes • Services will re-­‐use, as far as possible, concepts/tools created in other projects
  15. 15. Integrated Viewer-­‐Browser Tool • 3D-­‐COFORM IVB: Integrated viewer-­‐browser based on CIDOC-­‐CRM
  16. 16. Text AnnotaGon Tool
  17. 17. Mapping Tool (PIN, beta)
  18. 18. Mapping Archaeological Object E22 Man-made Object Inscription (ISR) E34 Inscription p128 carries "Olpe Chigi" Object Name (OGTN) Object Title (SGTT) E35 Title P102 has title Object "Position" E46 Section Definition P58 defines section Materials (MTC) E52 Material P45 consists of P43 has dimension Object Dimensions E54 Dimension [Open Vocabulary] "Foot" P1 is identified by OGTP E41 Appellation "Apollo del Belvedere" P90 has value MISA, MISL ... E60 Number Height Width Length P91 has unit MISU E58 Measurement Unit [Closed Vocabulary] P3 has note MISV E62 String Stamps, Badges, Emblemes E25 Mark p128 carries
  19. 19. Challenges • Languages – Most data are (and must remain) in their original languages • TradiGons – The way data are understood and captured are different according to schools and scienGfic tradiGons • FragmentaGon – There is a mulGtude of micro-­‐archives that contain valuable informaGon and are at risk of loss • Technology – Advances in the use of technology (e.g. 3D, scienGfic analyses) are creaGng ‘big data’ archives, not properly managed with the currently available tools • VirtualizaGon – Virtual tools need to be fully integrated in the research methodology of the discipline
  20. 20. ARIADNE is a project funded by the European Commission under the Community’s Seventh Framework Programme, contract no. FP7- INFRASTRUCTURES-2012-1-313193. The views and opinions expressed in this presentation are the sole responsibility of the authors and do not necessarily reflect the views of the European Commission. Contact: