On Fri, Jul 27, 2007 at 12:20:55AM -0400, Ekaterina Pechekhonova wrote:
I meant to say that building a flexible ExternalIdentifier service is a
challenging task (as James himself has said), so I am concerned that at
some point the configuration options will be dropped (because of lack of
time,
Message -
From: Mark Diggory [EMAIL PROTECTED]
Date: Wednesday, July 25, 2007 9:16 pm
Subject: Re: [Dspace-tech] [vote] Do we want to assign external identifiers
(Handles) to files?
To: Ekaterina Pechekhonova [EMAIL PROTECTED]
Cc: DSpace Tech dspace-tech@lists.sourceforge.net, Robert Tansley
Hello Kate,
On Jul 25, 2007, at 4:48 PM, Ekaterina Pechekhonova wrote:
We need to reiterate and recognize that in the DSpace 2.0
Architectural Model it was of strong interest that Metadata can be
attached at any level of the Data Model (Community, Collection, Item,
Manifestation and
We need to reiterate and recognize that in the DSpace 2.0
Architectural Model it was of strong interest that Metadata can be
attached at any level of the Data Model (Community, Collection, Item,
Manifestation and Content). That for all practical purposes, and
External
On Mon, Jul 23, 2007 at 09:48:39AM +1000, Gary Browne wrote:
James, thanks for raising this issue and in particular getting people to
put their money where their collective mouths are.
Believe me, if I could possibly avoid it, I would leave the issue well
alone ;)
I'm sure this will come as no
On Tue, 2007-07-24 at 09:22 +0100, James Rutherford wrote:
As I see it there are
(broadly) two camps: those who believe that every meaningful tier in the
DSpace content hierarchy should get external identifiers, and those who
don't (or at least those who can't decide and so want it to be
On 24/07/07, Graham Triggs [EMAIL PROTECTED] wrote:
But, I think we are getting a little tied up around the idea that it may
only be a single implementation that has all these possibilities
available as configuration options - and that need not be the case at
all.
+1 - I doubt we could come
On 24/07/07, James Rutherford [EMAIL PROTECTED] wrote:
On Tue, Jul 24, 2007 at 10:12:52AM -0400, Robert Tansley wrote:
But, I think we are getting a little tied up around the idea that it may
only be a single implementation that has all these possibilities
available as configuration options
Hi Rob,
However, IDs may depend both on the object type and
related objects -- e.g. bitstream IDs may include the item ID as a
path component, or the version number etc -- and the ID scheme itself.
Do you think it's appropriate for external IDs to support internal system
hierarchy
and
Tech
Subject: [Dspace-tech] [vote] Do we want to assign external
identifiers(Handles) to files?
Hi all,
As part of my work on the identification mechanisms employed by DSpace
(both internal and externally managed identifiers) I've decided that
it's better to assign external identifiers to files than
On Thu, Jul 19, 2007 at 06:46:20PM +0100, Graham Triggs wrote:
Possibilities that should be supportable:
* reassigning the existing id (handle) to a new file
This is, in my humble opinion, pure evil. How can you consider something
to be an *identifier* if you can't actually guarantee that it
On Thu, Jul 19, 2007 at 01:47:19PM -0400, Ekaterina Pechekhonova wrote:
+1 as it usually better to have more options then less.
However, in our repository we keep identifiers on item level as we
see item as a repository atomic structure, and we think it's pretty
important that file
From: James Rutherford [EMAIL PROTECTED]
This is, in my humble opinion, pure evil. How can you consider something
to be an *identifier* if you can't actually guarantee that it identifies
something?
I absolutely agree. But how can you guarantee that it resolves to what it is
meant to be
See the arch review notes (I think
http://wiki.dspace.org/index.php/ArchReviewNotesThur was the day we
really hammered on it) for decisions made about identifiers and
versions. We spent a lot of time on that! (Basically there's an
identifier for the 'latest version' of each item and sub-part,
From: James Rutherford [EMAIL PROTECTED]
Assigning or displaying? I find it hard to believe that you actually
have a problem with giving identifiers to files, but I can understand
why you might not want your users to know about them.
Because I don't believe that an identifier should be
From: James Rutherford [EMAIL PROTECTED]
I absolutely agree. But how can you guarantee that it resolves to what it
is meant to be identifying if you completely disallow the possibility to
reassign it?
I'd flip this around and say how can you guarantee that it resolves to
what it is meant to
I tend to agree with Graham:
1. That can of worm may have already been opened as soon as people
approach the persistent identifier issue. Items are relatively stable
so we don't have much of a problem on assigning handles to them but
the same can't said about the files. At least for now the admin
+1 for file identifiers; we do it already.
Use case (one of many): Professor is writing a print textbook, is
putting sample code in repository, wants permanent URLs for the
component files that can be printed in the book.
Dorothea
Jim,
Just for clarification to the group... Its unclear what your
requesting a vote on: Anyone can assign an external identifier to a
Bitstream in an external identification system. Can you answer the
two following questions for the group?
1.) Are you suggesting that we will support an
On Thu, Jul 19, 2007 at 11:14:15AM -0400, Mark Diggory wrote:
Just for clarification to the group... Its unclear what your
requesting a vote on: Anyone can assign an external identifier to a
Bitstream in an external identification system. Can you answer the
two following questions for
Then what will happen if I remove one file from an item and add
another file? Will the new file get the old handle or a new one or I
can choose?
Thanks,
Zhiwu
On 7/19/07, James Rutherford [EMAIL PROTECTED] wrote:
On Thu, Jul 19, 2007 at 11:14:15AM -0400, Mark Diggory wrote:
Just for
On Thu, 2007-07-19 at 12:03 -0400, Robert Tansley wrote:
+1 on ability to assign arbitrary external IDs to bitstreams.
+1 on ability to assign 'hierarchical' external IDs to bitstreams (for
graceful fallback if files are deleted etc).
Minor point, but you don't actually need a hierarchical
On Thu, 2007-07-19 at 10:06 -0600, Zhiwu Xie wrote:
Then what will happen if I remove one file from an item and add
another file? Will the new file get the old handle or a new one or I
can choose?
How deletion of objects assigned external ids is not something that
DSpace should force on to a
+1 assign external identifiers to files
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
24 matches
Mail list logo
