Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:d:data_management_criterion [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:d:data_management_criterion [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Data Management Criterion ====== | ||
| + | |||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | A Data Management Criterion establishes a measurable condition used to determine whether [[public: | ||
| + | |||
| + | A Data Management Criterion may address the identification, | ||
| + | |||
| + | A criterion identifies the condition to be evaluated. It does not itself perform a Data Management Activity or determine which criterion has governing authority. | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Dido Solutions, Inc. and Jackrabbit Consulting, Inc., derived for DIDO-TE and informed by ISO/IEC 25012 data-quality concepts and ISO/IEC 11179 metadata principles | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | A Data Management Criterion identifies the applicable subject, measure or observable condition, expected value or state, evaluation method, and conditions under which evaluation occurs. | ||
| + | |||
| + | Applicable Requirements, | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | A Data Management Criterion requires every Test Result retained as Evidence to preserve its originating Test Run identifier and content hash. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||