Ameriflux calls - notes

[bpbond]

Call with Deb, Margaret, Danielle 2019-07-03:

• Check with Avni about high latitude synthesis (Sue N?)
• Per Deb, take a careful look at e.g. CC-BY instead of current MIT, which is more of a software license and less familiar to e.g. journals.
• May want to reconsider acknowledgment policy—requiring citation of individual datasets and/or COSORE paper
• Follow up with Danielle (?) about an Ameriflux blog entry about COSORE
• In August, schedule call to discuss next steps, in particular no COSORE design decisions prevent a future COSORE->BADM transfer. Probably Ben and Danielle should review technical details ahead of this

[bpbond]

Call with Danielle 2019-09-11

• Design decisions - esp. vis-a-vis BADM
• Trivial - units
• Categorization questions
• Timestamps and aggregation
• Metadata and data

What we're thinking about:

• Anything that BADM requires that's not in COSORE?
• Anything in COSORE that BADM should add?

Goal: Google doc with mapping

BADM - overall design philosophy and organization

• crosses both BADM and continuous data products
• consistent resolution at a common interval -> continuous fluxnet data product
• sporadic data -> BADM
• Metadata: groups of metadata get entered together
• Location information about chamber? Some have asked about this
• What about identifying Ameriflux sites?
• Everything is in local standard time - UTC offset
• Start and end of observations - what about observation length as metadata?

Ben TODO

• Make a time resolution report
• Point her to the RPubs document & download link
• Set up a google sheet
• Think about further QA/QC
• Think about observation length field

[bpbond]

Meeting with Danielle - 2019-10-17 in Berkeley

Broad agreement on approach to heavy/light software stack, nimbleness, standards.

Things to think about technically:

• Flag whether flux computed by instrument, PI, COSORE, other
• Timestamp start and stop issue - Timestamps - start and stop #76
• CSR_PAR not well defined
• CSR_SM is ratio, not percent, right?
• Maybe a flag for suspected daylight savings problem? - see Timestamps (again) #57
• Google form -> everything should be captured in database
• Think hard about dark versus light versus Rs/Rh/NEE - Dark versus light versus Rs/Rh/NEE #75

[bpbond]

Meeting with Danielle and Stephanie at AGU 2019-12-09

• Summarized issues, institutions, goals for SCP
• Things like webinars could be supported by ESS-DIVE team
• See two bold issues above--there may be others but these currently known problems
• Talked about 2020: data ingestion, infrastructure development, and standards/outreach
• First step for outreach Outreach under ESS-DIVE work #72 might be to survey existing COSORE contributors - treat as a pilot survey