Relationships not appearing corrrectly after migration

[ma...@marmot.org]

We are in the process of migrating to a new server and have run into an issue that we can't explain.

After import, some objects and collections do not appear within their parent collection while others do appear correctly.  We can't find a pattern for which appears correctly and which do not.

When we did the migration, we used the command line client fedora-ingest.sh using a combination of file based import as well as server to server replication depending on size of the initial object. Examples of the commands used were:

File based ingest
./fedora-export.sh islandora.marmot.org:443 fedoraAdmin {password} steamboatlibrary:2 info:fedora/fedora-system:ATOMZip-1.1  archive /mnt/r_and_d/marmot/fedora-export/ https
./fedora-ingest.sh f /mnt/r_and_d/marmot/fedora-export/steamboatlibrary_2.zip info:fedora/fedora-system:ATOMZip-1.1 localhost:8080 fedoraAdmin {password] http

Replication based ingest
./fedora-ingest.sh r islandora.marmot.org:443 fedoraAdmin {password} steamboatlibrary:2 localhost:8080 fedoraAdmin {password} https http

We confirmed that all datastreams (including RELS-EXT) migrated properly and we compared the results of simple solr queries on both machines to be sure we are getting the same data.

We tried updating the MODS for the record in that isn't showing properly in Islandora and we tried updating by pid in fedoragsearch.  Neither technique has worked for us.

My suspicion is that something is incorrect in Fedora, but I'm not familiar enough with the problem is or to know where to look. 

Could anyone help point us in the right direction?

Thanks,

-- 
Mark Noble
Marmot Library Network

[ma...@marmot.org]

I figured out my own problem.  After doing the import, I need to run fedora-rebuild.sh from fedora/server/bin rebuilding the fedora index.  After running that, everything seems to be working perfectly.