I have several CSVs with thousands of lines - book biblio data and locations/street addresses. I'm debating whether I should import them to nodes using the Feeds module or just allow users to query the CSV and only then create nodes should there be matches. Am I being overly cautious thinking that feeding in and creating thousands of nodes via Feeds as being too resource intensive?
I don't want an unnecessarily weighty website if possible.
Maybe I'm seeing this wrong, but an individual node seems rather "chunky" when looking at the same data as a single line in a CSV.
Is it possible to upload the CSV, storing as entries in as lightweight method as possible, and have them be indexed and queired via Drupal, but then have matches converted to nodes via Rules? Perhaps refort CSV lines with Views rather than as individual nodes. Partof me tells me nodes may be overkill.
I'm really just wondering if prepopulating is better or whether create-on-the-fly is better, if at all possible.
Thanks
Comments
I would import as nodes.
I would import as nodes.
---
I would just get it over now and import as nodes. You don't want to do stuff like that on the fly.
I see what you're saying, if
I see what you're saying, if I upload and create nodes at once, it'll be a one time thing. Any idea how long or how intensive it would be to generate ~5000 nodes composed of 6 text fields?
And back to my original thoughts, is there a way I can upload a CSV that can be queried and then have query matches then created as nodes?
Given my CSV content type - book biblio data and locations/street addresses, is a node the right approach or would Content Taxonomy module make more sense? I'll definitely be requiring node references in the future with the data, mind you.
Thanks
Make it easy on yourself, use
Make it easy on yourself, use a content type.