Comment #3 on issue 2021 by [email protected]: Per repostitory digital object upload
http://code.google.com/p/qubit-toolkit/issues/detail?id=2021
Having per repository asset directories has performance drawbacks if a description is moved from one repository to another; all related assets must be moved and their path in the database must be updated. The performance hit especially pronounced if moving a high-level description with a lot of descendants.
If we thumbnail paths are dependent on repository, then the search index must be updated as well, as thumbnail paths are stored for search results.
Because of these considerations, it makes sense to make per-repository digital object paths a configuration setting, as many institutions will not need this feature.
-- You received this message because you are subscribed to the Google Groups "Qubit Toolkit Issues" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/qubit-issues?hl=en.
