Glossary

The following terms and concepts are used to describe software objects, features, and functionality across the CoBaseKRM application environment.

Term or Concept	Definition
archive function	inactivates certain objects and their metadata and removes them from active use, such as projects, network maps,and nodes. Archived objects are undiscoverable through the Search view. Archived objects can be restored to active use by an administrator role or lab manager role.
audit log	a security and compliance feature for recording historical details of significant user actions and system events. The audit log is supporing documentation to demonstrate an organization's adherence to industry regulations.
branch node	See node.
bulk export function	a function in the web client for bulk exporting a list of parameter names and their metadata from the database to an Excel file or CSV file
bulk import function	a function in the web client for bulk importing a list of parameter names and their metadata in an Excel file to the database
connector	a connecting line between two nodes within a network map to indicate an existing relationship between observations, data tables, and project activities of the connected nodes
data retention period	a configurable setting for how long archived objects are stored before they are deleted permanently. The supported periods for archived objects are: Indefinitely - indefinitely stored and no defined permanent deletion date 7 years after the archived date 3 years after the archived date 90 days after the archived date 30 days after the archived date
data type	specifies what type of data values are valid for a parameter. The supported data types are: Numeric - continuous numerical values which can be expressed with integers, decimal values, and floating point data. It allows for use with mathematical operations, such as addition, subtraction, and logical comparisons, as well as formulas. Character - string values that contain alphanumeric characters, punctuation, etc. DateTime - string values that contain date and time parts, such as year, month, day, hours, seconds, as a timestamp or representing an instant in time (see date format)
date format	a property of the DateTime data type that defines a preferred display format for date and time values in the web client and JMP add-in for CoBaseKRM
delete function	removes an object and its metadata from active use. Only certain objects are allowed to be deleted, namely projects, network maps, nodes, templates, domains, parameters, . Deleted objects cannot be recovered and are not discoverable by using the search function. See also delete permanently.
delete permanently function	deletes objects permanently from the database such that they cannot be recovered. An audit entry records a permanently deleted object with a timestamp in the Audit Log. Permanently deleted objects are not discoverable through the Search view. However, references to relationships of permanently deleted objects with other objects are preserved. See also delete.
design of experiments	a branch of applied statistics that deals with planning, conducting, analyzing, and interpreting controlled tests to evaluate the factors that control the value of a parameter or the values of a group of parameters. See also parameter, factor, and response.
domain	an object for categorizing parameters. Domain objects can be related to each other by parent-child relationships in a domain hierarchy.
electronic signature	an optional feature in data governance for collecting electronic signatures from users before allowing key user actions to be completed in the web client. Supports audit reporting for organizational compliance with 21 CFR Part 11 regulations.
export function	exports a data table in either Excel format or CSV format from the database, using either the web client or JMP add-in for CoBaseKRM
factor	a parameter that controls the value of another parameter or the values within a group of parameters. See also response.
journal card	a feature for recording notes in discussion threads about data tables and other significant artifacts. Supports WYSIWYG text formatting, hyperlinks, images, and mentioning users.
leaf node	See node.
model management	a method of managing predictive models and their training sets, and applying version control to model changes
modeling type	defines how CoBaseKRM will handle parameter values in analyses. Only parameters having the numeric data type and character data type can be defined with a modeling type, as further described below: Continuous - parameter values defined only with the numeric data type are treated as continuous measurement values. Nominal - parameter values are treated as discrete and unordered Ordinal - parameter values are treated as discrete, categorical values that have a given order. If a parameter has the numeric data type, the values are ordered according to their numeric magnitude. If a parameter has the character data type, its values are ordered alphanumerically.
network map	an object map for visualizing a project's research and experimentation activities, related data tables, and other important data artifacts
node	an object within a network map that visually represents a research or experimentation activity. A data table of observations and other supplementary files can be associated to a node. A template can be assigned to a node to help in harmonizing parameters names within a data table with existing parameter names in the database. The supported types of nodes are: branch node - the first node of a branch that forks from the main branch of a network map leaf node - a node within
node category	one of a set of predefined, default categories for classifying nodes according to a node's purpose within a project, namely Hypothesis (activities and/or tasks and data related to a hypothesis of a project), Experiment (activities and/or tasks, data, and other files related to experiments for a project), Conclusion (activities and/or tasks and data related to a conclusion of a project ), and JMP (JMP data tables and other files and other relevant information that are specific to the JMP add-in for CoBaseKRM)
observation	a set of numeric values for parameters of interest, which are measured or counted during a study or experiment
original data table	a status in the JMP add-in for CoBaseKRM to indicate an original version 1 of a version-controlled, uploaded data table in the JMP add-in for CoBaseKRM
parameter	an object to define a specific quantifiable or measurable aspect of a variable through certain characteristics or properties. A paraemter can be defined with a given data type and modeling type (see also data type and modeling type).
project	a set of research and experimentation activities and tasks with a specific objective, for example, product quality research and development, research studies, etc. A subproject is a child project and can represent a specific phase, activity, task, or other aspect of a project that is tracked as a dependent entity to a parent project
record	a row or collection of fields containing object details and metadata for a user-performed action or a system-executed action
reconstructed data table	a status in the JMP add-in for CoBaseKRM to indicate a version-controlled primary data table, whose version is higher than 1
response	A desired output resulting from multiple input factors that have been skillfully used in a design of experiments. See also factor.
restore parameter function	restores deleted parameters to the Data Governance > Parameters tab in the web client for active use across the entire application
supplementary file	a status in the JMP add-in for CoBaseKRM to indicate a supporting data table or other type of file that is adjacent to the primary data table in relation to a node. A supplementary file is not upversioned if it is downloaded from and uploaded once again to the database.
tag	a metadata tag that is assigned to objects, such as files, models, and journal cards, so that those objects can be filtered in an object list and discoverable through a search
tag type	type classification for tags
template	a defined set of existing parameter names that is used to help in harmonizing parameter names in a data table for upload with existing parameter names in the database. A project-level template is assigned at the project level and assigned by default to a related node, but a user can change it, if desired. A node-level template is assigned independently to a node and can be different from an assigned project-level template.
workspace	an access-controlled, collaborative work area within a CoBaseKRM application environment. A minimum of one workspace is required in a CoBaseKRM application environament The switch workspace function enables you to switch from working within one existing workspace to another.