37 lines
1.6 KiB
Plaintext
37 lines
1.6 KiB
Plaintext
head 1.1;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
comment @# @;
|
|
expand @o@;
|
|
|
|
|
|
1.1
|
|
date 2007.06.13.19.06.51; author MattJones; state Exp;
|
|
branches;
|
|
next ;
|
|
|
|
|
|
desc
|
|
@none
|
|
@
|
|
|
|
|
|
1.1
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@%META:TOPICINFO{author="MattJones" date="1181761611" format="1.1" version="1.1"}%
|
|
%META:TOPICPARENT{name="GUIDUseCases"}%
|
|
---++ Use Case: Replicating Data for preservation, load balancing, and failsafe retrieval
|
|
----
|
|
---+++++ Description
|
|
Biodiversity data and supporting abiotic data are used in a variety of applications, including ecological synthesis studies, taxonomic research, and other areas. In many cases it is desirable for the data to be replicated to multiple locations on the Internet in oder to preserve the data in the event of institutional or technological disruptions. Replicated data records, whether they deal with specimens, observations of organisms, or abiotic parameters, need to be identified independently of the multiple locations in which they might be stored in order to assure that the records are not confused as being independent observations when in fact they are replicas. Thus it is critical that the GUID primarily serves the role of identifier and that it not be conflated with current location of the data record.
|
|
|
|
In some cases, the source dataset is composed of hundreds or thousands of individual data records, each identified by a GUID. In those cases, additional resolution mechanisms may be necessary to resolve and retrieve the source data efficiently. Examples of initiatives towards this goal are: the [[STDDOI]] and the [[http://seek.ecoinformatics.org][SEEK]] projects.
|
|
|
|
|
|
---+++++ Categories
|
|
CategoryUseCases@
|