You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Kibana links are changed. We no longer try to build URLs that describe the
46
-
metrics' Elasicsearch results. Instead, we now only return a simple link to
73
+
metrics' Elasticsearch results. Instead, we now only return a simple link to
47
74
configured Kibana root. It is up to the kibana user to interact with the
48
-
dashbaord, setting default security tenant and default kibana index
75
+
dashboard, setting default security tenant and default kibana index
49
76
patterns. You can create kibana Index Patterns (or they may exist already)
50
77
to gather the cloudwatch logs sent to metrics with a similar patter to the
51
78
ES\_CLOUDWATCH\_TARGET\_PATTERN, and if you have configured s3 server access
@@ -76,7 +103,7 @@ This version of the dashboard requires Cumulus API `v9.5.0`
76
103
-**CUMULUS-2505**
77
104
- Update column show/hide component with new styling and "reset to default interaction for each table
78
105
-**CUMULUS-2506**
79
-
- Adds horizontal scroll buttons to tables improving accessibily
106
+
- Adds horizontal scroll buttons to tables improving accessibility
80
107
-**CUMULUS-2511**
81
108
- Ensured that sort state will persist through page changes.
82
109
-**CUMULUS-2524**
@@ -107,7 +134,7 @@ This version of the dashboard requires Cumulus API `v9.5.0`
107
134
- Layout CSS styling tweaks
108
135
-**CUMULUS-2459**
109
136
- Updated localAPI docker-compose.yml to include SSM, Postgres container to be used with RDS compatible API
110
-
- Updated integration tests due to changes in API behavior related to Postgres contstraints between tables
137
+
- Updated integration tests due to changes in API behavior related to Postgres constraints between tables
111
138
-**CUMULUS-NONE**
112
139
- Downgrades elasticsearch version in testing container to 5.3 to match AWS version.
113
140
@@ -341,7 +368,7 @@ This version of the dashboard requires Cumulus API v5.0.0
341
368
342
369
-**CUMULUS-2242** and **CUMULUS-2177**
343
370
- building with `npm run build` will now build a distribution that can be served from behind cloudfront.
344
-
- Fixed bug in nginx config that allows the application to run in the continer built by `bin/build_dashboard_image.sh`.
371
+
- Fixed bug in nginx config that allows the application to run in the container built by `bin/build_dashboard_image.sh`.
345
372
- Overhauled the README.md and added a "Quick start" section
346
373
347
374
-**CUMULUS-1873**
@@ -381,7 +408,7 @@ This version of the dashboard requires Cumulus API v5.0.0
381
408
- Updates the dashboard to use alpha version `@cumulus/api@3.0.1-alpha.2` for testing.
382
409
- Code changes to allow for private CMR collections to have links to the MMT.
383
410
-**CUMULUS-2215**
384
-
- Omits unnecesary statistics request when building the option list of collection names on the granules page.
411
+
- Omits unnecessary statistics request when building the option list of collection names on the granules page.
385
412
-**CUMULUS-2171**
386
413
- Allows filtering of the Granule Inventory List CSV download based on Granule IDs, Status, and Collection.
387
414
-**CUMULUS-2242**
@@ -422,7 +449,7 @@ This version of the dashboard requires Cumulus API v5.0.0
422
449
- Add dashboard version to footer
423
450
424
451
-**CUMULUS-2076**
425
-
- Add context references in headings on indivdual pages for screen reader accessibility
452
+
- Add context references in headings on individual pages for screen reader accessibility
426
453
427
454
-**CUMULUS-2087**
428
455
- Add Reconciliation Report creation page with report type selection
@@ -498,7 +525,7 @@ This version of the dashboard requires Cumulus API v5.0.0
498
525
499
526
-**CUMULUS-1906**
500
527
- Adds a download button dropdown to reconciliation report inventory view.
501
-
Option to download full report as json or indivdual tables as csv files.
528
+
Option to download full report as json or individual tables as csv files.
502
529
503
530
-**CUMULUS-1908**
504
531
- Adds Conflict Type and Conflict Details columns to reconciliation report inventory view tables.
@@ -581,22 +608,22 @@ This version of the dashboard requires Cumulus API v5.0.0
581
608
- Fix dashboard table sort issue
582
609
583
610
-**CUMULUS-1870**
584
-
- Fix/remove unecessary timers on Pdrs page
611
+
- Fix/remove unnecessary timers on Pdrs page
585
612
586
613
-**CUMULUS-1871**
587
-
- Fix/remove unecessary timers on Providers page
614
+
- Fix/remove unnecessary timers on Providers page
588
615
589
616
-**CUMULUS-1872**
590
-
- Fix/remove unecessary timers on granules page
617
+
- Fix/remove unnecessary timers on granules page
591
618
592
619
-**CUMULUS-1873**
593
-
- Fix/remove unecessary timers on executions page
620
+
- Fix/remove unnecessary timers on executions page
594
621
595
622
-**CUMULUS-1875**
596
-
- Fix/remove unecessary timers on Operations Page
623
+
- Fix/remove unnecessary timers on Operations Page
597
624
598
625
-**CUMULUS-1877**
599
-
- Fix/remove unecessary timers on Reconcilation Reports page
626
+
- Fix/remove unnecessary timers on Reconciliation Reports page
600
627
601
628
-**CUMULUS-1882**
602
629
- Fix ES query for TEA Lambda metrics
@@ -617,26 +644,26 @@ This version of the dashboard requires Cumulus API v5.0.0
617
644
### Changed
618
645
619
646
-**CUMULUS-1888**
620
-
- On the Granules page, CSV data was being refreshed in the background alog with the rest
647
+
- On the Granules page, CSV data was being refreshed in the background along with the rest
621
648
of the data based on the timer. This could take a long time, depending on the number of granules.
622
649
This has been changed so that the data is only fetched when the user clicks the "Download CSV" button.
623
650
624
651
-**CUMULUS-1913**
625
-
- Add datepicker to reconcilation-reports page
652
+
- Add datepicker to reconciliation-reports page
626
653
627
654
-**CUMULUS-1915**
628
-
- Add filters for `Report Type` and `Status` to reconcilation-reports page
655
+
- Add filters for `Report Type` and `Status` to reconciliation-reports page
629
656
630
657
-**CUMULUS-1916**
631
-
-reconcilation-reports page now requires Cumulus API version >= v1.23.0
658
+
-reconciliation-reports page now requires Cumulus API version >= v1.23.0
632
659
633
660
## [v1.8.1]
634
661
635
662
### Changed
636
663
637
664
-**CUMULUS-1816**
638
665
- Change Datepicker behavior on login. The default to "Recent" start/end dates
639
-
now only occurs on first login on the hompage.
666
+
now only occurs on first login on the homepage.
640
667
- URL is updated on login to reflect Datepicker params
641
668
642
669
-**CUMULUS-1903**
@@ -658,7 +685,7 @@ This version of the dashboard requires Cumulus API v5.0.0
658
685
659
686
-**CUMULUS-1984**
660
687
- Fix bug where Distribution metrics were showing on the homepage even when
661
-
Elasaticsearch/Kibana not set up
688
+
Elasticsearch/Kibana not set up
662
689
663
690
-**CUMULUS-1988**
664
691
- Fix bugs in reducer-creators
@@ -700,7 +727,7 @@ This version of the dashboard requires Cumulus API v5.0.0
700
727
- Change the metrics section on the home page to update based on datepicker time period.
701
728
702
729
-**CUMULUS-1509**
703
-
- Update styles on grnaules page
730
+
- Update styles on granules page
704
731
705
732
-**CUMULUS-1525**
706
733
- Style changes for rules overview page
@@ -721,10 +748,10 @@ This version of the dashboard requires Cumulus API v5.0.0
721
748
- Update executions details page styles
722
749
723
750
-**CUMULUS-1787**
724
-
- Changes `listCollections` action to hit `/collections/active` endpoint when timefilters are present (requires Cumulus API v1.22.1)
751
+
- Changes `listCollections` action to hit `/collections/active` endpoint when time filters are present (requires Cumulus API v1.22.1)
725
752
726
753
-**CUMULUS-1790**
727
-
- Changes default values and visuals for home page's datepicker. When the page loads, it defauls to display "Recent" data, which is the previous 24 hours with no end time.
754
+
- Changes default values and visuals for home page's datepicker. When the page loads, it defaults to display "Recent" data, which is the previous 24 hours with no end time.
728
755
729
756
-**CUMULUS-1798**
730
757
- Change the 12HR/24HR Format selector from radio to dropdown
@@ -903,7 +930,7 @@ Fix for serving the dashboard through the Cumulus API.
903
930
### Added
904
931
905
932
-**CUMULUS-1337**
906
-
- Must use Cumulus API version v1.14.0 or above in order to use the newi
933
+
- Must use Cumulus API version v1.14.0 or above in order to use the new
907
934
distribution metrics functionality.
908
935
- Distribution metrics are no longer served from the Cumulus API, but are
909
936
computed from the logs in an ELK stack.
@@ -1012,7 +1039,8 @@ Fix for serving the dashboard through the Cumulus API.
1012
1039
### Added
1013
1040
1014
1041
- Versioning and changelog [CUMULUS-197] by @kkelly51
The cloned directory `./cumulus-dashboard` will be refered as the root directory of the project and commands that are referenced in this document, should start from that directory.
60
+
The cloned directory `./cumulus-dashboard` will be referred as the root directory of the project and commands that are referenced in this document, should start from that directory.
61
61
62
62
### Build the dashboard using Docker and Docker Compose
63
63
64
-
It is easy to build a producution-ready, deployable version of the Cumulus dashboard without having to learn the complicated build process details. A single script, `./bin/build_dashboard_via_docker.sh`, when combined with your dashboard's environment customizations, allows you to run the entire build process within a Docker container.
64
+
It is easy to build a production-ready, deployable version of the Cumulus dashboard without having to learn the complicated build process details. A single script, `./bin/build_dashboard_via_docker.sh`, when combined with your dashboard's environment customizations, allows you to run the entire build process within a Docker container.
65
65
66
-
All of the environment variables in the [configuration](#configuration) section are available to override with custom values for your dashboard. A recommended method is to store your variables in a sourceable environment file for each dashboard you are going to build and deploy.
66
+
All of the environment variables in the [configuration](#configuration) section are available to override with custom values for your dashboard. A recommended method is to store your variables in a source-able environment file for each dashboard you are going to build and deploy.
67
67
68
68
If you are using bash, export the values for each configuration option. An example `production.env` could look like:
69
69
```sh
@@ -125,13 +125,13 @@ To build a dashboard bundle<sup>[1](#bundlefootnote)</sup>:
125
125
$ nvm use
126
126
$ [SERVED_BY_CUMULUS_API=true] [DAAC_NAME=LPDAAC] [STAGE=production] [HIDE_PDR=false] [LABELS=daac] APIROOT=https://myapi.com npm run build
127
127
```
128
-
**NOTE**: Only the `APIROOT` environment variable is required and any of the environment varaibles currently set are passed to the build.
128
+
**NOTE**: Only the `APIROOT` environment variable is required and any of the environment variables currently set are passed to the build.
129
129
130
130
The compiled dashboard files (dashboard bundle) will be placed in the `./dist` directory.
131
131
132
132
#### Build dashboard to be served by CloudFront
133
133
134
-
If you wish to serve the dashboard from behind [CloudFront](https://aws.amazon.com/cloudfront/). Build a `dist` with your configuration including `APIROOT` and ensure the `SERVED_BY_CUMULUS_API` variable is unset. For NGAP uers, follow the documentation to *Request Public or Protected Access to the APIs and Dashboard*, Step 5 of [Cumulus Deployments in NGAP](https://wiki.earthdata.nasa.gov/display/CUMULUS/Cumulus+Deployments+in+NGAP).
134
+
If you wish to serve the dashboard from behind [CloudFront](https://aws.amazon.com/cloudfront/). Build a `dist` with your configuration including `APIROOT` and ensure the `SERVED_BY_CUMULUS_API` variable is unset. For NGAP users, follow the documentation to *Request Public or Protected Access to the APIs and Dashboard*, Step 5 of [Cumulus Deployments in NGAP](https://wiki.earthdata.nasa.gov/display/CUMULUS/Cumulus+Deployments+in+NGAP).
135
135
136
136
#### Build dashboard to be served by the Cumulus API.
137
137
@@ -176,7 +176,7 @@ This runs a node http-server in front of whatever exists in the `./dist` directo
176
176
177
177
### Using S3
178
178
179
-
First, [build the dasbboard](#build-the-dashboard). Then deploy the `./dist` folder, the dashboard bundle, to an AWS bucket.
179
+
First, [build the dashboard](#build-the-dashboard). Then deploy the `./dist` folder, the dashboard bundle, to an AWS bucket.
180
180
181
181
```bash
182
182
$ aws s3 sync dist s3://my-bucket-to-be-used
@@ -288,7 +288,7 @@ Bring up and down the entire stack (the localAPI and the dashboard) with:
288
288
$ npm run start-dashboard
289
289
$ npm run stop-dashboard
290
290
```
291
-
This runs everything, the backing Localstack and Elasticsearch containers, the local Cumulus API and dashboard. Edits to your code will be reflected in the running dashboard. You can run cypress tests still with `npm run cypress`. As a warning, this command takes a very long time to start up because the containers come up in a specific order and generally this should be reserved for use by Earthdata Bamboo or some other continuous intergration service. But, if you are using it locally, **be sure to wait until all containers are fully up** before trying to visit the dashboard which is exposed at http://localhost:3000
291
+
This runs everything, the backing Localstack and Elasticsearch containers, the local Cumulus API and dashboard. Edits to your code will be reflected in the running dashboard. You can run cypress tests still with `npm run cypress`. As a warning, this command takes a very long time to start up because the containers come up in a specific order and generally this should be reserved for use by Earthdata Bamboo or some other continuous integration service. But, if you are using it locally, **be sure to wait until all containers are fully up** before trying to visit the dashboard which is exposed at http://localhost:3000
292
292
The stack is ready when the `view-docker-logs` task shows:
Copy file name to clipboardExpand all lines: TABLES.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,11 +14,11 @@ A basic table component that supports row selection and dumb sorting (see below)
14
14
* Options for each column include:
15
15
- Header: *text or component that will render as the header*
16
16
- accessor: *key or function for obtaining value*
17
-
- id: *unqiure column id. required if accessor is function*
17
+
- id: *unique column id. required if accessor is function*
18
18
- disableSortBy: *set to true if the column should not be sortable*
19
19
- width: *default is 125. set value if column needs to be wider/smaller*
20
20
21
-
* Additional options can be found [here](https://github.com/tannerlinsley/react-table/blob/master/docs/api/useTable.md#column-options) or in the documation for a specific plugin hook
21
+
* Additional options can be found [here](https://github.com/tannerlinsley/react-table/blob/master/docs/api/useTable.md#column-options) or in the documentation for a specific plugin hook
22
22
23
23
-**data**: Array of data items. Items can be any format.
24
24
-**sortId**: The id of the column to sort on.
@@ -44,7 +44,7 @@ Wraps `sortable-table` and implements auto-update and smart sort. When a new sor
44
44
45
45
## Dumb vs smart sort
46
46
47
-
Dumb sorting uses react-table's built in sort functionality to sort table data that has **already** been received from the API. Smart sorting initiates a new API request, passing the sort parameter to the server (elasticsearch) which returns a sorted response. The `maunalSortBy` option passed to `useTable()` tells react-table whether we are doing server-side sorting (`true`) or letting react-table sort (`false`).
47
+
Dumb sorting uses react-table's built in sort functionality to sort table data that has **already** been received from the API. Smart sorting initiates a new API request, passing the sort parameter to the server (elasticsearch) which returns a sorted response. The `manualSortBy` option passed to `useTable()` tells react-table whether we are doing server-side sorting (`true`) or letting react-table sort (`false`).
48
48
49
49
When sorting on multiple columns, select the first column, hold down the shift key, and select another column.
0 commit comments