Hi, I've just moved a collection from CommunityA to CommunityB using SQL like this:
UPDATE community2collection SET community_id=8 WHERE community_id=140 and collection_id=132; Followed by stopping Tomcat, then running an `index-init`. Now I see the collection listed in the new community, but when I browse to the collection itself, the bread crumb trail in the header still lists the old community as it's parent. I'm on DSpace 3.1 with PostgreSQL, and I've tested this same procedure in a test environment with the same DB / environment, where it worked as expected. Any pointers? :) -- Alan Orth [email protected] http://alaninkenya.org http://mjanja.co.ke "I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone." -Bjarne Stroustrup, inventor of C++ GPG public key ID: 0x8cb0d0acb5cd81ec209c6cdfbd1a0e09c2f836c0
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet
_______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
