Page History
...
Use Case Number | Init1hm2.pm6.3 |
Brief Description | Data elements that have been created dynamically locally and shared should be reusable by other researchers and organizations. Users should be able to browse for, select, and reuse them in their data collection forms. |
Actor(s) for this particular use case | Metadata Specialist |
Pre-condition | Data elements are shared by other users in other organizations. |
Post condition | Shared data elements are reused for data collection. |
Steps to take |
|
Alternate Flow | None. |
Priority | High. |
Associated Links | |
Fit criterion/Acceptance Criterion | Data elements are reused, data can be captured, and data can be shared based on reused metadata. |
Load and retrieve entire models
Use Case Number | Init1hm2.pm6.4 |
Brief Description | It is often more convenient to pull back or push entire models rather than single elements at a time. This is especially important for systems that are using models to build queries and allow for the extension of models. |
Actor(s) for this particular use case | Metadata Specialist |
Pre-condition | None. |
Post condition | The entire model is fetched from the repository. |
Steps to take |
|
Alternate Flow | It is not necessary that a tool enter a model in its entirety in order for it to be retrieved in its entirety. |
Priority | High |
Associated Links | |
Fit criterion/Acceptance Criterion | None. |