Hmmm, where *is* the sequence_id defined and discussed, anyway? It appears that the sequence_id must be (expected to be) unique per-item, because a bitstream can be in more than one bundle (Bitstream.getBundles returns an array) and that makes nonsense of having a single sequence_id if it's per-bundle.
Hmmm, grepping around for sequence_id finds a comment in the class which upgrades DSpace 1.1 to 1.2, which comment leads me to Item.update(). There any unsequenced bitstreams are indiscriminately given serially-numbered sequence_ids higher than any found in the item. Again this is suggestive but not definitive. However it also destroys any speculation that sequence_id might be used to relate derivative bitstreams to source bitstreams. (Can you see I'm grasping at straws to explain our data?) I'm rattling on like this because (a) I'm hoping that someone who knows the design can confirm or deny my deductions; and (b) this should be documented somehow, and the record of my investigations may help in that effort. -- Mark H. Wood, Lead System Programmer [email protected] Asking whether markets are efficient is like asking whether people are smart.
pgpUn4U3ddJqR.pgp
Description: PGP signature
------------------------------------------------------------------------------ The demand for IT networking professionals continues to grow, and the demand for specialized networking skills is growing even more rapidly. Take a complimentary Learning@Cisco Self-Assessment and learn about Cisco certifications, training, and career opportunities. http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
