Is it possible to import an entire book hierarchy from CSV files? I see that there is a supported/book.inc file, which declares a column 'plid' for the parent item. But I'm not sure how this is to be used. Does anyone have an example of a file that can be imported which uses this column?

Is it necessary to put a node id in the plid column? I'm trying to import all the hierarchy at once, so my file doesn't know any drupal node ids, just the titles of the nodes created by it.

Again sorry if this is a FAQ I haven't seen any detailed docs.

Comments

frank ralf’s picture

frank ralf commented

Download the version for Drupal 5. There's more documentation on the inner workings of the module and also test files for all the supported node types.

HTH
Frank

PS:
You might also have a look at http://drupal.org/node/207738 regarding the status of the D6 port.

Robrecht Jacques’s picture

Robrecht Jacques commented

Version 6.x-1.x-dev doesn't do anything yet.

Version 5.x-1.8 can import complete book hierarchies. You can put the nid or the title of the node in the parent column.

HansBKK’s picture

HansBKK commented
Title: import entire book hierarchy » import data set as hierarchy - URL aliases, menu tree
Category: support » feature

As an alternative to book, have a look at what Node Hierarchy does. When (manually) creating nodes, it lets you to create a hierarchy - node x is parent of y and z results in both URL aliases and menu items for the nodes matching up.

Then later you can Ajax shuffle the hierarchy and the aliases and menu items all stay in sync.

Turn off the module and it all stays in place, everything is native menu and url path hierarchy, but effectively lets you set up "just like a book" but with any (mix of) node types.

So (coming to a point here I promise)

what if

I could set up my CSV data file with a "hierarchy" field structured like this

. . .","about/mission and vision",". . .
. . .","about/facilities/fine arts",". . .
. . .","about/facilities/music",". . .
. . .","about/facilities/computers",". . .
. . .","about/facilities/sports",". . .
. . .","about/facilities/drama",". . .
. . .","about/staff",". . .

and my menus and path aliases get automagically created at node import time?

I think this would add incredible usability for noobs getting started on creating their corporate brochure site, ideally combined with a suitable installation profile.