Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Page Properties

Target release

2.3

Epic

Jira Legacy
serverSystem JIRA
serverId3ed8d091-172c-31ee-8b1a-f688a0e72656
keyGDM-814

Document status

Status
titleDRAFT

Document owner

Deb Weigand

Designer

Elizabeth Jones

Tech lead

Angel Manica Raquel

Developer

Angel Manica Raquel

QA

Deb Weigand

...

User Interface Specifications:

For the samplestab, there will be three additional tabs in the right (content) panel will contain:

  1. The user has the option to select any of the followingadditional tabs will be:

    1. Germplasm

    2. Dnasample

    3. Dnarun

  2. For germplasm, the filtering controls:

    1. germplasm_id (range, ex: 100-210)

    2. germplasm.name list (text area: line-separated list)

  3. For dnasample, the filtering controls:

    1. project.name/project_id

    2. filtering controls from #2 above

    3. dnasample_id (range, ex: 100-210)

    4. dnasample.name list (text area: line-separated list)

    5. uuid

  4. For dnarun, the filtering controls:

    1. filtering controls from #3 above, which includes controls from #2

    2. dnarun_id (range, ex: 100-210)

    3. dnarun.name list (text area: line-separated list)

    4. experiment.name/experiment_id

    5. dataset.name/dataset_id

  5. A submit button to query the database

  6. A clear button to clear the current filters and result set

  7. A table listing the data resulting from the filters

    • This table will provide pagination for optimal performance

    • This table will provide a capability to select rows individually

    • And a select all button to select all rows

  8. A delete button to delete the rows selected

  9. For the result table: All the columns wherein an ID is displayed should have a column next to it displaying the names. Columns should be sortable.

...

  1. Prompt the user to confirm what will be deleted (basic yes-no prompt window with a list of all the germplasm/dnasamples/dnaruns that will be deleted)

  2. PREREQUISITE CHECK:

    1. We only allow dnarun deletion IFF the dnaruns are not associated with any datasets
      If there are dnaruns associated with datasets:

      1. Provide a window/prompt/page that displays the list of dataset references for the dnaruns, and do not allow deletion if there are references. Basically, you have to delete the datasets first.

        1. A message that essentially displays: "dnarun 1 is being used in dataset A, B, and C. dnarun 2 is being used in dataset D and E. Please delete those datasets first."

        2. Presentation of this message and list of datasets should be consistent with that of the Marker Module

    2. We only allow dnasample deletion IFF the dnasamples are not associated with any dnaruns.
      If there are dnaruns associated with those dnasamples:

      1. Provide a window/prompt/page that displays the list of dnarun references for the dnasamples, and do not allow deletion if there are references. Basically, you have to delete the dnaruns first.

        1. A message that essentially displays: "dnasample 1 is associated with dnarun A, B, and C. dnasample 2 is being used on dnarun D and E. Please delete those dnaruns first."

        2. Presentation of this message and list of datasets should be consistent with that of the Marker Module

    3. We only allow germplasm deletion IFF the germplasms are not associated with any dnasamples.
      If there are dnasamples associated with those germplasms:

      1. Provide a window/prompt/page that displays the list of dnasample references for the germplasms, and do not allow deletion if there are references. Basically, you have to delete the dnasamples first.

        1. A message that essentially displays: "germplasm 1 is associated with dnasample A, B, and C. germplasm 2 is being used on dnasample D and E. Please delete those dnasamples first."

        2. Presentation of this message and list of datasets should be consistent with that of the Marker Module

  3. If the user clicks yes, the system will delete the entities provided they meet all pre-requisite checks.

  4. If the user clicks no, the operation will simply abort.

...