When a lesson is started, the authored design is considered the orginial learning design Unique signature for each version of a tool. <organisation><tool><version> Unique identifier for the tool. This should remain the same for every version of the tool. It will be used for the IMS LD import/export. Version of tool. Expected to be in format [major version.minor version] eg 1.2 There will usually be 0 or 1 workspace for each tool in LAMS, so this should be a pretty small table. The main lookup is done on name, but given the small number of rows a complete table scan should be fine. A name index would probably be about the same size as the table anyway. Like lams_cr_workspace, there will usually be 0 or 1 workspace for each tool in LAMS, so this should be a pretty small table. The main lookup is done on name, but given the small number of rows a complete table scan should be fine. Has a "dummy" id nv_id (node version id) which is unique for all node_id and version_id combinations. It is the node_id and version_id combination that is the "real" key for this table. A node can only belong to one parent - so each time a new version of a package is created, all the nodes are recreated. All the lams_css_property values matching this lams_css_style make up the CSSStyleDeclaration for this style. It may be a "base" style for a theme, or it may be for a named visual element. Each style may have a subset of properties, such as "_tf" Url details for system tools such as gates and grouping Unique signature for each version of a tool. <organisation><tool><version> Individual permissions, such as read access to a content folder. Link table between lams_role and lams_privilege.