Page History

{scrollbar:icons=false}
h1. {page-info:title}
{anchor:ContentsofthisPage}{panel:title=Contents of this Page}
{toc:minLevel=2}
{panel}

h2. 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 \\ | # The Metadata Specialist selects the electronic form to import into the metadata repository
# The Metadata Specialist selects the type of file
# The Metadata Specialist adds other annotation items to associate with the form (e.g. creator, source, etc.)
# The Metadata Specialist begins the import
# The tool parses the form if possible
# 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. \\ | * [Init1pm9 - Automate|https://wiki.nci.nih.gov/x/vgRyAQ]
* [Automate|https://cabig-kc.nci.nih.gov/Vocab/forums/viewtopic.php?f=44&t=143] |
|| *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.\\ |

h2. 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 \\ | # The Metadata Specialist identifies a definition or annotation to match to existing CDEs.
# The Metadata Specialist invokes the matching algorithm of the Metadata Repository
# 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. \\ | * [Init1pm9 -  Automate|https://wiki.nci.nih.gov/x/vgRyAQ]
* [Automate|https://cabig-kc.nci.nih.gov/Vocab/forums/viewtopic.php?f=44&t=143] |
|| *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.\\ |
\\
{scrollbar:icons=false}