The data-products filter initially used associated instruments to get the gcmd keywords. I have now updated the graphql schema to bring in the data product's (doi's)own gcmd keyword property. This variable is stored as a json string and needs to be parsed in the frontend.
I also made a few minor cosmetic changes.
I removed the radial color gradient from the explore views (since it would change based on page length and led to an undesirable user experience)
I updated the tab to say "Data Products" instead of just "products"
Lastly, I also fixed a bug where I had been using an tag instead of the gatsby component for an internal link.
How you can test the enhancement
You can type in the text input box that says "Search for a measurement variable" then select one of the suggestions from the dropdown. The filtered results are data products that will have matching keywords when you navigate to them by clicking on the link in the table.
For example, "AIR QUALITY > TROPOSPHERIC OZONE" returns a result for "TRACER-AQ Ozonesondes" which has the keywords "AIR QUALITY" and "TROPOSPHERIC OZONE".
What I'm changing
The data-products filter initially used associated instruments to get the gcmd keywords. I have now updated the graphql schema to bring in the data product's (doi's)own gcmd keyword property. This variable is stored as a json string and needs to be parsed in the frontend.
I also made a few minor cosmetic changes.
Lastly, I also fixed a bug where I had been using an tag instead of the gatsby component for an internal link.
How you can test the enhancement
You can type in the text input box that says "Search for a measurement variable" then select one of the suggestions from the dropdown. The filtered results are data products that will have matching keywords when you navigate to them by clicking on the link in the table. For example, "AIR QUALITY > TROPOSPHERIC OZONE" returns a result for "TRACER-AQ Ozonesondes" which has the keywords "AIR QUALITY" and "TROPOSPHERIC OZONE".