Changes between Version 43 and Version 44 of BluePrint/Importer

Timestamp:

01/22/11 14:14:29 (15 years ago)

Author:

Pat Tressel

Comment:

--

BluePrint/Importer

@@ -265 +265 @@
 Some notes and cautions:
 
-- Ideally the (internal) schema mapping will be "runnable" -- that is, it can
-  drive the extraction of data. Actually producing a state machine or similar is
-  likely overkill.
+- It would be convenient to have the (internal) schema mapping be "runnable" --
+  that is, able to drive the extraction of data. Actually producing a state
+  machine or similar is likely overkill. ;-)
 
 - Error handling and feedback must be done without user intervention -- this may
@@ -274 +274 @@
 - Need to provide error info in a machine-readable form.
 
+- The data may contain duplicates, or near duplicates. The spreadsheet importer
+  attempts to detect duplicates, and gathers them up for the user to decide on.
+  But because this may operate with no human do de-dup the data, we should
+  expect to find and deal with dups.
+
+- There may be missing data or malformed data -- again, error messages should
+  be in a machine-readable form.
+
+- Besides the repeated parent records that occur in an outer join, there may be
+  multiple records that can be recognized as refering to the same entitiy,
+  that each have partial information. It may be appropriate to merge / aggregate
+  these into more complete records. This should be part of the napping.
+
+- Need to handle security, e.g. is the source authorized to update or create
+  the tables / fields they're trying to act on?
+
 ----
 BluePrints