You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: site/docs/concepts/collection.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ Home collections are used to organize elements for a particular person, team, pr
39
39
40
40
Collections can be used by automated services, typically [governance services](/concepts/governance-service), to gather the results of their processing together. Such a collection would have the *ResultsSet* classification attached to it.
41
41
42
-
For example, the results set collection shown below is from a governance service that is identifying assets that should be archived (for example, by reviewing their [Retention](/types/4/0422-Governance-Action-Classifications) classification).
42
+
For example, the results set collection shown below is from a governance service that is identifying assets that should be archived (for example, by reviewing their [Retention](/types/4/0422-Governed-Data-Classifications) classification).
Copy file name to clipboardExpand all lines: site/docs/guides/planning/governance-program/governance-program-planning.drawio
+5-8
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
<mxfile host="Electron" modified="2023-11-17T13:22:37.333Z" agent="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) draw.io/21.6.8 Chrome/114.0.5735.289 Electron/25.5.0 Safari/537.36" etag="gVbaf2clTMyOt-k-hYU1" version="21.6.8" type="device" pages="7">
1
+
<mxfile host="Electron" agent="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) draw.io/26.0.9 Chrome/128.0.6613.186 Electron/32.2.5 Safari/537.36" version="26.0.9" pages="7">
> Examples of different governance domains within an organization.
41
41
42
-
Governance domains are represented by [*Governance Domain Descriptions*](/types/4/0401-Governance-Definitions/#governancedomaindescription) entities in open metadata. They are organized into a *GovernanceDomainSet* collection.
42
+
Governance domains are represented by [*Valid Value Definition*](/types/5/0545-Reference-data) entities in open metadata. They are organized into a *ValidValueSet* collection using the [Valid Metadata Values](/guides/planning/valid-values/overview) services.
> The governance domain descriptions organized in a governance domain set
45
+
> The governance domain descriptions organized in a valid value set under the `domainIdentifier` attribute
46
46
47
-
The governance domain descriptions include the *domainIdentifier* property, a *displayName* and a *description*. The *domainIdentifier* property is an integer and by convention "0" means "applies to all domains". For example:
47
+
The governance domain descriptions include the *preferredValue* for the *domainIdentifier* property, a *displayName* and a *description*. The *domainIdentifier* property is an integer and by convention "0" means "applies to all domains". For example:
48
48
49
49
| Domain Identifier | Display Name | Description |
@@ -59,9 +59,7 @@ The governance domain descriptions include the *domainIdentifier* property, a *d
59
59
60
60
61
61
??? education "Defining governance domains"
62
-
Governance domain descriptions can be defined in an [Open Metadata Archive](/concepts/open-metadata-archive) or through the [Governance Program OMAS](/services/omas/governance-program/overview).
63
-
64
-
The [egeria-samples.git repository](https://github.com/odpi/egeria-samples) includes a sample called [Sample metadata archives for Coco Pharmaceuticals](https://github.com/odpi/egeria-samples/tree/main/sample-metadata-archives/coco-metadata-archives) that creates open metadata archives with basic definitions for Coco Pharmaceuticals. This includes the definition of this organization's governance domains with their communities and governance officers.
62
+
Governance domain descriptions can be defined in an [Open Metadata Archive](/concepts/open-metadata-archive) or through the [Valid Metadata OMVS](/services/omvs/valid-metadata/overview).
65
63
66
64
## Governance Leadership
67
65
@@ -96,7 +94,7 @@ These different approaches allow you to have enough detail in your open metadata
The [Governance Program OMAS](/services/omas/governance-program/overview) supports the setting up of governance roles. The [Community Profile OMAS](/services/omas/community-profile/overview) supports the appointment of people to roles.
97
+
The [Governance Officer OMVS](/services/omvs/governance-officer/overview) supports the setting up of governance roles. The [People Organizer OMVS](/services/omvs/people-organizer/overview) supports the appointment of people to roles.
100
98
101
99
102
100
## Governance Leadership Communities
@@ -196,9 +194,10 @@ The organization of the subject areas is orthogonal to the governance domains. S
196
194
* [Setting up the subject area definitions :material-github:](https://github.com/odpi/egeria/tree/main/open-metadata-resources/open-metadata-samples/access-services-samples/governance-program-client-samples/governance-subject-area-sample){ target=gh }
197
195
* [Setting up glossary categories for each subject area :material-github:](https://github.com/odpi/egeria/tree/main/open-metadata-resources/open-metadata-samples/access-services-samples/subject-area-client-samples/subject-area-definition-sample){ target=gh } ready for subject area owners to start defining glossary terms associated with their subject area.
198
196
199
-
* The [Governance Program OMAS](/services/omas/governance-program/overview) supports the setting up of subject area definitions.
200
-
* [Digital Architecture OMAS](/services/omas/digital-architecture/overview) supports the definition of reference data and quality rules for the subject area.
201
-
* [Asset Manager OMAS](/services/omas/asset-manager/overview) supports the management of glossaries and the exchange of subject area information with other catalogs and quality tools.
197
+
* [Governance Officer OMVS](/services/omvs/governance-officer/overview) supports the setting up of subject area definitions.
198
+
* [Reference Data OMVS](/services/omvs/reference-data/overview) supports the definition of reference data for the subject area.
199
+
* [Data Designer OMVS](/services/omvs/data-designer/overview) supports the definition of quality rules for the subject area.
200
+
* [Asset Manager OMAS](/services/omvs/asset-manager/overview) supports the management of glossaries and the exchange of subject area information with other catalogs and quality tools.
202
201
203
202
## Governance classification, tagging and linking
204
203
@@ -229,7 +228,7 @@ The labels may be assigned directly to the asset, or to elements, such as schema
229
228
230
229
## Setting up the levels for your governance classifications
231
230
232
-
The values used in governance classifications show the specific group that the classified asset belongs to. Often an organization has their own levels defined, and they can be set up in [`GovernanceClassificationLevel`](/types/4/0421-Governance-Classification-Levels/) definitions.
231
+
The values used in governance classifications show the specific group that the classified asset belongs to. Often an organization has their own levels defined, and they can be set up using the [valid metadata values](/guides/planning/valid-values/overview) definitions.
Copy file name to clipboardExpand all lines: site/docs/patterns/metadata-manager/categories-of-metadata.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ The categories of metadata listed below help you organize your metadata needs ar
54
54
* [Reference data](/types/5/0545-Reference-Data) describing valid values and mappings for data values,
55
55
* [Technical controls](/types/4/0430-Technical-Controls) defining quality rules and processing rules - such as anonymization/encryption requirements,
56
56
* [Terms and conditions](/types/4/0483-Terms-And-Conditions) of use,
57
-
* [Governance action classifications](/types/4/0422-Governance-Action-Classifications) such as level of confidentiality, expected retention period, how critical this type of data is ...,
57
+
* [Governed data classifications](/types/4/0422-Governed-Data-Classifications) such as level of confidentiality, expected retention period, how critical this type of data is ...,
58
58
* [Data classes](/concepts/data-class) are logical types for data used to characterize data during analysis.
59
59
* [Standard/preferred schemas](/concepts/schema) and [associated implementation snippets](/types/5/0504-Implementation-Snippets) to guide developers to improve the consistency of data representation across the digital landscape.
Copy file name to clipboardExpand all lines: site/docs/practices/common-data-definitions/overview.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ Typically, the common data definitions consist of:
21
21
22
22
The common data definitions in open metadata are part of the *Subject Area Materials* and are grouped into [subject areas](/concepts/subject-area). The core materials that cover the meaning of data are described in one or more [glossaries](/practices/common-data-definitions/anatomy-of-a-glossary). These are augmented by [valid values](/practices/common-data-definitions/open-metadata-for-common-definitions), [reference data](/practices/common-data-definitions/open-metadata-for-common-definitions) and [quality rules](/practices/common-data-definitions/open-metadata-for-common-definitions).
23
23
24
-
[Governance action classifications](/types/4/0422-Governance-Action-Classifications) may be added to these definitions which in turn link to governance requirements. This determines how data that is linked to the subject area material should be governed.
24
+
[Governed data classifications](/types/4/0422-Governed-Data-Classifications) may be added to these definitions which in turn link to governance requirements. This determines how data that is linked to the subject area material should be governed.
25
25
26
26
Tools used by the organization to, for example, create new data stores, data visualizations, or APIs, or analytics models are pre-populated with concrete data definitions by automated tool bridges. Each tool bridge extracts the relevant definitions from the metadata catalog, generates the concrete definitions and loads them into the tool. Where possible, these definitions include tags that link the definitions back to the common data definitions.
> Figure 10: Using assignment relationships to create a rich description of the data stored in a schema attribute (data field)
136
136
137
-
??? info "Governance action classifications"
137
+
??? info "Governed data classifications"
138
138
139
-
[Governance action classifications](/types/4/0422-Governance-Action-Classifications) can be attached to most types of metadata elements. They can also be assigned to glossary terms to indicate that the classification applies to all data values associated with the glossary term. The governance action classifications have attributes that identify a particular *level* that applies to the attached element. The definition for each [level](/types/4/0421-Governance-Classification-Levels) can be linked to appropriate Governance Definitions that define how digital resources classified at that level should be governed. Governance Classification Levels are linked to Governance Definitions using the [GovernedBy](/types/4/0401-Governance-Definitions) relationship.
139
+
[Governed data classifications](/types/4/0422-Governed-Data-Classifications) can be attached to most types of metadata elements. They can also be assigned to glossary terms to indicate that the classification applies to all data values associated with the glossary term. The governed data classifications have attributes that identify a particular *level* that applies to the attached element. The definition for each [level](/guides/planning/valid-values/overview) can be linked to appropriate Governance Definitions that define how digital resources classified at that level should be governed. Governance Classification Levels are linked to Governance Definitions using the [GovernedBy](/types/4/0401-Governance-Definitions) relationship.
Copy file name to clipboardExpand all lines: site/docs/services/omas/governance-program/overview.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -85,9 +85,9 @@ The labels may be assigned directly to the asset, or to elements, such as schema
85
85
86
86
## Setting up the levels for your governance classifications
87
87
88
-
The values used in governance classifications show the specific group that the classified asset belongs to. Often an organization has their own levels defined ,and they can be set up in [`GovernanceClassificationLevel`](/types/4/0421-Governance-Classification-Levels/) definitions.
88
+
The values used in governance classifications show the specific group that the classified asset belongs to. Often an organization has their own levels defined ,and they can be set up using the [Valid Metadata Values](/guides/planning/valid-values/overview) services.
89
89
90
-
Egeria has a set of default values that can be set up using the [`createStandardGovernanceClassificationLevels`](https://odpi.github.io/egeria/org/odpi/openmetadata/accessservices/governanceprogram/api/GovernanceClassificationLevelInterface.html) method. Alternatively you can set up your own values through the [GovernanceClassificationManager](https://odpi.github.io/egeria/org/odpi/openmetadata/accessservices/governanceprogram/client/GovernanceClassificationLevelManager.html) client.
90
+
Egeria has a set of default values that are set up when the [Core Content Pack](/content-packs/). Alternatively you can set up your own values through the [GovernanceClassificationManager](https://odpi.github.io/egeria/org/odpi/openmetadata/accessservices/governanceprogram/client/GovernanceClassificationLevelManager.html) client.
Copy file name to clipboardExpand all lines: site/docs/types/0/0021-Collections.md
+1-3
Original file line number
Diff line number
Diff line change
@@ -31,8 +31,6 @@ The classifications associated with *Collection* allow it to be specialized for
31
31
*[*RecentAccess*](#recentaccess-classification) means the collection is a set of elements that have been recently accesses by a user.
32
32
*[*WorkItemList*](#workitemlist-classification) means the collection is a set of elements that have been recently accesses by a user.
33
33
*[*DigitalProduct*](/types/7/0710-Digital-Service) describes a collection of [assets](/concepts/asset) that represent a [digital product](/concepts/digital-product).
34
-
*[*GovernanceStatusSet*](/types/4/0421-Governance-Classification-Levels) for a collection of governance statuses.
35
-
*[*GovernanceClassificationSet*](/types/4/0421-Governance-Classification-Levels) for a collection of governance classification for a particular governance classification.
36
34
*[*EventSet*](/types/5/0535-Event-Schemas) for a collection of related event schemas.
37
35
38
36
The example below shows part of a collection hierarchy representing a digital product catalog. The collections are shown in green and the assets that provide the content for the digital product are shown in yellow.
@@ -113,7 +111,7 @@ The values for the *MembershipStatus* enumeration are:
113
111
**Obsolete* - The membership must no longer be used.
114
112
**Other* - Another membership status that is set up in the *userDefinedStatus* attribute.
115
113
116
-
They can be used to support a simple stewardship workflow. For example, consider an [engine action](/concepts/engine-action) that scans through the [assets](/concepts/asset) examining each one's [Retention](/types/4/0422-Governance-Action-Classifications) classification. If the values in the classification indicate that the [resource](/concepts/resource) that it represents should be archived, it may link the asset into a collection.
114
+
They can be used to support a simple stewardship workflow. For example, consider an [engine action](/concepts/engine-action) that scans through the [assets](/concepts/asset) examining each one's [Retention](/types/4/0422-Governed-Data-Classifications) classification. If the values in the classification indicate that the [resource](/concepts/resource) that it represents should be archived, it may link the asset into a collection.
117
115
118
116
0 commit comments