Explicitly include obs unit id in `request.yaml`?

[lwjohnst86]

Can't they be either?
A simple dataset with only one resource will not have foreign keys (to other resources). Here, the obs. unit ID is the primary key.
A more complex dataset could have resources where the obs. unit ID is the primary key (or part of the primary key) and resources where the obs. unit ID is the foreign key.

Originally posted by @martonvago in #116

It might be better to be explicit rather than try to guess. So maybe we should have a field in the request that explicitly lists the obs-unit-id...? Not sure how that could look like yet.

[fruvago]

Just linking a comment where it came up that knowing the obs. unit ID would be useful in Sprout too.

[fruvago]

By the way, are we saying that the columns that make up the obs. unit ID must be present in all resources? This would make data processing much simpler, as it would allow us not to rely on primary/foreign key info at all for subsetting. Or is this what you're saying?

And whether we have any requirements in addition about primary keys and foreign keys is a different question.

[lwjohnst86]

Yup, that's right! The obs unit should be present in all resources ☺️ And yes, that's right, it will make subsetting easier 💪