On our site we have a content type called product showcase. This content type was using to store information about products our company has certified. After awhile it became apparent that what I had developed wasn't good enough. We were constantly changing how the fields worked and things were getting sloppy.
So I started making a new content type on our beta site. This time I split one content type up into 3. One content type for vendor info and one for profile. The third content type would contain the info about the product and I used CCK reference fields to have it reference vendor and profile information.
After a lot of experimenting and adjusting, I got what I wanted.
So I have data for 100 or so products on our production site and I want to export the parts of the database that keep that info and move them to my beta site and be able to do field matching. The fields in the new content types don't have the same names but I don't want to have to manually imput all that data again.
Is there some way in the database that I can do this? Edit cells and tables?
I don't mind if I have to learn MYSQL but I have no idea what tables I need to modify or anything like that.
I do think fields like my image field and my certificate field, which are file upload fields might have to be imported manually but I'm not sure.
I know element feed mapper exists too but I have problems with it. I don't really understand how to use it that well. Last time I tried to use it for an event content type, all the dates and everything came over to my site in the field and I couldn't move everything into it's own field..
If someone could give me some kind of guide to doing this or maybe, has a better idea of how to achieve this, I would really appreciate hearing it.
Thanks,
Becky
Comments
Oh I should add that the
Oh I should add that the plan is to export my data from the production site to the beta site and once we have that going well, to then export it all back to the production site.
migrate
I would take a look at migrate http://drupal.org/project/migrate .
The migrate module works with views to import data into nodes. It's designed to work with TableWizard, but since your node data is already visible to views you probably won't need it.
Dylan, Could you give me
Dylan, Could you give me some instructions on how to use Migrate? I read this article here: http://civicactions.com/blog/2009/jul/25/migrating_your_website_drupal But I am confused on how to get my data from our existing production site into our beta site and into table wizard and migrate.
Becky
The manual approach might be faster
It sounds like you're making some good decisions with your new approach
Unles you already have the steps/solution for auto-converting the data wired, it will probably be faster to do this manually.
I say that because in the grand scheme of things one hundred (or even a few hundred) pieces of data is a relatively small number to convert. Once you get into the thousands, that is when automated data conversion starts to make a lot more sense.
If you do decide to take the automated approach, we would all appreciate you posting your recipe here for the group or, better yet, presenting it at one of our monthly meetings.
Good luck with the conversion.
Brian Gilday
Managing Partner
Aha Consulting
www.ahaconsulting.com
Brian Gilday
Municode
www.municode.com
Views Bonus/csv export/import
Use Views Bonus to export your existing data in csv format: http://drupal.org/project/views_bonus
Import your data using CSV Parser (my preferred choice) or Node Import (which is at a dev version; handle with care): http://drupal.org/project/parser_csv or http://drupal.org/project/node_import
Profit!
Dylan's suggestion of the Migrate module is also a good one, as is Brian's point about the relatively small dataset. The one factor in going for an automated solution for this is that hashing these details out expands your skillset with data migration on a manageable dataset.
Cheers,
Bill
FunnyMonkey
Click. Connect. Learn.
Using Drupal in Education
FunnyMonkey
Thanks for the tips! I'll
Thanks for the tips! I'll try them out when I'm back in the office Monday. I'll post back here if I have any problems or success.
Becky
OK. I installed Feed API,
OK. I installed Feed API, CSV Parser and the mapping module that goes with it... and I edited my content type to be a feed node type and enabled the csv parser and what not and then I went to "create content" and then I clicked on my content type and ....ta da! Got a blank page. A white page. Why? Why? Why?
I am totally clueless here. I disabled everything that I had just enabled and I still have the problem. Only for this content type so it must be linked to the modules. I don't know what though. I looked through the issue queue for each module and couldn't find a mention of this happening.
I really need some help guys. I hope someone has an idea of how to fix this......
Becky