1 / 20

The fault is not in our databases, but in ourselves: messy data, metadata, and interoperability

The fault is not in our databases, but in ourselves: messy data, metadata, and interoperability. Adam Rabinowitz The University of Texas at Austin arabinow@mail.utexas.edu.

jennifer-rodriquez
Download Presentation

The fault is not in our databases, but in ourselves: messy data, metadata, and interoperability

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The fault is not in our databases, but in ourselves: messy data, metadata, and interoperability Adam Rabinowitz The University of Texas at Austin arabinow@mail.utexas.edu

  2. British Museum Collection CRM schema - work in progress version by Dominic Oldman is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License. Rabinowitz ● FAIMS 2012 ● 8.17.12

  3. Rabinowitz ● FAIMS 2012 ● 8.17.12

  4. Go Fish! Rabinowitz ● FAIMS 2012 ● 8.17.12

  5. Does anyone have… a medieval Islamic padlock? Rabinowitz ● FAIMS 2012 ● 8.17.12

  6. Rabinowitz ● FAIMS 2012 ● 8.17.12

  7. Rabinowitz ● FAIMS 2012 ● 8.17.12

  8. Rabinowitz ● FAIMS 2012 ● 8.17.12

  9. Hey, Corinth: do you have… a ceramic krater? Rabinowitz ● FAIMS 2012 ● 8.17.12

  10. Hey, Corinth: do you have… a ceramic krater? Rabinowitz ● FAIMS 2012 ● 8.17.12

  11. Hey, Corinth: do you have… a ceramic krater? Rabinowitz ● FAIMS 2012 ● 8.17.12

  12. Does anyone have… stuff from Athens? Pelagios graph explorer Rabinowitz ● FAIMS 2012 ● 8.17.12

  13. Hey, South Italy, do you have… Geometric ceramics? Rabinowitz ● FAIMS 2012 ● 8.17.12

  14. Mockup of metadata description for digital object sfi_CH05SR_3065_m.JPG <dc > <title>sfi_CH05SR_3065_A9_m.JPG</title> <temporal>Hellenistic to Late Byzatine</temporal> <spatial>Chersonesos South</spatial> <creator>ICA</creator> <description>Lock</description> <date>2005:08:23</date> <format>.JPG</format> <identifier>sfi_CH05SR_3065_A9_m.JPG</identifier> <publisher>ICA</publisher> <language></language> <relation>image_documentation/special_finds/photographs/master</relation> <isInContext>CH05SR_434</isInContext> <isPartOf>sfi_CH05SR_3065</isPartOf> <rights>Specified in SIP</rights> <subject>Chersonesos South</subject> <subject>Archaeology</subject> <subject>photographs</subject> <source>Master</source> <type>image_documentation</type> </dc> • Static • Harvested From ARK • Technical Metadata • Harvested from Hierarchy • Harvested From File Name Rabinowitz ● FAIMS 2012 ● 8.17.12

  15. iRODS (integrated rule-oriented data system) www.irods.org Rabinowitz ● FAIMS 2012 ● 8.17.12

  16. Descriptive metadata using METS and Dublin Core Rabinowitz ● FAIMS 2012 ● 8.17.12

  17. Automated integration of post-season documentation with database using unique ID in filename of iRODS object Rabinowitz ● FAIMS 2012 ● 8.17.12

  18. Preservation metadata using METS and PREMIS Rabinowitz ● FAIMS 2012 ● 8.17.12

  19. The next step: a freestanding desktop toolkit to automatically extract metadata without iRODS? Rabinowitz ● FAIMS 2012 ● 8.17.12

  20. Go Fish, again! Some thoughts about interoperability and archaeologists off the grid • The bar for metadata creation has to be lowered – it needs to be cheaper and easier to document your own material outside repositories • This is especially true for documentation outside the database: individual files like images (or spatial data) that tend to proliferate even after a project is over, and that aren’t self-explanatory • Data federation strategies should take into account the tendency of archaeologists to begin a search for information with a few key concepts, like • Space • Time • Record type (site, building, object, excavation photo, etc) • and within this, for objects, material • URI services could really help here in the production of minimally interoperable metadata; Dublin Core probably isn’t a bad starting point as a schema • In building services to use interoperable data, we should not neglect the highly visual nature of Go Fish searches, which get us past issues of terminology, classification, and misclassification (I can tell that’s not a hand-axe when I see it) Rabinowitz ● FAIMS 2012 ● 8.17.12

More Related