Skip to Content

Changes for page 12 Constraints

Last modified by Artur on 2025/09/10 11:19
From version 7.1
edited by Helena
on 2025/05/15 11:07
Change comment: There is no comment for this version
To version 7.2
edited by Helena
on 2025/05/16 14:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -29,23 +29,14 @@
29 29  Any artefact that inherits from the //ConstrainableArtefact// interface can have constraints defined. The artefacts that can have constraint metadata attached are:
30 30  
31 31  Dataflow
32 -
33 33  ProvisionAgreement
34 -
35 35  DataProvider – this is restricted to release calendar
36 -
37 37  DataStructureDefinition
38 -
39 39  Metadataflow
40 -
41 41  MetaDataProvider – this is restricted to release calendar
42 -
43 43  MetadataProvisionAgreement
44 -
45 45  MetadataSetMetadataStructureDefinition
46 -
47 47  SimpleDataSource – this is a registered data source where the registration references the actual Data Set or Metadata Set
48 -
49 49  //QueryDataSource//
50 50  
51 51  Note that, because the //Constraint// can specify a subset of the component values implied by a specific //Structure// (such as a specific DataStructureDefinition or specific MetadataStructureDefinition), the //ConstrainableArtefact//s must be associated with a specific //Structure//. Therefore, whilst the //Constraint// itself may not be linked directly to a DataStructureDefinition or MetadataStructureDefinition, the artefact that it is constraining will be linked to a DataStructureDefinition or MetadataStructureDefinition. As a DataProvider or a MetadataProvider does not link to any one specific DSD or MSD the type of information that can be contained in a Constraint linked to a DataProvider/MetadataProvider is restricted to ReleaseCalendar.