NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Old Version 23

changes.mady.by.user Unknown User (wileyal)

Saved on

compared with

New Version 24

changes.mady.by.user Unknown User (wileyal)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Wiki Markup
{scrollbar:icons=false}

Page info
title
title

Anchor
ContentsofthisPage
ContentsofthisPage
Panel
titleContents of this Page
Table of Contents
minLevel2

Load forms into metadata repository

Use Case Number

Init1pm9.pm16.1

Brief Description

There is a need to be able to import electronic documents/forms into the caDSR.  These may be electronically computable (e.g. in a well formed spreadsheet or other file) or simply a print form (e.g. PDF).  Either way, they need to be annotated as "models" or "forms" within the metadata repository.

Actor(s) for this particular use case

Metadata Specialist

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

A form exists in an electronic file.

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

The form is imported into the metadata repository.

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 Metadata Specialist selects the electronic form to import into the metadata repository
  2. The Metadata Specialist selects the type of file
  3. The Metadata Specialist adds other annotation items to associate with the form (e.g. creator, source, etc.)
  4. The Metadata Specialist begins the import
  5. The tool parses the form if possible
  6. The appropriate metadata items are created in the metadata repository

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

Medium.

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.

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

The form must exist and be reusable, if only from a file-download perspective.

CDE matching

Use Case Number

Init1pm9.pm16.1

Brief Description

When a user is trying to identify a CDE to match with a data field description, the matching should be "intelligent" and provide top matches based on a variety of context criteria.

Actor(s) for this particular use case

Metadata Specialist

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

None.

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

A list of matching CDEs is provided.

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 Metadata Specialist identifies a definition or annotation to match to existing CDEs.
  2. The Metadata Specialist invokes the matching algorithm of the Metadata Repository
  3. The Metadata Repository provides a list of matching CDEs ranked by likelihood of reuse.

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

This flow can be entered through any number of tools or loading scenarios.

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.

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

The matching algorithm should be more intelligent than simple complete text match.


Wiki Markup
{scrollbar:icons=false}