search

marineenergy / apps

shiny apps for marineenergy.app
https://marineenergy.github.io/apps/
MIT License
3 stars 1 forks source link

update Management Measures with Tethys API #124

Open bbest opened 2 years ago

bbest commented 2 years ago

Latest from Tethys

image

Existing

image

Hey Grace,

Yes, the OES-E team recently added a bunch of new entries to the management measures tool and made some structural changes (adding new fields, etc.). Moving forward, the OES-E team plans to make updates every 6 months or so, and I’m not always in the loop on when updates are pushed. We do have a CSV API currently available that you should be able to pull from: https://tethys.pnnl.gov/export/tethys-management-measures-tool.csv. The API will always have the latest content. But I am happy to hop on a call if there are still additional questions.

One more thing – I would encourage reaching out to Mikaela Freeman and the OES-E team to get more details on getting notifications for future updates. I’m only peripherally involved with the OES-E team these days now that Tethys has shifted to live within the PRIMRE project. And it would probably be good to credit OES-E for the management measures tool.

All the best,

-Jonathan

bbest commented 1 year ago

In transforming:

The following columns are used:

And the following new fields are not yet handled:

These are complicated for a few reasons:

  1. The display in the Management tab has limited width, so adding more columns is prohibitive. Perhaps a button could be added with a fuller view. Or we greatly reduce the font size of the table.
  2. There are some one-to-many relationships to sort out. Rows unique by Interaction, Specific_Management_Measures, Implications_of_Measure are repeated when including these extra columns.
  3. Should we match Project_Sites to those find in our Projects tab?
  4. Similarly, should we match Project_Documents to the Documents and Publications tabs?
bbest commented 1 year ago

From Jonathan Whiting:

Hey Ben,

To your first point, I agree that we have too many columns to display everything because of width limitations. We have a few strategies to address this on Tethys. One is that some fields (Comments_on_Past_Experience, Cost_of_Management_Measure, When_Is_It_Needed, Specific_Management_Measures) are simply not displayed and are only available on the downloaded version – these fields tend to be those with more blanks and less valuable information. Another strategy was stacking fields in columns, bolding one field above another (e.g., Management Category over Interaction). Lastly, we have responsive design where it hides some fields for a mobile version, though you can click a button to show the columns again. For vertical constraints, we trim and add a “read more” link to expand specific text sections. Pulling out all the stops to cram in way too much information! You can see these features on the Tethys view: https://tethys.pnnl.gov/management-measures.

I’m not understanding your comment on one-to-one relationships and unique rows repeating. Can you elaborate?

You can map “Project_Documents” to Documents, these exactly match titles of documents in Tethys. “Project_Sites” is new field and references OES-E Metadata Project Sites in Tethys, matching titles exactly. We are currently working on adding OES-E Metadata Project Sites to the PRIMRE API, so you can scrape those if you want. They are international in scope and don’t cover as many U.S. projects as those in the MEE Toolkit, though I would assume your database has all the same U.S. projects.