Curtis et al 2022 data hook

[BettsH]

• [x] data curation
• [ ] QAQC
• [ ] manager review

[BettsH]

Hey @jaxinewolfe, mentioning you here to say that I just pushed the first draft of the Curtis hook. A few things I'd like to ask you about and didn't define but might be in the paper: marker date, position method, elevation method/datum, inundation class, vegetation class.

[jaxinewolfe]

Nice work @BettsH! Here are my notes for Curtis data hook:

Methods:

• dry bulk density volume will be the cylinder volume calculated from the 5.2cm diameter and 10cm intervals
• sediment sieved flag: sediment not sieved
• roots_flag: roots and rhizomes included
• For the fraction carbon method, I found this method. Measured carbon is usually EA (elemental analyzer) but if it's not that or wet oxidation, we may need to add dynamic flash combustion to the vocab 🔥 This is something to ask Jim about probably.
• study ID capital C Curtis to match other tables

Depthseries

• There aren't any organic matter measurements (surprisingly) so keep "Fraction OC" and rename as fraction_carbon. Drop "Carbon Density" and "Percent OC by weight". You can also remove the marker type column since there's no dating.

Core-level:

• drop the elevation but include a note that the elevation is available at the site level
• in the Salt Marsh Monitoring section of the report, there are details you can use to fill inundation class for each study marsh.
• I'm not sure about the position method, I think the xml metadata indicates pretty high resolution so it might be RTK, but we might need the authors to confirm

Other:

• impact classes: Jim said he knew these sites, we should confirm this classification with him. We might end up leaving this table out if its not explicitly stated by the study.
• QAQC: test core IDs as well

[jaxinewolfe]

@BettsH It looks like on your recent commit both the Curtis and Rodriguez folders ended up in the Arriola_2017 folder. I'm not sure why this would be since the hook script appears to write to the correct folders. Are you seeing this as well?

[BettsH]

Thanks for catching this @jaxinewolfe, not sure why that happened. I just re-pushed the update and fixed it.