On Aug 15, 2008, at 10:44 AM, John Preston wrote:

>> 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?
> I need to be able to have a stable reference for a bitstream which
> might undergo a number of version updates. I do not expect to save the
> earlier versions at this time.
>
>> 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.
> I think this is what I need. Was this done via xslt or in servlet  
> code.

XSLT in the 1.5.0 or greater release of the dspace-xmlui. Note, I do  
not think this is present in the servlet code for the jspui in 1.5

-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

Reply via email to