ancient prosopographies
play

Ancient Prosopographies Gabriel Bodard K. Faith Lawrence (Kings - PowerPoint PPT Presentation

Standards for Networking Ancient Prosopographies Gabriel Bodard K. Faith Lawrence (Kings College London) Project history Bringing people together Prior art: Pelagios Data Model Creating SNAP URIs Technical Issues -


  1. Standards for Networking Ancient Prosopographies Gabriel Bodard K. Faith Lawrence (King’s College London)

  2. ● Project history ● Bringing people together ● Prior art: Pelagios ● Data Model ● Creating SNAP URIs ● Technical Issues - Storage ● Methodological Issues – Merging ● SNAP Online ● Into the future…

  3. Digital Classicist wiki

  4. LAWDI

  5. Bringing People Together ● King’s College London ○ Gabriel Bodard ○ Faith Lawrence ● Duke, Hugh Cayless (Papyri.info) ● Leuven, Mark Depauw (Trismegistos) ● Oxford, Sebastian Rahtz (LGPN) ● Southampton, Leif Isaksen (Pelagios)

  6. The ancient geography model

  7. The ancient geography model

  8. The ancient geography model

  9. The “Pleiades part” ● No single authority “Pleiades” for ancient people ● Not feasible to create brand new authority ● Linked Data doesn’t require single silo ● Many existing authorities LGPN, Trismegistos, PIR ○ ○ PBE/PBW, Smith, Hellenistic Babylonia, RIB, Syriac, Nomisma, Kerameikos Perseus Catalog, VIAF, BM persons, Zenon catalog ○ ● Get them into RDF ○ uris, properties, relationships co-references ○

  10. The “Pelagios part” 1. Enable and encourage linking to persons 2. Enable and encourage linking between datasets 3. Internal relationships: a. person:1234 snap:hasBond <xyz> . <xyz> rdf:type snap:DaughterOf ; snap:bondWith person:7890 . 4. Unproblematic co-references: a. person:200000 rdf:type snap:mergedResource ; dcterms:replaces person:12345 ; dcterms:replaces person 67005 .

  11. The Technical Bit But not too technical...

  12. Data Model (Reuse is Good) Our Ontology Existing Ontologies • • Lawd Snap • Prov http://onto.snapdrgn.net • Foaf (Relationships) • Bibo • Rdf • Rdfs • Cnt • Dct

  13. Persons ● Model centers around lawd:Person ● Main classes provided by lawd ● Snap ontology provides relationship links between Persons ● Separation between Publisher and Collection

  14. Minting URIs Project URI Project URI Ingestion Person Data Person Data SPARQL Query XSLT Script SNAP URI SNAP URI Project URI Re-Ingestion Project URI Person Data Person Data

  15. Storage • Attempt #1 – Sesame • Attempt #2 – 4Store • Currently 673, 982 Persons (+ associated data) • Ingested • Datasets: PIR, LGPN, TM BM, VIAF (1 - 673754) • Merged records: LPGN/PIR (not finalised)

  16. Merging Persons SNAP URI dct:replaces SNAP URI SNAP URI Project URI Project URI Person Data Person Data

  17. Human-Readable Resource • http://data.snapdrgn.net/person/<id> • Current Breakdown of Person IDs: • PIR: 1 - 10924 • TM: 10925 - 367917 • LPGN: 367918 – 671019 • BM: 671020 - 671972 • VIAF: 671973 - 673753 • Test Merged (LGPN & PIR): 673754 – 673934

  18. Data Out • Public Endpoint (Human) : https://snap.dighum.kcl.ac.uk/query/ • Public Endpoint (Computer): https://snap.dighum.kcl.ac.uk/sparql/

  19. Coming Soon(ish) ● Polish Person Profile pages ● Add Project and Collection pages ● Add search pages o by project-minted identifier o by place o by name (string) o by citation reference... ● More Merged Persons

  20. SNAP:DRGN 2 ● To merge or not to merge..? o Adding in the description of scholarly disagreement on merging e.g V5a-38858 claims to be both pir2-r-0243 and pir2- r-0244 V5a-38861 claims to be both pir2-i-0492 and pir2- i-0493

Recommend


More recommend