|
Importing and Exporting Tiles, NEs and Maps |
|
|
Tiles, NEs, knowledge maps and object models can be imported into and exported from the DNE. There are two reasons to export information. The first reason is to back it up, and the second reason is to send it to another DNE or to DNE Maps
Exports keep all the data and relations created in the DNE, as well as the files involved. Tiles, NEs and maps are exported DNE-ready, complete with contributions and affinities as well as fields and all other database information. Because exports include associations and fields and not just the files you are using, they preserve and present a far richer context than you could get with your files alone.
There are three options for exporting and importing DNE objects from and to the DNE. Each involves sending a different amount of information.
Exported information is copied to a folder in your DEKSTRUS\DNE\Backups folder.
A tile can be imported to the tile scroller of any NE in the DNE, in any room or in the cabinet. An NE or map can be imported to the cabinet, or to any association area of the active NE in any room.
When you export an object, you can choose whether or not you want to include unpublished information. This information includes fields for all objects, and associated NEs for maps and models.
When you import a map that was created in an object model, you can either preserve it as in that object model or you can turn the object model relations into repository relations or convert the map into any other model. In either case, the relations will remain the same. If you preserve it in the model in which it was built, but you do not have that model in your DNE, the DNE will add the model to your repertoire.
Bringing folders and files into the DNE either by Microsoft® Explorer® or by the DNE explorer is not an "importing" process. It is done differently:
|