We are redoing the community/collection hierarchy and am trying to get some grip on the best way to proceed. As I understand, sub-community management can be done via dspace's administrative tool (CommunityFiliator) and that would be very helpful in what I'm trying to do. However, there is a requirement to move existing collections to a new community/sub-community and based on what I read so far (1,2), this would involve manipulating database directly. I need some clarification on the process:
1. To change the collection-community relationship, I can use the query <code>update community2collection set community_id=NewCommunityID where community_id=OldCommunityID and collection_id=CollectionID; </code> 2. There is a reference to a second query related to communities2item table: <code> update communities2item set community_id=NewCommunityID where item_id in (select item_id from item where owning_collection=CollectionID) </code> Do I need to execute #2 above for each community that the item ultimately belongs to ? In other words, is there a difference between moving a collection to a top-level community vs moving it to a sub-community. Any help much appreciated. Thanks, Harish 1. http://dspace.2283337.n4.nabble.com/Moving-collection-td3417885.html 2. http://sourceforge.net/mailarchive/message.php?msg_id=27543132 -------------------------------- Harish Maringanti ITS Coordinator Kansas State University Libraries 785.532.3261 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
