1 / 10

Common Development A Natural History Example using Darwin Core

Common Development A Natural History Example using Darwin Core. Much talk of common development Concern over level of agreement required Necessary differences between implementations “We’re all individuals” Does this necessarily mean “lowest common denominator”?. Natural History Catalogues.

dash
Télécharger la présentation

Common Development A Natural History Example using Darwin Core

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. Common DevelopmentA Natural History Example using Darwin Core • Much talk of common development • Concern over level of agreement required • Necessary differences between implementations • “We’re all individuals” • Does this necessarily mean “lowest common denominator”?

  2. Natural History Catalogues • KE: “Just another catalogue” • Museum: “We’re different” • Some degree of commonality in non-catalogue modules • e. g. taxonomy • Cross-fertilisation approach to catalogue design • Ad-hoc evolution of natural history support • Critical mass of natural history sites What more can we do?

  3. “Standard” Structure • KE EMu is object-oriented • Commonality at several levels • Base module • Multimedia, Admin • Base catalogue • Location tracking, Deaccession, Condition checks, … • Most natural history functionality built per site • Simple specimen counts, measurements etc. • Identifications • Type status

  4. “Standard” Catalogue Object Structure

  5. Creating a Natural History layer • Extends base functionality • Common across all NH sites • Not “one size fits all” • Add common columns • Identifications • Darwin Core • Add common functionality • Re-identification • Specimens & Preparations

  6. Natural History Catalogue Object Structure

  7. Benefits • Raise level of commonality amongst sites • Facilitate data interchange • Better utilise natural history based development by KE • Easier adherence to standards • Darwin Core • ABCD • Simpler implementations of protocols • DiGIR • Can grow incrementally

  8. Example – Darwin Core • Darwin Core columns and tabs available in Natural History Catalogue layer • Population of columns implemented for each specific client • Mapping of client specific columns to standard DwC columns • DwC columns automatically populated when record saved (similar to Summary Data) • Significantly simplifies provision of DwC data (e.g. DiGIR provider) • Once mapping done then all DwC immediately available for your collection • Currently implemented for NMNH and MV • Success depends on mapping

  9. Issues • Agreeing common goals • Conflicting requirements • Ultimately depends on NH user base • Utilise EMuUsers forums • Setting priorities • Funding • Backwards compatibility • Don’t want to change existing column names! • Changes to existing workflows? • Integration with non-NH parts of catalogue?

  10. Summary • Critical mass of natural history sites using KE EMu • Scope for common natural history level of module development • Particularly suited to emerging standards • Success dependent on degree of agreement • Approach equally applicable to other catalogues and other modules

More Related