Introducing ApplePie:A botanical annotation network

powered by Filtered Push

James A. Macklin

Lei Dou, James Hanken, Maureen Kelly, David Lowery, Bertram Ludaescher, Paul J. Morris, Robert A. Morris

Supported by NSF DBI-0960535

Outline

AppleCore Communicating Knowledge Digitization Efficiency and Accuracy Kepler Kurator

AppleCore

DarwinCore (DwC) has become a mature set of standards for sharing biodiversity data.

Inherent generality of the documentation has led to broad interpretation of the terms and confusion about which terms to use within a community.

Goal of AppleCore is to tackle this issue for herbaria by providing detailed guidelines based on best practices for publishing botanical specimen information as DwC.

These guidelines include recommended terms, more specific definitions, multiple examples, common issues and controlled vocabularies.

https://code.google.com/p/applecore/

Example: Guidance on Collector Number

DarwinCore: recordNumber

An identifier given to the Occurrence at the time it was recorded. Often serves as a link between field notes and an Occurrence record, such as a specimen collector's number.

AppleCore: Collector number

The collector number is a personal identifier assigned by the collector to the specimen(s) at the time of collecting, and typically written on the specimen label. Collector numbers - also called collection numbers - often form chronological series of specimens collected by one or more collectors. Duplicate specimens typically get the same collector number (as opposed to specimen numbers!) and can as such help to identify duplicates across herbaria.

Publish the collector number in recordNumber. In the case of multiple collector numbers assigned to the same specimen, list the primary collector number first (if feasible) and separate with "|" or "; ".

Morphbank

Symbiota

FP Access PointFP

Helper

FPHelper

Specify6FP

Helper

AnnotationProcessor

AnnotationStore

Analysis: Cluster Duplicates

Publish Messages

FP Node

KeplerFP

Helper

Driver

WebClientFP

Helper

AnnotationProcessorDriver

InstitutionalDatabase

CSV, XML

Export

A new determination transported through ApplePie

FP Node

Communicating Knowledge

PUSH

HISTORY

FILTER

FILTER

Specify 6

Digitization Efficiency and Accuracy

Users can detect duplicates in the network based on fuzzy lookups: collector, collector number, date, etc.

Users can annotate any field in record to provide new determinations, correct errors, add information, etc.

Users can benefit from a consensus record which is generated based on annotation of any/all related records

Users can automatically insert records or fields into Specify 6 or export data using web client

Input DataSet (csv)

GeoLocate IPNI FNA

Filtered PushNetwork

Google Cloud ServiceHuman Curation Visualization In Google Map Kepler Provenance Browser

http://www.youtube.com/watch?v=DEkPbvLsud0

Keywords: SPNHC 2011, Filtered-Push, Kepler, Specimen Curation

Kepler Kurator

Collaborations

Consortium of Northeast Herbaria (CNH) TCN funded in 2012 will use FP network in a similar fashion to what has

been demonstrated SCAN: Southwest Collections of Arthropods

Network TCN funded in 2012 Will use FP for data cleanup by experts using

annotation Your project here!

Feedback

If you would like more information about a botanical Filtered Push Network (ApplePie) please contact us:

james.macklin@agr.gc.ca

Interaction with the user is critical and we want to know how best to design interfaces.

Acknowledgements

Components of this work are licensed under a Creative Commons Attribution-Share Alike 3.0 License

Funding: NSF DBI-0960535

Annotation Interest Group:

Apple Core Contributors:

– Peter Desmet, Patrick Sweeney, John Wieczorek, Paul Morris, Amanda Neill

https://code.google.com/p/applecore/

Project Wiki: http://etaxonomy.org/mw/FilteredPush