How can we resolve the failure of automated data migration due to this difference in the names of the dspace communities and collections in the two dspace versions? Is it possible to program the data migration process regardless of these changes?
The background to this is that we have an upgrade dspace site. However the names of the communities on the interface of the old dspace version site are different from the names of the communities on the interface of the website of the upgraded dspace version. Secondly, in our old site we had document types as collections, where as in the new site we do not have document types as collections -- Andrew Mwesigwa Librarian I (Academic), Editorial Team Member of Uganda Scholarly Digital Library found at http://dspace.mak.ac.ug and http://dspace3.mak.ac.ug Digitisation Unit, Makerere University Library Services, P. O. Box 7062, Kampala, Uganda, E. Africa Office Phone: +256-414-533735 Mobile Phone: +256-712131871 or +256-701032235 Alternative Email: [email protected] ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
