Project

General

Profile

Bug #5802

Use UUID for local identifiers

Added by ben leinfelder over 7 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Category:
morpho - general
Target version:
Start date:
01/23/2013
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5802

Description

Currently in Morpho 2.x development we are using a "scope.XX" format for our local identifiers. The "XX" is incremented whenever the need arises for a new identifier, whether as a revision to the previous package or as a new data file or as a new data package. This can be confusing because you might infer relationships between packages as older or newer even though they have no relationship to one another.

If we went with UUID locally we would have very opaque/very unique identifiers and would not be at risk of tricking people with faulty semantics. The downside is that they are long and not user friendly.

When it came time to save them to the network the likelihood of collision is als very low.

When it came time to "publish them" (see bug #5799) we would have the EZID service generate a [shorter] DOI for us so that it would be more friendly for print media and citations.


Related issues

Blocked by Morpho - Bug #5799: publish using DOI featureNew01/22/2013

History

#1 Updated by ben leinfelder over 7 years ago

Now using UUID across the board. GMN uses this exclusively for its generateIdentifier method and Metacat 2.0.6 will support UUID generation too.

#2 Updated by Redmine Admin about 7 years ago

Original Bugzilla ID was 5802

Also available in: Atom PDF