Title: Message Title
|
|
|
|
Updating existing installations' databases will be...interesting. New constraints on existing columns must be added as table constraints. Removing existing constraints requires discovering the names generated for them, since we don't name them.
An alternative would be to create a new MetadataValue2 table with the desired properties, copy the old table's rows to it, drop the old table, and rename the new table. We'd have to DROP and recreate the dcvalue view and the additional indices too.
|
|
|
|
|
|
|
Many have wished for the flexibility of DSpace's *operable* metadata infrastructure, which is specific to Item, to be available in other types such as Community and Collection. Support for operable metadata should be pushed down from Item to DSpaceObject so that all DSOs can use it.
I recognize that there are a number of other ways in which DSpace's m...
|
|
|
|
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel
