Changes between Version 39 and Version 40 of BluePrint/Importer

Timestamp:

01/22/11 13:28:06 (14 years ago)

Author:

Pat Tressel

Comment:

--

BluePrint/Importer

@@ -126 +126 @@
 == CSV import ==
 
+This discusses only the back end of the CSV import, not the UI.
+
 === What sources and forms of data should we support? ===
 
@@ -141 +143 @@
 for self-cycles (a reference from a table to itself). Collections of records and
 their key references can also form a DAG. (There should not be cycles in the
-key references even if there are self-references within one table -- it is always
-possible to avoid cycles among records by using relationship tables that
-have outlinks to all the participants.)
+key references of records in the database, even if there are self-references within
+tables -- it is always possible to avoid cycles among records by using relationship
+tables that have outlinks to all the participants.)
 
 - A flat table -- one resource with no components or foreign key references.
@@ -220 +222 @@
   (or at least a couple of decades), and automation isn't reliable. If attempted, it
   should be done with the user at hand to verify it, so it would be done as part of
-  the UI. By the time the back end is called, we should have a schema mapping.
-
-==== Possible format and schema mapping representations: ====
+  the UI. (Just speculating: Could offer the user trial runs as they construct their
+  mapping -- let them do uploads of a few records and examine the result. Set ACLs
+  on the records so they're not visible to others. Back them out when the user is
+  done with them.)
+
+- In any case, by the time the back end is called, we should have a schema mapping.
+
+==== Options for format and schema mapping representations: ====
+
+//Under Construction -- need to enumerate the options and check what the spreadsheet
+importer is doing.//
 
 ----