For example if you want to add a URL<\/em> to your item, there is no point trying to store the data inside Cradle this is, by its very nature, an As Reference storage type<\/em>. On the other hand a binary<\/em> word processor document could easily be stored inside the Cradle Database<\/em> or as a reference to an external file<\/em> on the rest of the company’s network. In this case it could depend whether the file needed to be accessed from outside Cradle<\/em> or whether it was shared by multiple Cradle<\/em> projects<\/p>\n Within an item data is either held in the main indexed database fields, such as ID, name, key<\/em> or a category<\/em>, or in associated frames<\/em>. These frames are defined as part of the project’s schema<\/em> to hold different types of data. There are a large number of predefined types and the ability to define your own.<\/p>\n These are the fundamental type\u00a0 of data we expect to see in the frame<\/em>. They may be presented in different ways to the user. For example a plain text<\/em> based frame can be shown in Forms<\/em> and Views<\/em> and read directly on the screen. The same is true for basic images<\/em>. However, a word processor document is held as a binary frame<\/em> and viewed within whichever application your company uses. A CAD sketch would not be directly visible in Cradle, but could still be stored in the item and viewed with an external program.<\/p>\n These are the fundamental and abstract data types offered in Cradle<\/p>\n Each of the above types can be stored in Cradle in one or more ways. Some storage in Cradle, such as a date, make no real sense to store in more than one manner, the URL as mentioned or a date would not make sense to be stored in a file!<\/p>\n This shows the combinations of base type and storage in Cradle that are possible. More information in Cradle help<\/a>.<\/p>\n \u2714<\/span> Frame data stored in the database is inherently linked to the database item that owns it. It is controlled in the same way as all the other fields of data (name, category, group, description, etc.). This means it can be imported and exported as part of the item. Text frames can form part of a query. Images, text and RTF can be displayed in-line. They move through the CM (configuration management) system with the item. Different revisions of the frame form part of the item’s history, and can be rewound. \u2714<\/span> Frame data stored in a file is loosely linked to the item that owns it. Date and access times are remembered by Cradle so changes to the file can be highlighted. Great for large files. Other users can access the information externally to Cradle if they have access to a common file directory. Can be accessed through Cradle and item is locked while file is being edited as if it were part of the item. \u2714<\/span> Frame data is held in an external environment under an identity, the item stores this identity, and uses Get<\/em> and Set<\/em> commands to move the data between the environment and a temporary file where it can be operated on. \u2714<\/span> Frame data stored anywhere and only loosely linked to the database item. Ideal for large resources such as Intranet pages. Ideal for information that is expected to change outside Cradle and be accessed by others. Cradle does not wait when viewing or editing. \u2714<\/span> Frame data is held in a frame of a different item whose identity (PDUID and frame name) is stored in the current item. When the frame is accessed via a View<\/em> the user is editing the common shared data held by the referenced item. This provides a method of reuse, allowing multiple items to directly access a data component of a different item. The ‘host’ item and the frame data follow normal CM operations. In this example of storage in Cradle, a frame will be set up to hold a word processor document, internally (in pdb)<\/em>, in a file (as file),<\/em> and in another item (referenced file from item)<\/em>.<\/p>\n First set up a set of frames for each storage type and set commands on how to view and edit the file.<\/p>\n Ensure the items you want have these frames assigned. In this example the Feature has all three types and the Reference item has just the stored in pdb.<\/p>\n When the file types are set up the data can be imported into the item using the frame button and import Content…<\/strong> this brings the document into the item and it can be stored in the database. It can then be viewed and edited from the same button. In this illustration the Design Notes<\/em> and Legal Requirements<\/em> and have been stored in in this way.<\/p>\n The Company Design Standards<\/em> are held in one directory for every project to access. The illustration links to this as file<\/em> from where it can be viewed or edited.<\/p>\n Finally the Reference<\/em> item holds the Legal Requirements <\/em>document so that it is under formal control. However, other linked items can access this file directly, without having to open the holding item. Their frame is an alias for the data held by the other item.<\/p>\nFrames<\/h3>\n
Base Types<\/h3>\n
\n
Storage Types<\/h3>\n
\n
![\"setting](\"https:\/\/www.threesl.com\/blog\/wp-content\/uploads\/2018\/03\/Frame_type_details.png\")
Storage Matrix<\/h4>\n
\n\n
\n <\/td>\n In PDB<\/td>\n As File<\/td>\n By Command<\/td>\n As Reference<\/td>\n Referenced File from Item<\/td>\n<\/tr>\n \n Text<\/td>\n \u2713<\/td>\n <\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/tr>\n \n Binary<\/td>\n \u2713<\/td>\n \u2713<\/td>\n \u2713<\/td>\n \u2713<\/td>\n \u2713<\/td>\n<\/tr>\n \n Image<\/td>\n \u2713<\/td>\n \u2713<\/td>\n \u2713<\/td>\n \u2713<\/td>\n \u2713<\/td>\n<\/tr>\n \n URL<\/td>\n <\/td>\n <\/td>\n <\/td>\n \u2713<\/td>\n <\/td>\n<\/tr>\n \n Category Picklist<\/td>\n \u2713<\/td>\n <\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/tr>\n \n Category Multiple Picklist<\/td>\n \u2713<\/td>\n <\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/tr>\n \n RTF<\/td>\n \u2713<\/td>\n \u2713<\/td>\n \u2713<\/td>\n \u2713<\/td>\n \u2713<\/td>\n<\/tr>\n \n Date\/Time\/Integer\/Positive Integer\/Real<\/td>\n \u2713<\/td>\n <\/td>\n <\/td>\n <\/td>\n <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n Benefits and Usage<\/h3>\n
In PDB (Project DataBase)<\/h5>\n
\n\u2717<\/span>Not ideal for very large data, e.g. video. Not externally accessible.<\/p>\nAs File<\/h5>\n
\n\u2717<\/span>Not directly controlled within Cradle, nothing to prevent the external file being removed or deleted. Can’t be rewound.<\/p>\nBy Command<\/h5>\n
\n\u2717<\/span>Not directly controlled within Cradle, nothing to prevent the external file being removed or deleted. Can’t be rewound.<\/p>\nAs Reference<\/h5>\n
\n\u2717 <\/span>This is not considered storage in Cradle so there is no CM or rewind available. No control over alterations.<\/p>\nReferenced File from Item<\/h5>\n
\n\u2717<\/span>Not ideal storage in Cradle for very large data, e.g. video. Not externally accessible.<\/p>\nSetting Up a Frame Storage in Cradle<\/h2>\n
Frame Setup<\/h3>\n
![\"Setting](\"https:\/\/www.threesl.com\/blog\/wp-content\/uploads\/2018\/03\/Frame-Setup.png\")
Frame Assignments<\/h3>\n
![\"Assigning](\"https:\/\/www.threesl.com\/blog\/wp-content\/uploads\/2018\/03\/Storage_assignments.png\")
Usage<\/h3>\n
![\"the](\"https:\/\/www.threesl.com\/blog\/wp-content\/uploads\/2018\/03\/Storage_Illustration.png\")