Changes between Version 52 and Version 53 of BluePrint/Importer

Timestamp:

01/23/11 08:54:22 (14 years ago)

Author:

Pat Tressel

Comment:

--

BluePrint/Importer

@@ -126 +126 @@
 == CSV import ==
 
-//Under Construction...falling...asleep...will continue when awake//
+//Under Construction//
 
 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:
 
-- (Comments please!)
+- //(Comments please!)//
 
 ==== Which should we implement in the initial version? ====
@@ -235 +235 @@
 - (Pat:) Single file, outer join, allow lists in cells.
 
-- (Comments please!)
+- //(Comments please!)//
 
 === Specifying the file layout and schema mapping ===
@@ -302 +302 @@
 - For concatenated tables, what is the table separator?
 
-- Is there a row with column names in the file, or are column names supplied
-  separately?
+- Are columns specified (in the schema mapping) by name or number?
+ - If name, is there a row with column names in the file, or are column names
+   supplied separately?
+ - If number, is it 0-based or 1-based?
 
 - Column separator? (Popular separators other than commas are tabs, semicolons,
@@ -322 +324 @@
 ==== Schema mapping specification: ====
 
+Very broadly:
+
+- For non-object cells, specify: (Sheet, column), Simple, Xform:<xform> -> (Eden table, field)
+- For list cells (i.e. where the list contents are each added as a
+  separate record), specify: (Sheet, column), List, Xform:<xform> -> (Eden table, field)
+- For object cells, specify: (Sheet, column), Object, Format:<format> (e.g. XML),
+  { (tag hierarchy, i.e. tag1:tag2:tag3...), Xform:<xform> -> (Eden table, field), ... }
+
+Xform:<xform> is a transformation to be applied to the data. (E.g. if a name
+in the primary table is to be used for its associated location, might want to
+say "Location of <name>". Yes, I know that's not a good example. However, it
+is one that has actually been done.)
+
+For the user specification, if not entered via a UI form, we could ask for a
+common format like XML, or something more human-readable.
+
+- //(Suggestions for the user specification format?)//
+
+- //(Comments, especially, what cases have been omitted?)//
+
 === Implementation notes ===
 
@@ -329 +351 @@
 
 - Extract the data into XML.
+
 - Call S3Resource import_xml().