A conceptual framework for implementing solid identifiers for use in data aggregation frameworks and their impact on data publishing and downstream linking.

1. BiSciCol + VertNet: A Conceptual and
Technical Framework for Identifying
Specimens
iEvoBio Flash Talk 2013
Aaron Steele, University of California, Berkeley
John Deck, University of California, Berkeley
Rob Guralnick, University of Colorado, Boulder

2. VertNet

4. VertNet LifeCycle of a Record

5. • <1% DwC Triplet match between Genbank and
VertNet
• Identifiers are not awesome (not persistent,
resolvable, or even globally unique)
BiSciCol / Identifier Review of
Challenges

6. ark:/21547/R2 = Uniquely identifies processed data instance
_
separator = _
550e8400-e29b...
suffix =550e8400-e29b-41d4-a716-446655440000
The suffix is assigned by VertNet can be resolved using both the
EZID and BCID systems using the suffix passthrough system.
BCID Technology (from software bazaar)
ark:/21547/
ark:/21547/ = Scheme plus name assigning authority
R2
R2 = BCID Group identifier, defines a common concept per dataset

7. A Conceptual and Technical Framework for
Identifying Specimens with (VertNet + BiScicol)

8. IC:CC:CN (Literal)
ark:/21547/R2 (group)
ark:/21547/R2_{LocalID}
ark:/21547/S2_{UUID}
ID’s in the
Data LifeCycle
Identifiers Maintained
Identifiers Maintained
Identifiers Maintained
Identifiers Maintained
MachineInterpretation

9. Publisher
IC:CC:CN (Literal)
ark:/21547/R2_{LocalID}
Aggregator
ark:/21547/S2_{UUID}
Using awesome identifiers we can track all metadata
instances from publisher to aggregator through Applications
Machine_interpretation
VertNet
EOL
iDigBio
Genbank
Resolver
Applications
AggregationsSource