Page History

Use Case Number

Init1dbw6.U9

Brief Description

caB2B uses value sets (that bind to concepts) to filter/constrain
certain data elements in formation of queries to datasets. This requires runtime
access (or metadata download prior to runtime) to possible values for
specific data elements. Currently value domains that are associated with data elements stored in metadata repository (MDR/caDSR) are fetched and provided in query builders. The
enumerated values are provided in pull down menus/lists to ensure the queries are formulated with correct allowable values.

The new SI should continue to provide services and processes for us to
be able to identify and compute the value set for querying data elements

Actor(s) for this particular use case

Cancer Researcher

Pre-condition
The state of the system before the user interacts with it

The enumerations (value sets) for attributes/data elements/variables in a particular database are available to help form queries of the database.

Post condition
The state of the system after the user interacts with it

Data matching the selected enumerations (values) is retrieved via an SI operation.

Steps to take
The step-by-step description of how users will interact with the system to achieve a specific business goal or function

1. The Cancer Researcher selects the entity/class of interest and an operation to retrieve the possible attributes/properties. (such as selecting "MyGeneArray" and asking getAttributes)
2. The SI service returns the results (such as all the property/attributes associated with MyGene Assay in the models/data service). 
3. The Cancer Researcher discovers that there is an attribute in the data source that is called GeneArray.Identifier type and that the possible values are "P52Gene Expression" "P40SNP" and "Gene TMExon", and issues a query (such as  "query myGenearray.Id where id = P52 or P40type="Gene Expression")
4. The SI services are invoked and results are returned
5. The results are returned to the user

Alternate Flow
Things which would prevent the normal flow of the use case

None.

Priority
The priority of implementing the use case: High, Medium or Low

High.

Associated Links
The brief user stories, each describing the user interacts with the system for the one function only of the use case. There would potentially be a number of user stories that make up the use case.

• Init1dbw6 - Support caB2B to integrate services on caGrid
• Support caB2B Services to integrate data on grid

Fit criterion/Acceptance Criterion 
How would actor describe the acceptable usage scenarios for the software or service that meets the actor's requirement?

The researcher is able to discover what the possible values are for a data field and select one or more values of interest, results are returned that match only the selected values.