Quote:
Originally Posted by Parody
RW's XML setup lets LWD define how you can tell Realm Works what each piece of data means. That allows interested folks to write the glue that goes between some set of data and how they want it to appear in RW. This flexibility comes at the cost of ease of use for the person who has to write the glue and perhaps for those using the results.
|
This mostly. Because in the CSV you might have a column which needs mapping to a tag, and another column which might be a comma-separated list of values (like classes) which needs mapping to one or more tags for that single field.
There are other columns where you need the plain text, and other fields where maybe you need a tag for the basic data but also need an annotation added to appear next to the tag.
The number of cases is so vast that no single tool could possibly provide this import capability without a mass of options to select between. For this reason, the task may as well be left to a separate tool (or collection of scripts) to perform this task.
(Note that exporting a CSV from Excel as XML doesn't work very well, since it cheats when skipping blank cells in the grid making it more difficult to parse the resulting XML.)