On Mon, 2008-08-18 at 19:23 +0100, Graham Triggs wrote: > Richard Rodgers wrote: > > I do worry about opening door #1 [content rejection], > > since taking assets as found seems pretty close to the bedrock > > use-case for digital repositories - at least preservation-minded ones. > > > Well, that is an interesting argument! Now, if we look at assets 'as > found' then they will [probably] be located in a users file system. That > file system will already be enforcing a unique constraint on the names > of files within a directory. > True - ingestion into a repository is a destructive decontextualization/recontextualization. My point about 'as found' means be as minimally destructive as possible, viz not changing 'graham.txt' to 'richard.txt' (or 'graham[2].txt'). If fact (the web submission UI notwithstanding), nothing in the data model prevents us from capturing all we want as contextual metadata (hasParent 'q4' etc).
> Now, in your example you had a user with two files that had the same > name but located in different directories. Presumably there is implicit > knowledge in the particular organisation of the file structure. And we > are not taking it 'as found' because DSpace is forcing the user to throw > away that organisation (and therefore any knowledge/information it > implies) when attaching all those files to a single item. > > In terms of the sequence number, we assign a 'genuine unique id' to > every bitstream that is ingested, and there is no reason why that id > can't be used in place of the sequence number in the url in the case > where disambiguation is necessary. > > There is nothing wrong with presenting a disambiguation page if a url is > provided without that unique id, and where the filename can't uniquely > resolve. > > There just isn't any need to use a sequence number in this way, and > include it as part of the URL. What there is a need for is a way to > define the order in which the bitstreams are presented for an item - > which should be the job of a sequence number, but it isn't used for that. > > (Note that the above is true for the majority using the 80/20 rule. > There may be some exceptional cases that doesn't fit into the above > statements, but then they may not be serviced sufficiently by the > existing use of sequence numbers either). > > G > This email has been scanned by Postini. > For more information please visit http://www.postini.com > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
