Changes between Version 52 and Version 53 of BluePrint/Importer
- Timestamp:
- 01/23/11 08:54:22 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrint/Importer
v52 v53 126 126 == CSV import == 127 127 128 //Under Construction ...falling...asleep...will continue when awake//128 //Under Construction// 129 129 130 130 This discusses only the back end of the CSV import, not the UI. … … 226 226 Besides the observed forms, please propose others that we want to support: 227 227 228 - (Comments please!)228 - //(Comments please!)// 229 229 230 230 ==== Which should we implement in the initial version? ==== … … 235 235 - (Pat:) Single file, outer join, allow lists in cells. 236 236 237 - (Comments please!)237 - //(Comments please!)// 238 238 239 239 === Specifying the file layout and schema mapping === … … 302 302 - For concatenated tables, what is the table separator? 303 303 304 - Is there a row with column names in the file, or are column names supplied 305 separately? 304 - Are columns specified (in the schema mapping) by name or number? 305 - If name, is there a row with column names in the file, or are column names 306 supplied separately? 307 - If number, is it 0-based or 1-based? 306 308 307 309 - Column separator? (Popular separators other than commas are tabs, semicolons, … … 322 324 ==== Schema mapping specification: ==== 323 325 326 Very broadly: 327 328 - For non-object cells, specify: (Sheet, column), Simple, Xform:<xform> -> (Eden table, field) 329 - For list cells (i.e. where the list contents are each added as a 330 separate record), specify: (Sheet, column), List, Xform:<xform> -> (Eden table, field) 331 - For object cells, specify: (Sheet, column), Object, Format:<format> (e.g. XML), 332 { (tag hierarchy, i.e. tag1:tag2:tag3...), Xform:<xform> -> (Eden table, field), ... } 333 334 Xform:<xform> is a transformation to be applied to the data. (E.g. if a name 335 in the primary table is to be used for its associated location, might want to 336 say "Location of <name>". Yes, I know that's not a good example. However, it 337 is one that has actually been done.) 338 339 For the user specification, if not entered via a UI form, we could ask for a 340 common format like XML, or something more human-readable. 341 342 - //(Suggestions for the user specification format?)// 343 344 - //(Comments, especially, what cases have been omitted?)// 345 324 346 === Implementation notes === 325 347 … … 329 351 330 352 - Extract the data into XML. 353 331 354 - Call S3Resource import_xml(). 332 355