 |
Page History
...
| # | Functional Requirement | Module | Notes | Expected Input | Expected Output | Priority |
|---|---|---|---|---|---|---|
| 1 | Service shall provide ability to return a attributes for a list of valid concept codes. | Service | One or more concept codes | Concept metadata and properties for each code as limitations of the EVS API allow. Concept parents will also be expected | High | |
| 2 | Service shall provide ability to return a list of concept properties | Service | base URL + /properties | Filtered list of properties as curated by expert users | High | |
| 3 | Service shall provide ability to return a list of export formats available (JSON, CSV, Tab Delimited, Excel) | Service | base URL + /<codes>/properties/<format: JSON,CSV,TABD,EXCEL>/<filename> | Returns file formatted in value indicated by format string | High | |
| 4 | Service for Resolved Branch shall provide ability to return a curated list of NCI Thesaurus branch concept codes | Service | We'll maintain for possible internal use. Not something to be tested | N/A | N/A | |
| 5 | Service for Resolved Branch shall provide ability to return entire concepts of a select branch given the following input parameters:
| Service | This encompasses and replaces the previous us case. Expected inputs include base URL /<code>/<properties>/<level>/,<format>/<filename> | A flattened version of the branch results including concept metadata, properties and parents | High | |
| 6 | Service for Entity Export shall provide ability to return entities for a list of concept codes given the following input parameters:
| Service | This is the same requirement and use case as the use case above. Inputs and expected Exception: concept code inputs can be multiple but expected individual outputs are the same. | See proceeding column | High | |
| 7 | Service for Entity Export shall provide a list of hierarch roots. These will be the same as those expressed by the EVS API REST service | Service | base URL + /concept/<terminology>/roots | Listing of the terminology root concept code and name which will be the same as that expressed by the EVS API | High | |
| UI shall be hosted on a public URL available outside the firewall | UI | High | ||||
| UI shall work in the latest versions of Chrome, FireFox, IE, Safari | UI | High | ||||
| UI shall be 508 compliant (https://www.section508.gov/test/web-software) | UI | High | ||||
| UI shall have a header and footer similar to the look and feel and content of the EVS Explorer (https://evsexplore.nci.nih.gov/evsexplore/welcome) | UI | Medium | ||||
UI shall allow the user to select the type of report they want to export
| UI | High | ||||
| UI Entity Export will allow a user to enter NCI Thesaurus concept codes either manually or paste in a comma delimited list of concept codes. | UI | High | ||||
| UI Entity Export shall allow a user to select what properties that they want associated with the export. These properties will be a filtered list retrieved from the server. | UI | High | ||||
UI Entity Export shall allow a user to select the format of the report. Formats must include:
| UI | High | ||||
UI Resolved Branch Export will allow a user to select an NCI Thesaurus top node code. The user must have the following options for selecting a top node:
| UI | High | ||||
| UI Resolved Branch Export will allow a user to select the number of levels to export. | UI | High | ||||
| UI Resolved Branch shall allow a user to select what properties that they want associated with the export. These properties will be a filtered list retrieved from the server. | UI | High | ||||
UI Resolved Branch shall allow a user to select the format of the report. Formats must include:
| UI | High | ||||
...
