Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Design Initial Model #23

Closed
javier-molina opened this issue Feb 16, 2022 · 1 comment
Closed

Design Initial Model #23

javier-molina opened this issue Feb 16, 2022 · 1 comment
Assignees

Comments

@javier-molina
Copy link
Collaborator

No description provided.

@javier-molina
Copy link
Collaborator Author

From Doug on 10 Feb

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.

@javier-molina javier-molina changed the title design initial model Design Initial Model Feb 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants