{"id":41,"date":"2017-02-17T12:42:31","date_gmt":"2017-02-17T12:42:31","guid":{"rendered":"https:\/\/www.threesl.com:2958\/blog\/?p=41"},"modified":"2017-05-10T15:34:47","modified_gmt":"2017-05-10T14:34:47","slug":"cradle-database","status":"publish","type":"post","link":"https:\/\/www.threesl.com\/blog\/cradle-database\/","title":{"rendered":"Contents of a Cradle database"},"content":{"rendered":"

Each Cradle database contains different sets of information. These can be imagined as layers, where each layer uses the data in the layers below it. For example, cross references cannot exist until the items exist whose relationships are shown by the cross reference. These layers are, highest to lowest:<\/p>\n

1. Cross references – the links between the data
\n2. Items – the data
\n3. Definitions – how to find, view and report the data
\n4. User profiles – who can own and access the data
\n5. Schema – the structure of the data
\n\"Cradle
\nYou can export\/import each layer individually, or in any combination, or all layers. You should only import a layer of information if the lower layers already exist in the database (unless you know that it is safe).<\/p>\n

To initialise a new database from an existing database, you need as a minimum:<\/p>\n

– The schema
\n– Definitions<\/p>\n

User profiles are needed to use a database and may be needed for some parts of the schema (such as workflows and alerts) and definitions (user and personal scopes).<\/p>\n