You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gents. For your viewing pleasure the full model is what I think the extended data model will eventually look like. The reduced model is what I think it should look like in the first instance. The key elements are the event subclasses. Implicitly, an observation is an event that either leads to occurrence records, measurement or facts, or both. The parent of the observation may be a sample event (or it may be stand-alone). The parent of a sample event may be a site visit (or again it may be stand alone). There is also the possibility of multiple levels of parent-child events, if that makes sense in context. Right now, my internal model is that a data resource, event and occurrence can hold any DwC (and friends) term, with terms inheriting down the DR -> site visit -> sample -> * -> observation -> occurrence chain unless over-ridden.
No description provided.
The text was updated successfully, but these errors were encountered: