Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assign data names to new ecodata indicators #174

Open
BBeltz1 opened this issue Nov 15, 2024 · 14 comments
Open

Assign data names to new ecodata indicators #174

BBeltz1 opened this issue Nov 15, 2024 · 14 comments
Labels
help wanted Extra attention is needed

Comments

@BBeltz1
Copy link
Collaborator

BBeltz1 commented Nov 15, 2024

New Indicators Requiring ecodata Names

  • Benthic Invertebrate Index (Sarah G) = benthos_index
  • Community Climate Change Risk Indicators (CCCRI; Tarsila S) = community_climate_vulnerability
  • Bottom Temperature Ocean Model (MOM6; Laura G) = bottom_temp_MOM6
  • Zooplankton Indices (Sarah G) = zooplankton_index
  • Cetacean Weekly Acoustic Presence (Becca VH) = cetacean_acoustic
  • Ambient Sound Levels SNE Wind Energy Areas (Jessica M) = wea_sound
  • NE Shelf Functional Trait Indicators (Bart DF) = finfish_traits
  • Sea Surface Temperature Ocean Model (MOM6; Laura G) = sst_MOM6
  • Effective swept area (Andy A) = effective_swept_area
  • Shoreside Support (Geret DP) = shoreside_support
  • Community Social Vulnerability Indicators (CSVI; Bobby M) = community_social_vulnerability
@BBeltz1
Copy link
Collaborator Author

BBeltz1 commented Nov 15, 2024

Hi leads, above is a list of new indicators that have been submitted so far this year. If you have suggestions/preferences for naming these new datasets in ecodata, please edit the original comment above or provide in a new comment below. Thanks!

@gdepiper
Copy link

Are there any naming conventions that you want us to follow?

@BBeltz1
Copy link
Collaborator Author

BBeltz1 commented Nov 15, 2024

Not particularly. We try to be clear and concise. The goal is for an external user to be able to navigate ecodata as intuitively as possible. We can, as a team, iterate over these to find something that works. So feel free to make an initial suggestion for others to review.

For example, for Tarsila's new dataset I would not recommend using ecodata::cccri because there is no way you could decode that acronym if you've never seen it before.

@BBeltz1
Copy link
Collaborator Author

BBeltz1 commented Nov 15, 2024

Ah you know what, I misspoke. We do maintain the following conventions: all lowercase and words separated by underscores.

@jcaracappa1
Copy link
Contributor

@LGruenburg Are the sst and bt MOM6 indicators seasonal anomalies?

@BBeltz1
Copy link
Collaborator Author

BBeltz1 commented Nov 18, 2024

Sarah W and I have gone through and made some suggestions. We would appreciate feedback on these, especially the social ones. Thanks!

@gdepiper
Copy link

I added vulnerability to each of the human community indices, to be more explicit as to what is being measured.

@sgaichas
Copy link
Member

I named the benthos and zooplankton indices similarly to the VAST forage_index
I debated appending VAST but these indices will need to switch to tinyVAST or sdmTMB eventually so decided not to... and we would likely need to rename the forage index with an appendix if we do

@BBeltz1
Copy link
Collaborator Author

BBeltz1 commented Nov 18, 2024

I think that works Sarah, no need to append VAST if it makes them less futureproof and inconsistent with forage index. Thanks for your input!

@jcaracappa1
Copy link
Contributor

Should we consider combining the GLORYS and MOM6 bottom temperature indices to just bottom_temp_model and adding a 'source' column?

@BBeltz1
Copy link
Collaborator Author

BBeltz1 commented Nov 18, 2024

With our current workflows, combining the datasets would also combine the catalog pages. Do we want MOM6 to have its own catalog page?

@jcaracappa1
Copy link
Contributor

I'm not sure. The analytical methods should be the same between the two datasets, so maybe they should be sections under the same page?

@LGruenburg
Copy link

I like the two sections under the same page idea! I have been following the methods as closely as possible with the exception that climatologies are sometimes different. We just need to make sure we emphasize that GLORYS is data assimilative and MOM6 is not. Yes, the SST and BT are seasonal anomalies.

@Laurels1
Copy link

These look good to me. Thanks!
For Community Climate Change Risk Indicators, maybe community_climate_risk so it's not confused with the climate vulnerability assessment?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
Status: Done
Development

No branches or pull requests

8 participants