About Classification

Oracle Life Sciences Data Hub classification system allows you to define a set of labels and use them to label, or classify, every defined object, output, and visualization in Oracle LSH.

Users can search and browse for an object or output by its classifications.

The classification system consists of a set of hierarchies. A hierarchy can contain multiple logically related levels (such as Project/Study/Site) where the values, or terms, defined for each level are logically related to a single term in the next higher level (for example, the site Mercy Hospital is related to its study, Study01, which is related to its project, Project Wonderdrug.) an Oracle LSH"hierarchy" can also consist of a single level, in which case its terms function as a list of values.

Classification brings order to the potentially huge number of defined objects and outputs contained in the Life Sciences Data Hub. The Outputs and Visualizations subtabs under the Reports tab display reports, submission forms, and visualizations according to the classification hierarchies you define and the classification terms that Definers assign to outputs, similar to the file system on a PC.

For example, in the Reports tab a user can click on the Project/Study/Site hierarchy. Oracle LSH then displays all the project names defined as terms in the Project hierarchy level. If the user clicks on Project Wonderdrug, for example, Oracle LSH displays folders for all the studies that are part of the Wonderdrug project (including Study01) and also all the reports that are classified to Project Wonderdrug as a whole. If the user clicks on Study01, Oracle LSH displays folders for all the sites that are part of Study01 (including Mercy Hospital) as well as all reports that are classified to Study01 as a whole. If the user clicks on Mercy Hospital, Oracle LSH displays all reports classified to Mercy Hospital.

Further information is available in the Oracle Life Sciences Data Hub Implementation Guide.

You must create the following:

• Hierarchies. A hierarchy consists of one or more named levels in a strict linear hierarchical order. Each level can have only one child level. You can define any number of levels.
• Hierarchy Levels. Each hierarchy must include at least one level. If a hierarchy has multiple levels, they must be logically related. For each object subtype, you must specify at least one hierarchy level to which objects of that subtype can be classified.
• Terms. A term is a specific value belonging to a hierarchy level. In each hierarchy level you must add meaningful terms to assign to objects. In a multilevel hierarchy, each term must be logically and definitionally related to a term in the level above. When a Definer assigns a term to an object, the object is classified to that term and users can search for the object by its classification.

You can add classification hierarchies and values at any time. For more information, see Required Role.

This section contains the following topic:

• Required Role
  You must have the Classification Administrator application role to access any of the screens under the Classification tab in the user interface and to perform any of the tasks covered in this section.