Dorothea Salo wrote: > Good point. Would I be right in hazarding a guess that this was > originally designed as a gesture toward relatively simple updating of > this set of configuration options (without direct database-mucking)? > And that this is therefore a special case of the general issues with > how difficult DSpace (and its underlying tech stack) is to configure?
Ahh... but it *is* relatively simple to update the registered bitstream formats without direct database-mucking. There is an admin panel to do it! And there is the rub that makes handling updates harder - even if you can distinguish precisely which items have been added / modified since the version that a user is upgrading from (and we have to account for skipping versions, which complicates that a little), you have to be able to cope with the fact that the user may have altered their registry - adding conflicting entries, removing others, etc. G This email has been scanned by Postini. For more information please visit http://www.postini.com ------------------------------------------------------------------------- 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 DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
