I think we're talking about different things (or I'm really confused). As I understand it, I have to create the collection on the new dspace before I can import items from the source collection. The act of creating a collection assigns and database ID for that collection. When you create a collection on a brand new dspace, you get collection ID of 1. When you hold your mouse over the collection name, you can see the handle/collectionID.
I have an exported simple archive format directory structure from the source dspace. (I did not actually do the export). That structure is handle/collection Id/<1,2,3...>/dublin_core.xml, handle,... The collection Id on the source system is different. On the dspace import command, I specify --collection=4321/1 as the destination of the import since I just created that collection on my new system, and --source=4321/1765 and the import directory of that collection from the source system. Is it OK that the collection ID's are different? If it's not OK, then I need to create the collection on the new system and make it's ID match that of the source system???? I'm not talking about the id of the endpoint article, (the value in the "handle" file of the simple archive format structure for an article), only of the collection the article resides in. Am I really confused? ;-/ -- View this message in context: http://dspace.2283337.n4.nabble.com/moving-to-new-machine-tp4606063p4606441.html Sent from the DSpace - Tech mailing list archive at Nabble.com. ------------------------------------------------------------------------------ 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
