I had missed that we were hurrying to do something in 4.0. I had assumed that there wasn't time.
Please let us keep DS-220 in mind. SWORD needs a *globally unique* identifier to begin deposit, before we will have created a Handle or DOI or whatnot -- that happens when the Item is installed. So we are sort of being forced toward UUIDs or something like them. https://jira.duraspace.org/browse/DS-220 Let's see if I have all the constraints so far discovered: o Not tied to external services. o The DBMS is an external service. o Not coordinated with other instances. o Durable, because people for some reason want to remember these identifiers for use in other sessions. o Globally unique (at least statistically) due to Atom requirements in SWORD. o Usable across the several services making up a single instance. o Durable across backup/restore. Destroyed and reassigned when transporting objects between instances. o And we want *something* for 4.0. Anything else? When this list is somewhat stable, we should add it to DS-1782. https://jira.duraspace.org/browse/DS-1782 -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Machines should not be friendly. Machines should be obedient.
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access Free app hosting. Or install the open source package on any LAMP server. Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native! http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
