Date: Thu, 16 Jun 2005 23:52:07 -0700 (PDT)
From: Corey Harper <charper@darkwing.uoregon.edu>
The command line tool I was thinking of (called the community filiator!)
wasn't actually capable of making the fix. It's for creating new (or
removing) parent child relationships between communities &
sub-communities, but can't actually move a collection from one community
to another. The latter is necessary to create an interceding
sub-community where collections already exist.
However, it's easy enough to move a community by editing the database
directly. I tested this in irtest first, but did a database dump before
doing it live in case anything broke. It looks okay, but let me know if
you see anything weird. Essentially, it just involves changing the
collections community membership, then re-indexing to make sure all items
are represented in all appropriate browse and search indexes.
If you notice anything awry, I can either troubleshoot or restore to a
backup from about 11:30pm, but everything looks right to me.
-Corey