[REQUEST]: Maintain Obs Vars list associated with DeltaBreed experimental dataset

[SCYarnes]

Description

Current Behavior

• No BrAPI endpoint for dataset:
• DeltaBreed users create dataset(s) before data collection. Information from these datasets is pulled via BrAPI to Field Book to support data collection. However because there is no dataset concept, when multiple datasets are pulled the observation variable lists associated with each dataset is not respected.
• Field Book exports dataset files after data collection (with obs) in two formats: tabular & database

Limits of current behavior

Pull two datasets from DeltaBreed into FB.

• DS1 = 3 observations variables = A, B, C
• DS2 = 8 observations variables = A, B, C, D, E, F, G, H

When DS2 is loaded, all 8 observation variables are now erroneously selected for DS1.

Alternatives

Desired Dataset Behavior

• When DS1 is loaded to Field Book the correct 3 observation variables are loaded and selected.
• When DS2 is loaded to Field Book the correct 8 observation variables are loaded and selected.

Additional Context

Experimental (Trial) Dataset is not in BrAPI

• Observation units and related details (independent experimental variables, aka experimental design)
• Observation Variable list (dependent experimental variables)
• Observations (optional, only available after data collection)

Pete doesn't think it needs to be in BrAPI

Hey Shawn, Field Book has the ability to manually enable/disable traits. I think it would be relatively trivial for them to track ObsVars downloaded with a dataset, then enable/disable them automatically when a user changes fields in the app. This functionality would need to be added to Field Book to solve your issue either way, whether it uses the current BrAPI import methods, or if BrAPI had an explicit dataset endpoint that linked everything. I would recommend opening an issue/feature request on the Field Book GitHub (if you haven't already) and perhaps copying this explanation into the #field-book channel to make sure the right people see it.I'm not sure I see the need for a new BrAPI endpoint right now, based on this use case. ObsUnits, ObsVars, and Observations can all be linked together and queried together by a trialDbId or studyDbId depending on how you organize your experiments. Field Book is currently retrieving all its data by studyDbId but it isn't maintaining the relationship between ObsVar and Study after pulling the data.

Duplicates BI-2249