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
Harmonization of metadata and data QC procedures for cross-referenced data (some wrinkles exist currently when harvesting ETN's metadata that we sort of quietly work through over here, perhaps there could be some going the other way as well.). Some specifics for our current issues will be added to this ticket shortly, but ETN has also raised the following:
We should take a look to the naming conventions. There are a lot of mismatches between ex: Station, projects, PI's...
Automate the OTN -> ETN harvest after a new push, now we need to start this manually after receiving an email. An automated notification to OTN can also be created when new data is added to ETN
Harmonization of metadata and data QC procedures for cross-referenced data (some wrinkles exist currently when harvesting ETN's metadata that we sort of quietly work through over here, perhaps there could be some going the other way as well.). Some specifics for our current issues will be added to this ticket shortly, but ETN has also raised the following:
We should take a look to the naming conventions. There are a lot of mismatches between ex: Station, projects, PI's...
Automate the OTN -> ETN harvest after a new push, now we need to start this manually after receiving an email. An automated notification to OTN can also be created when new data is added to ETN
Match Deployment/Receiver statuses with the ETN statuses. #28
Harmonize mystery tag layer dataset #32
ETN mystery tags layer - add tag code space #17
The text was updated successfully, but these errors were encountered: