Closed (fixed)
Project:
ICES
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
13 Feb 2013 at 18:04 UTC
Updated:
12 Jun 2014 at 19:34 UTC
Jump to comment: Most recent, Most recent file
Import data from CSV files that CES exports. Build it in a separated module. We can add new fields to our database tables so more data can be imported from CES. Other fields may be ommited and lost.
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | testdata.tgz | 3.08 KB | esteve.badia |
Comments
Comment #1
hongpong commentedThis could probably be done by building up some kind of presets with the Migrate module. See http://drupal.org/project/migrate
"Migrate 2.6 beta1 is now available. The main theme of this release is UX - the existing UI has been significantly rearranged, and a new API has been introduced to allow other modules to easily developed wizard-style UIs targeted to non-developers." Nice!
Comment #2
esteve.badia commentedInteresting! Have in mind that the main goal of this issue is to import data from CES, though in future we could have to import an export from/to other platforms, o a generic approach like this sounds good to me. Moreover, I tried to have minimum dependencies (only to d7 core) for critical features, but for this kind of feature It seems right to me to get support from other projects if it really helps.
Fortunately, and administrator of a CES exchange group can download the database records in a CSV format. There are several files: users.csv, transactions.csv, offers.csv, etc.
I have access to these files because I'm currently administrating such a community, but I can't post them here because of privacy issues. Perhaps we should anonymize on of such set of files in order to have a public test suite. Do you find it really useful? Do anyone have an idea how such a thing is usually done?
The main thinks we have to import are:
Several thinks to take in count:
That's all that I have in mind now. The issue isn't easy and my explanation is neither clear nor exhaustive, but we are on it!
Comment #3
hongpong commentedthat is quite informative!! If you can create and make available some kind of smaller fake version of all the CSV files, with pseudo data in the same format, that would be excellent. Think like 50 lines for each file perhaps.
I think that using Migrate module should definitely suffice - would be much better to use migrate code than re-implement. However also, we should look at making an 'entity controller class' so that things like transactions can be dealt with as entities in Drupal. I have been researching this as I have not done it before.
Comment #4
esteve.badia commentedAttached file users.csv with the users database export from CES. Soon I'll try to add more csv with balances, transactions, offers, etc. But we can start working with this. Of course it is not real data. There are 25 fictitious CES user accounts.
Comment #5
edumag commentedComment #10
esteve.badia commentedComment #17
edumag commented