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

ancient prosopographies
SMART_READER_LITE
LIVE PREVIEW

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 -


slide-1
SLIDE 1

Standards for Networking Ancient Prosopographies

Gabriel Bodard

  • K. Faith Lawrence

(King’s College London)

slide-2
SLIDE 2
slide-3
SLIDE 3
  • Project history
  • Bringing people together
  • Prior art: Pelagios
  • Data Model
  • Creating SNAP URIs
  • Technical Issues - Storage
  • Methodological Issues – Merging
  • SNAP Online
  • Into the future…
slide-4
SLIDE 4
slide-5
SLIDE 5

Digital Classicist wiki

slide-6
SLIDE 6

LAWDI

slide-7
SLIDE 7

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)
slide-8
SLIDE 8

The ancient geography model

slide-9
SLIDE 9

The ancient geography model

slide-10
SLIDE 10

The ancient geography model

slide-11
SLIDE 11

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

slide-12
SLIDE 12

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 .

slide-13
SLIDE 13

The Technical Bit

But not too technical...

slide-14
SLIDE 14

Data Model (Reuse is Good)

  • Lawd
  • Prov
  • Foaf
  • Bibo
  • Rdf
  • Rdfs
  • Cnt
  • Dct

Our Ontology

  • Snap

http://onto.snapdrgn.net (Relationships)

Existing Ontologies

slide-15
SLIDE 15

Persons

  • Model centers around lawd:Person
  • Main classes provided by lawd
  • Snap ontology provides relationship

links between Persons

  • Separation between Publisher and

Collection

slide-16
SLIDE 16

Minting URIs

Person Data Project URI

Ingestion

Person Data Project URI SNAP URI Person Data Project URI

XSLT Script Re-Ingestion

Person Data Project URI SNAP URI

SPARQL Query

slide-17
SLIDE 17

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)
slide-18
SLIDE 18

Merging Persons

SNAP URI Person Data Project URI SNAP URI Person Data Project URI

SNAP URI dct:replaces

slide-19
SLIDE 19

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
slide-20
SLIDE 20

Data Out

  • Public Endpoint (Human) :

https://snap.dighum.kcl.ac.uk/query/

  • Public Endpoint (Computer):

https://snap.dighum.kcl.ac.uk/sparql/

slide-21
SLIDE 21

Coming Soon(ish)

  • Polish Person Profile pages
  • Add Project and Collection pages
  • Add search pages
  • by project-minted identifier
  • by place
  • by name (string)
  • by citation reference...
  • More Merged Persons
slide-22
SLIDE 22

SNAP:DRGN 2

  • To merge or not to merge..?
  • Adding in the description of scholarly disagreement
  • n 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