head	1.4;
access;
symbols;
locks; strict;
comment	@# @;


1.4
date	2006.03.02.14.07.38;	author RicardoPereira;	state Exp;
branches;
next	1.3;

1.3
date	2005.12.22.20.52.27;	author RicardoPereira;	state Exp;
branches;
next	1.2;

1.2
date	2005.12.22.20.49.55;	author RicardoPereira;	state Exp;
branches;
next	1.1;

1.1
date	2005.12.22.20.46.00;	author RicardoPereira;	state Exp;
branches;
next	;


desc
@
.
@


1.4
log
@Page out-of-date
.
@
text
@*This page is out-of-date!!*
-- RicardoPereira - 02/Mar/2006
----

---++ GUID Requirements Specific to Specimens and Collections

*Requirements:*

   * Metadata must identify different categories of specimens and preparations (e.g. survey, trap, individual, leg preparation, tissue)
   * Metadata must identify duplicates of specimens in different collections (like in Herbaria, for example)
   * Metadata must identify original specimen record when served by aggregators
   * Metadata must link identifier to original specimen record when aggregator adds value to it (e.g. adding a geo-reference)

*Issues:*

   * Can a service like DiGIR or BioCase provide GUIDs when underlying collection doesn't provide one?
   * Must collections management software store versions of database records, and assign versioned GUIDs to them? Can DiGIR, BioCase or Tapir software implement that feature instead?


[[GUIDsForCollectionsAndSpecimens][Summary of earlier discussions from the mailing list]]@


1.3
log
@
.
@
text
@d1 4
@


1.2
log
@
.
@
text
@d13 4
a16 1
   * Must collections management software store versions of database records, and assign versioned GUIDs to them? Can DiGIR, BioCase or Tapir software implement that feature instead?@


1.1
log
@Initial revision
@
text
@d5 2
a6 2
   * Metadata must identify different categories of specimens and preparations
   * Metadata must identify duplicates of specimens in different collections
@