Posted by webchick on July 27, 2006 at 12:43am
Jump to:
| Project: | User Import |
| Version: | master |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
The data I'm importing has lots of "s as well as newlines, so it would be cool to be able to specify an arbitrary delimiter and enclosure for CSV files.
Comments
#1
Would be good yes.
In the long run it would be better to hand the whole task of data input to a dedicated module like this one:
http://drupal.org/node/67043
That way other Drupal modules can use the data input functions, and then just concentrating on processing the data.
#2
Because http://drupal.org/project/profile_csv uses doubleqoute enclosures and semicolon delimiters and this module is the logical complement it would make much sense to at least support that format
#3
Fixing the title... must've been tired. :)
#4
I would really like a API module that just handles CSV import.
#5
I need this -- I'm trying to rebuild my drupal system to avoid some data corruption that may have occurred. My user data has to include commas, as it includes LDAP information. Am I going to have to import directly to MySQL?
#6
I've had to import fields with commas as well. I switched to a tab-delimited file and modified the module slightly. There are two calls to the function fgetcsv in user_import.module; if you make the third argument in each "\t", the module will break the file up by tabs instead of commas.
I've imported ~30,000 user records this way with no problems.
#7
Replacing to head as it could a significant feature... and subscribing
#8
Is there a better way of doing this (exporting and importing users) by now? I am looking at http://drupal.org/project/importexportapi but it doesnt mention users and seems not to be quite ready. Haven't tried though, so method described in this issue still seems to be a good idea?
#9
User Import 6.x-3.0-beta1 has support for custom delimiters.
Not sure if it covers all the requirements of this issue, if it doesn't please re-open it and give more detail.
#10
Automatically closed -- issue fixed for 2 weeks with no activity.