I realize in the free version I cannot use the structured import. So I can't really test this out. However, reading through the documentation on the Pro, I am a bit confused if I can import a tiered structure that has a 1000+ parent nodes and 5-20 child nodes under each parent.
Do I have to import the child nodes under each parent? Or is there a way in the definition to layout my xml data so it will import and create the child nodes accordingly?
I don't want to pay for the Pro, if I have to still do those manually. It would be nice if I can import the structure in the free on a really limited amount for testing for my desired purpose.
The structured import will follow the structure of the datasource and will act on the Parent Child relations you specify when creating the Import definition in CMSImport via the GUI. Did you watch the video on http://www.cmsimport.com/ already? That shows how it is working. I'm using a sql server database in that situation but you can use the same for xml.
If you want to try it yourself please email me on richard[at] soetemansoftware.nl
I also have a quick question about structuring data imported from Excel files. I have an existing Forum that I plan to export to an Excel file and then import into Umbraco using CMSImport Pro. I would like to import the posts following nForum format like this:
So my plan was to first import all of the categories (top level), and then import the topics as children of the categories. However, how to I handle the intermediate category folders? Also, when specifying a primary key on import, where is this key actually stored in the document type? In your video, I noticed that you somehow were able to produce sub-categories in the catalog example but how did you do this? Is there somewhere that I can see the Excel file that you used in the video?
Great question. Normally you only have Category + Topic. I think the Year/date category folders are based on the created data, or some other date field in NForum. CMSImport PRO will still be able to determine the relation when the topic gets moved from the Category folder to a data category folder so you don't have to worry about that.
All information about the relations (Primary key Foriegn key) etc isn't stored in a document type. When installing CMSIMport a few relation tables are created and they do the magic. If you want to ahve a look at the Excel sheet. You can find it here
To make sure cmsImport can handle the Date category folders I would suggest you create a category in NForum and try to import some topics (can be dummy data). Then check if the Date category folders are created.If not please let me know.
Ah, thanks very much for explaining that. You're right that the category folders in nFourm are just for organization and it doesn't really matter if they are left off. Since we don't have a huge amount of traffic, we will probably just import the topics directly under the category. However, what might be nice for a future version is to somehow be able to specify a different document type for the "recursive" import.
For example I could see that it might be very useful to have one document type called "Product Category", but then the children would be a lighter-weight "Product Category Folder" document type. Then, the products can be directly imported into either the folders or main categories after that. Again, we can live without this, but just a suggestion. Thanks for this great product... it will save us a lot of time :)
Think I didn't explain it correct. When you use the method I mentioned I think the event system of NForum automatically generates the other light weight category folders for so you get the topics nicely sorted into those light weight category folders. The event system of Nforum should take care of this, if not pelase let me know.
In case of the productcategory you mentioned I suggest you just use the recursive option where you can specify the key which maps to the parent category. As shown in the video. then the structure will build up itself based on that relation.
Oh, you're 100% correct... it does automatically create the date folders on import natively. I was just able to move over my entire nForums content to our new website including members and all. CMSImport was a real life saver!
Structured Import ?
I realize in the free version I cannot use the structured import. So I can't really test this out. However, reading through the documentation on the Pro, I am a bit confused if I can import a tiered structure that has a 1000+ parent nodes and 5-20 child nodes under each parent.
Do I have to import the child nodes under each parent? Or is there a way in the definition to layout my xml data so it will import and create the child nodes accordingly?
I don't want to pay for the Pro, if I have to still do those manually. It would be nice if I can import the structure in the free on a really limited amount for testing for my desired purpose.
Thanks
Hi David,
The structured import will follow the structure of the datasource and will act on the Parent Child relations you specify when creating the Import definition in CMSImport via the GUI. Did you watch the video on http://www.cmsimport.com/ already? That shows how it is working. I'm using a sql server database in that situation but you can use the same for xml.
If you want to try it yourself please email me on richard[at] soetemansoftware.nl
Cheers,
Richard
Hi Richard,
I also have a quick question about structuring data imported from Excel files. I have an existing Forum that I plan to export to an Excel file and then import into Umbraco using CMSImport Pro. I would like to import the posts following nForum format like this:
-- Cateogry 1
------ 2011 (Category Folder)
---------- 09 (Category Folder)
-------------- Topic 1
-------------- Topic 2
So my plan was to first import all of the categories (top level), and then import the topics as children of the categories. However, how to I handle the intermediate category folders? Also, when specifying a primary key on import, where is this key actually stored in the document type? In your video, I noticed that you somehow were able to produce sub-categories in the catalog example but how did you do this? Is there somewhere that I can see the Excel file that you used in the video?
Thanks,
Ben
Hi Ben,
Great question. Normally you only have Category + Topic. I think the Year/date category folders are based on the created data, or some other date field in NForum. CMSImport PRO will still be able to determine the relation when the topic gets moved from the Category folder to a data category folder so you don't have to worry about that.
All information about the relations (Primary key Foriegn key) etc isn't stored in a document type. When installing CMSIMport a few relation tables are created and they do the magic. If you want to ahve a look at the Excel sheet. You can find it here
To make sure cmsImport can handle the Date category folders I would suggest you create a category in NForum and try to import some topics (can be dummy data). Then check if the Date category folders are created.If not please let me know.
Hope this helps you,
Richard
Ah, thanks very much for explaining that. You're right that the category folders in nFourm are just for organization and it doesn't really matter if they are left off. Since we don't have a huge amount of traffic, we will probably just import the topics directly under the category. However, what might be nice for a future version is to somehow be able to specify a different document type for the "recursive" import.
For example I could see that it might be very useful to have one document type called "Product Category", but then the children would be a lighter-weight "Product Category Folder" document type. Then, the products can be directly imported into either the folders or main categories after that. Again, we can live without this, but just a suggestion. Thanks for this great product... it will save us a lot of time :)
double post :(
HI Ben,
Think I didn't explain it correct. When you use the method I mentioned I think the event system of NForum automatically generates the other light weight category folders for so you get the topics nicely sorted into those light weight category folders. The event system of Nforum should take care of this, if not pelase let me know.
In case of the productcategory you mentioned I suggest you just use the recursive option where you can specify the key which maps to the parent category. As shown in the video. then the structure will build up itself based on that relation.
Hope this makes it more clear.
Cheers,
Richard
Hi Richard,
Oh, you're 100% correct... it does automatically create the date folders on import natively. I was just able to move over my entire nForums content to our new website including members and all. CMSImport was a real life saver!
Thanks,
Ben
is working on a reply...