Feat/guppy explorer

[qingyashu]

Use guppy for data explorer instead of arranger. Portal config like this (under dataExplorerConfig block):

"guppyConfig": {
      "dataType": "subject",
      "fieldMapping": [
        { "field": "project", "name": "Project" },
        { "field": "study", "name": "Study" },
        { "field": "race", "name": "Race" },
        { "field": "ethnicity", "name": "Ethnicity" },
        { "field": "gender", "name": "Gender" },
        { "field": "vital_status", "name": "Vital Status" },
        { "field": "whatever_lab_result_value", "name": "Lab Result Value" },
        { "field": "file_count", "name": "File Count" },
        { "field": "file_type", "name": "File Type" },
        { "field": "file_format", "name": "File Format" }
      ],
      "manifestMapping": {
        "resourceIndexType": "file",
        "resourceIdField": "file_id",
        "referenceIdFieldInResourceIndex": "subject_id",
        "referenceIdFieldInDataIndex": "subject_id"
      }
    },
    "charts": {
      "project": {
        "chartType": "count",
        "title": "Projects"
      },
      "study": {
        "chartType": "count",
        "title": "Studies"
      },
      "file_type": {
        "chartType": "count",
        "title": "File Types"
      },
      "ethnicity": {
        "chartType": "stackedBar",
        "title": "Ethnicity"
      },
      "gender": {
        "chartType": "pie",
        "title": "Gender"
      },
      "race": {
        "chartType": "pie",
        "title": "Race"
      },
      "vital_status": {
        "chartType": "bar",
        "title": "Vital Status"
      }
    },
    "filters": {
      "tabs": [
        {
          "title": "Project",
          "fields": [
            "project",
            "study"
          ]
        },
        {
          "title": "Subject",
          "fields": [
            "race",
            "ethnicity",
            "gender",
            "vital_status"
          ]
        },
        {
          "title": "File",
          "fields": [
            "file_type"
          ]
        }
      ]
    },
    "buttons": [
      {
        "enabled": true,
        "type": "data",
        "title": "Download All Data",
        "leftIcon": "user",
        "rightIcon": "download",
        "fileName": "data.json"
      },
      {
        "enabled": true,
        "type": "manifest",
        "title": "Download Manifest",
        "leftIcon": "datafile",
        "rightIcon": "download",
        "fileName": "manifest.json"
      }
    ],
    "table": {
      "enabled": true,
      "fields": [
        "project",
        "study",
        "race",
        "ethnicity",
        "gender",
        "vital_status",
        "whatever_lab_result_value",
        "file_count",
        "file_type",
        "file_format"
      ]
    }

Notice that filters and charts are same as previous cofnig, and for table there's extra table.fields block. For backward compatibility, if there's no "guppyConfig" block in portal config, data explorer will still use arranger for data explorer page by reading arrangerConfig and related config blocks.

New Features

• Use guppy for data explorer instead of arranger

Breaking Changes

Bug Fixes

Improvements

Dependency updates

Deployment changes

[thanh-nguyen-dang]

Should we automate this part to only configure the special mapping?
I mean if it is only project -> Project or vital_status -> Vital Status you don't need to put it in the fieldMapping.

[qingyashu]

I think sometimes some field name mapping will need more caring, like thrpyv, but yeah automation is a good idea, I think we could combine both automation and customized names

[abgeorge7]

can you change this back to "Explore, Analyze, and Share Data" ?

[qingyashu]

Prod use this so I copied them

[abgeorge7]

:O I'll change prod - they should all be "Explore, Analyze, and Share Data" now

[abgeorge7]

and this to false?

[qingyashu]

Sure~

[abgeorge7]

"cases" here shouldn't be hardcoded - for example, NIAID uses "subjects"