94 | | Should we have a wrapper function for this which is easily accessed from the CLI? |
95 | | |
96 | | Rationale: |
97 | | * People could create their own "Deployment" pre-populate directories with unique (& contextual) data which could be used to easily create simulations. ( And be a great GCI task ) |
98 | | * We should separate csv from xsl (xsl could very easily confuse semi-technical users) |
99 | | * CSV templates should be easily downloaded - prepopulate data should not (always) be |
100 | | * All XLS should be in trunk (even if it is for private data) and have a matching CSV Template |
101 | | * Then a configuration file can be created where you can just list the CSV file names which you want to be imported when Sahana Eden is initialized. Copies of this files could be saved in the private/templates/<deployment>/ directory then a config setting could select which file to use, to make it easy to set up Sahana Eden to have different types of data in it. |
| 95 | Also see [wiki:S3/DataImportCLI S3/DataImportCLI] |