Changes between Version 31 and Version 32 of BluePrint/Importer


Ignore:
Timestamp:
01/22/11 12:31:27 (11 years ago)
Author:
Pat Tressel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Importer

    v31 v32  
    180180=== Specifying the schema mapping ===
    181181
     182==== Assumptions and notes: ====
     183
    182184- If the data uses our formatting, we don't need a schema mapping -- we just need
    183185  to be told it's our formatting.
    184186
    185187- If the source has a schema that does not match ours, a means of mapping from the
    186   source's schema to ours will be needed (or will have to be inferred).
    187   (It is likely, for an existing major source, that we would write the schema mapping.
    188   For such a source, if we were receiving updates from them regularly, we would want
    189   to detect schema changes, or get notification of them.  But for a source we draw
    190   on regularly, there may be better means of pulling data than CSV files...)
     188  source's schema to ours will be needed.
     189  For an existing major source, it is likely that we would write the schema mapping.
     190  (But for a source we draw on regularly, there may be better means of pulling data
     191  than CSV files...)
     192
     193- If the spreadsheet importer developed for GSoC has a schema mapping representation
     194  that it either receives from the user or generates from having the user match up
     195  fields, we should be use the same one. Once past reading in the files and working
     196  with the user, the CSV and spreadsheet back-end processes should be equivalent.
     197 
     198- Inferring the schema mapping, or trying to, might be part of working with the user
     199  to establish the mapping. However, people have been working on this since forever
     200  (or at least a couple of decades), and automation isn't reliable. If attempted, it
     201  should be done with the user at hand to verify it, so it would be done as part of
     202  the UI. By the time the back end is called, we should have a schema mapping.
    191203
    192204