83 lines
2.5 KiB
Plaintext
83 lines
2.5 KiB
Plaintext
|
head 1.3;
|
||
|
|
access;
|
||
|
|
symbols;
|
||
|
|
locks; strict;
|
||
|
|
comment @# @;
|
||
|
|
|
||
|
|
|
||
|
|
1.3
|
||
|
|
date 2007.01.29.15.52.09; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.2;
|
||
|
|
|
||
|
|
1.2
|
||
|
|
date 2006.01.18.13.24.10; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next 1.1;
|
||
|
|
|
||
|
|
1.1
|
||
|
|
date 2006.01.17.20.29.59; author RicardoPereira; state Exp;
|
||
|
|
branches;
|
||
|
|
next ;
|
||
|
|
|
||
|
|
|
||
|
|
desc
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.3
|
||
|
|
log
|
||
|
|
@none
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@%META:TOPICINFO{author="RicardoPereira" date="1170085929" format="1.1" version="1.3"}%
|
||
|
|
---++ Use Case: Tracking Source Records
|
||
|
|
|
||
|
|
----
|
||
|
|
---+++++ Description
|
||
|
|
In some situations, aggregators may add value to records harvested from data sources. For example:
|
||
|
|
* a geo-referencing service may assign a geo-reference to a record based its locality description;
|
||
|
|
* a GBIF data cleaning service may correct an error in the record geo-reference; or
|
||
|
|
* an on-line determination system may assign a different determination to a specimen record.
|
||
|
|
|
||
|
|
In those cases, a new record is generated from the original source record. Both the source and derived records can be made available by online data services. It may be difficult to identify whether a record is derived from another. Also, in some analyses using both versions of a data record may yield lower quality results.
|
||
|
|
|
||
|
|
The main difference between this use-case and DetectingDuplicates is that in the later both the source and the duplicate records are essentially the same, thus they can both share the same globally unique identifier. In this use-case, the source and derived records are different because some of the attributes have been changed.
|
||
|
|
|
||
|
|
----
|
||
|
|
<img class="center" alt="Tracking Source Records" title="Tracking Source Records" src="%ATTACHURL%/TrackingSourceRecords.png">
|
||
|
|
|
||
|
|
---+++++ Categories
|
||
|
|
CategoryUseCases@
|
||
|
|
|
||
|
|
|
||
|
|
1.2
|
||
|
|
log
|
||
|
|
@
|
||
|
|
.
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d1 1
|
||
|
|
d16 1
|
||
|
|
a16 1
|
||
|
|
<img class="center" alt="Tracking Source Records" title="Tracking Source Records" src="images/TrackingSourceRecords.png">
|
||
|
|
@
|
||
|
|
|
||
|
|
|
||
|
|
1.1
|
||
|
|
log
|
||
|
|
@Initial revision
|
||
|
|
@
|
||
|
|
text
|
||
|
|
@d6 3
|
||
|
|
a8 3
|
||
|
|
* a geo-referencing service may assign a geo-reference to a record based on locality description;
|
||
|
|
* a GBIF data cleaning service may correct an error in a geo-reference; or
|
||
|
|
* an on-line determination system may assign a different determination to the record.
|
||
|
|
d12 1
|
||
|
|
a12 1
|
||
|
|
The main difference between this use-case and DetectingDuplicates is that in later both the source and the duplicate records are essentially the same, thus can get the same identifier. In this use-case, the source and derived records are different because some of the attributes have been added or changed.
|
||
|
|
@
|