add columns to indicate OOI sampling on chl REST API products

[sbeaulieu]

See closed #19

[sbeaulieu]

consider using ooi chla id column in the sample log (like for nutrients code) ; (could consider using cruise_project_id column from chl log but it is not as fully populated)

[joefutrelle]

@sbeaulieu please explain this in more detail. what column(s) should be added and how would they "indicate" OOI sampling?

[ecrockford]

There is a "project_id" variable in the EDI published packages for both chl and nut data. Categorical with options: LTER, OOI, JP. I think the packages figure out the project_id differently. It appears to be available in nut API output so reference that workflow?

[joefutrelle]

@sbeaulieu @ecrockford will provide details about where to find this information in the LTER_sample_log.xlsx from Sosik lab