Importing Existing Relationships

[ashwken]

I'm new to the program, and not entirly sure that this can be done, but before I spend hours on trial and error I thought I might pose this question:

How do I import an exisiting relational structure?

I have an external database (in Alpha5 simialr to MS-Access) consisting of individual entity tables, and various sets (table joins to create relational views).

The data can be exported to csv, I can create new joins (querys) for export purposes, and manipulate the tables prior to export. For example, add a field to hold a concatated value for mapping to UR-Item Title.

I have been able to import an individual table to a specific Folder using a Derived Template, so I've gotten my mind around some of the program.

I can't figure out how to import a parent-child AND have the child import as a linked item.

I think part of the procedure is described at this thread:

http://www.kinook.com/Forum/showthre...&threadid=1157

This mentions the addition of a field to the external table for mapping to UR-Indent Level (assign value of: 0=Parent, 1=Child). So that each row of the csv contains a value for Indent Level - does this mean that the import is accomplished in 2-passes, one pass to import the parent, then a second pass to import the children (???).

How should I handle (prepare) the external data tables for import porposes?

For example: if I "flatten" an external Parent-Child set, each row contains columns from the Parent (repeating data for rows of children) and unique Child columns. I don't see how to apply the Indent Level to this type of structure.

AND to the second part of my question - can an imported Child be assigned a Link value?

For example: after import, unique instances of Child items should become the source for future usage as linked (cloned) items - building new records.

Or, is it possible to export the UR-Item ID, or some other system fields to establish linkage externally, then re-import?

I guess my point is how should exisitng tables be structured (and/or joined) for export - import to UR.

Also, is there any point in creating Item Attributes for mapping the unique and forgein keys from the exisitng tables?

Any insight would be helpful.


KenA