Page History
Scrollbar | ||
---|---|---|
|
Page info | ||||
---|---|---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
| ||||
|
Mark CDE as preferred for class
Use Case Number | Init1hm1.pm25.1 |
---|---|
Brief Description | When creating registering a class in the metadata repository, it may be desirable to mark a common data element as having a preferred definition for that class. This will enable CDE and class reuse later. |
Actor(s) for this particular use case | Metadata Specialist |
Pre-condition | A class has been registered in the metadata repository with associated attributes as a set of CDEs. |
Post condition | A CDE has been marked as preferred for a class. |
Steps to take |
|
Alternate Flow | None. |
Priority | Low |
Associated Links | |
Fit criterion/Acceptance Criterion | The "preferred" CDE/definition must be discoverable. |
Discover preferred CDE for class
Use Case Number | Init1hm1.pm25.2 |
---|---|
Brief Description | When reusing a class, it is desirable to select a definition that the original modeler considers preferred. |
Actor(s) for this particular use case | Metadata Specialist |
Pre-condition | A class has been registered and has a preferred CDE selected. |
Post condition | The user has discovered the preferred CDE. |
Steps to take |
|
Alternate Flow | None. |
Priority | Low. |
Associated Links | |
Fit criterion/Acceptance Criterion | None. |
Reuse CDE and constrain value set
Use Case Number | Init1hm1.pm25.3 |
---|---|
Brief Description | After a CDE has been discovered for reuse, it should be possible to constrain the CDE allowable values by a specific value set. |
Actor(s) for this particular use case | Metadata Specialist |
Pre-condition | A CDE exists in the metadata repository. |
Post condition | The CDE has been constrained by a set of allowable values. |
Steps to take |
|
Alternate Flow | The value set may be selected from a registered ontology. |
Priority | High. |
Associated Links | |
Fit criterion/Acceptance Criterion | None. |
Non-technical metadata management interface
Use Case Number | Init1hm1.pm25.4 |
---|---|
Brief Description | Most of the expertise in any given domain rests with the subject matter experts, many of which are often non-technical. Therefore, it is critical to provide an interface that allows for metadata to be created and annotated by non-technical users. |
Actor(s) for this particular use case | Cancer Researcher |
Pre-condition | None. |
Post condition | Metadata has been created and updated by a non-technical user. |
Steps to take |
|
Alternate Flow | None. |
Priority | High. |
Associated Links | |
Fit criterion/Acceptance Criterion | None. |
Scrollbar | ||
---|---|---|
|