> First, it is assigned sequentially and IDs are not reused if a bitstream
> is deleted. There is no magic ordering, and it was *not* intended for
> organizing a set of bitstreams into a meaningful sequence (e.g. PDF
> chapters of a book). Its sole purpose is to provide a *durable* unique
> ID for a bitstream - think of it as a 'sub-handle' ID - modulo an item
There's actually a bug in the data model, then. It's possible to get
the same sequence ID reused, because when adding a Bitstream, the code
only looks for the highest existing SequenceID and increments that.
1. Take an existing Item, go into the "Edit Item" admin page
(/dspace/tools/edit-item), and add a new Bitstream with a distinctive name.
Say, "foo.pdf".
2. Determine its Sequence ID. Go to the Item page
/dspace/handle/<my-handle> and observe the "View/Open" link next
to your bitstream, the path element after its handle is the SequenceID.
It should be the highest SequenecID there since it was most recently added.
There are some "invisible" Bitstreams (like licenses) that also take
up SIDs.
3. Go back to the "Edit" page and delete that newest bitstream.
4. Add a different bitstream with a different name, say, "bar.pdf".
5. Go to a freshly-loaded copy of the Item page, and observe that
"bar.pdf" has the same SequenceID that "foo.pdf" had before.
I'll submit this as a bug on sourceforge too.
-- Larry
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
