Managing large number of nodes
polebia - August 3, 2009 - 12:51
I'm not sure if this should be posted here or in a more general discussion forum but here it goes.
I would like to create a bibliography database within my drupal website. The bibliography has between 5-10 fields and will have over 300 entries. Does it make sense to publish this as 300 separate nodes and a new content type or to use a seperate database that just receives use queries and displays that information using php.
It seems like having 300 separate nodes is a messy way to handle it on the back end even though quite a lot of functionality can be added to each individual node (keywords, tags, links, etc)
What are peoples experience with managing drupal sites with large numbers of nodes and content types?
Thank you!
300 nodes isn't a large
300 nodes isn't a large number by any means, and from what you've said here you'll only need one content type (albeit with several fields).
You should definitely go with one node per record. Keeping the information in a separate database will make it impossible to use other modules such as CCK and Views - in which case there's little point in using Drupal.
Bibliography Module
Drupal has a biblography modules which you should check. It may be exactly what you need and will save you a lot of time in setting up custom CCK fields.
Thanks!
Should have known someone already created a module for this!
300 is nothing
I personally know of "Biblio module" installations which have in excess of 30,000 entries, so not to worry about 300.