> On Aug 15, 2008, at 9:36 AM, John Preston wrote: >> Hi. Can anyone say how I can re-use a bitstream sequence number. The >> use case is the following. >> >> I have a item with a number of bitstreams which are my data files. I >> also have a text file bitstream which contains the url to the data >> file bitstreams. Now, if I update one of these data files by deleting >> the old bitstream and adding the new data file bitstream, the name >> remains the same but the sequence number for the updated bitstream is >> different from the original data file bitstream. I want to be able to >> add the updated data file bitstream with the same sequence number as >> the original one. >> >> Is this allowed, or do I have to hack it. >> >> John
On Aug 15, 2008, at 10:01 AM, Mark H. Wood wrote: > Allowed or not, this sounds risky. If you are overloading the > sequence number with a new meaning, this practice is likely to bite > you again and again, since the developing stock code won't recognize > your second meaning and will take no pains to preserve it. > > What is it that you need to accomplish? Mark is correct about overloading the semantics here. Note, We adjusted the behavior behind the dspace 1.5 XMLUI (but not the JSPUI) to allow for unsequenced name resolution of the bitstreams. For instance: http://dspace.mit.edu/bitstream/handle/1721.1/39126/ womenpolicymakers_census_dta.tab http://dspace.mit.edu/bitstream/handle/1721.1/39126/ womenpolicymakers_census_dta.tab?sequence=3 http://dspace.mit.edu/bitstream/handle/1721.1/39126/3/ womenpolicymakers_census_dta.tab Are now all valid references the bitstream at this location. In the case where the sequence number is absent, the first bitstream encountered in the Item with that name is returned. It certainly would have been much easier to key Bitstreams on the name rather than a sequence id in the original architecture. I've seen requests such as yours numerous times during my history of working on DSpace and being able to reference resources by simple assignable predictable names rather than internally generated sequence ids makes life on the outside of DSpace easier and 3rd party tooling more powerful. This is something I hope to take into the 2.0 development initiative. Cheers, Mark ------------------------------------------------------------------------- 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
