Add support for Storm content types to node_import.module

OK, have kicked this off - pretty painless actually, which is a good sign. Have added Storm Organisation support now, I expect to get onto invoice and invoice item support pretty shortly.

To add this code to node_import, extract the attached tarball in modules/node_import/supported so it creates the new directory modules/node_import/supported/storm

This code will ultimately need to be added to node_import module, but I'm keen to keep it in the Storm issue queue until we're ready to provide the support files to that module, then transfer the ticket / code over.

Because our use case is importing an existing system with its own keys for organisation, invoice, invoice item etc, I've added CCK fields in my site to map these. For our import we'll need to post-process these to map the items to the correct new invoice, organisation, etc. This last probably won't be part of the first release of node_import support, but I'll document the process we used, because I'm sure it'll be useful for others looking at moving to Storm.

I have added support for import stormperson. just unpack tgz file in modules/node_import/supported.
It is working, but not perfectly, there are some errors, and manually choosing organization_nid field - but it is possible to import organizations and people very easy. This code only uses very basic node_import functionality, for more advanced features I would need to get deep into node_import module - so any example (some other module, some other code) would be great.

I do not suggest to run this on production site, but you can test it on backup and development sites.
This is enough for me to satisfy mine current needs, but I would like to finish this import thing - just don't know when exactly.
If someone have any suggestion/code/example post here.

Other important thing are examples of .csv files, And I will post them here as soon as I make them.

My use case was to enable the imporation of Organizations and then import Persons, linking them to the pre-existing Organization.
I investigated using the node_import node_reference type, however this is specific to the CCK node_reference and didn't seem to work with the basic node reference in storm. So I altered the node_import.inc to add another field type for basic_node_reference. This is used to set the organization_nid when provided with the organization_title. So in your csv you can specify the Organization title and the code will find the pre-existing node reference and put this in the organization_nid.

Attached is a patch to apply to node_import.inc and the two include files to put in the node_import/supported/storm directory are in the zip file