node_import future directions

I know this is an aging thread now but nevertheless, all good suggestions above - I'd also love to see term hierarchy import incorporated too.

Whereas now, there is the ability to import multiple-select terms, given a field formatted:

multi-select
term1|term2|term3|

.. an option to preserve that same format but as an hierarchy.

Anyway, whilst I'm here, just wanna say a big thanks to Robert for taking-up the baton on this project - I consider this to be amongst the, 'should be in core' features, particularly as sites are getting larger these days thanks to bandwidth and hosts providing larger disk-space. Tools like this are going to grow in demand and users will naturally gravitate to those CMS's that provide it IMO.

Don't stop Robert ;)

I'm really interested in the XML import part of this, and the automatic refresh too, and it looks like others are willing to sponsor it...

Subscribing - this would be tremendous if it could be done

Here is another parallel thread of folks willing to $support this feature.

subscribing!
"Permit automated importing via a cron process" is something I am willing to pay for!

Subscribing.

Also interested in some sort of integration with User Import and import of user node profiles. Working on a hack now...

^{benjamin, Agaric Design Collective}

While everybody's wishing, it seems to me that the current process of defining which fields are available for node_import to use for each node type is a duplication of the views integration that every module worth it's salt has already done. The fields which are exposed for views to query are generally going to be the same fields node_import wants to be able to populate. Does anybody with views expertise have an opinion on whether it would be feasible to use this to get the list of fields in this way, and eliminate most if not all of the contents of the 'supported' folder?

It seems like the only other major function of the 'supported' files is field validation, and it looks to me like some love applied to _node_import_get_nodes() in node_import.module (see comments from line 624 on) would remove the need for this.

(4) export as CSV, XML

Just for the sake of completeness, I'll note that the Views Bonus Pack adds the Export view type - if you can build a View of it, you can export it as a CSV/XML(/DOC) file (either by using an argument or by setting the entire thing to "be" an export). I'm using this a lot.

Subscribing

kingandy is right. I've been doing this too. It can be tedious but it works great in many cases.

Not in 6.x - maybe in 7.x.