Project

General

Profile

Task #1598

Story #312: Identifier generation and reservation

Design replicated store for reserved identifiers

Added by Dave Vieglais almost 13 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ben Leinfelder
Category:
-
Start date:
2011-05-31
Due date:
% Done:

100%

Milestone:
CCI-0.6.2
Product Version:
*
Story Points:
Sprint:

Description

We need a data store replicated across the CNs for keeping track of identifiers that have been reserved.

Expect that the postgres database would be the simplest mechanism for this - using either metacat as the replication manager or some other lock mechanism.

History

#1 Updated by Dave Vieglais almost 13 years ago

Note that we will likely use the http://n2t.net/ezid EZID service for identifier production. Some additional considerations listed in #1599

#2 Updated by Ben Leinfelder over 12 years ago

  • Status changed from New to Closed
  • Milestone set to CCI-0.6.2

We now have an LDAP implementation for reserving Identifiers for a particular user for a short amount of time (24 hour expiration).
The LDAP objectClass hass been added to the cn_buildout and the ReserveIdentifierService class has been coded in the d1_identity_manager project (which shares many similar LDAP functions)

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)