> >> 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.
This is also possible in the JSPUI with the "html" servlet; it was intended to let DSpace serve an archived website. In certain circumstances (at least in 1.4, it was when the primary bitstream appeared to be an HTML file) the item page uses the "html" servlet instead of the "bitstream" servlet in the links to bitstreams, and only shows the primary bitstream. For example, these are equivalent references to bitstreams, but note how the second one doesn't have the Sequence ID: http://mydemo/jspui/bitstream/123456789/454/4/2dExports/stata/dxf/a3_6-10.dxf http://mydemo/jspui/html/123456789/454/2dExports/stata/dxf/a3_6-10.dxf There is another problem with Sequence IDs, however. None of the current item migration/transfer tools preserve them. The AIP packager (see the wiki page about the PLEDGE prototype) managed it. Currently, if an Item gets moved from one DSpace to another, the Sequence IDs can get scrambled. As Richard mentions, bitstream names are not necessarily unique. Hopefully the 2.0 data model will include some sort of relationship metadata so the code can do better than randomly choosing the "first" bitstream matching the correct name. -- Larry ------------------------------------------------------------------------- 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
