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

Our metadata misses so much content #39

Open
ps2270 opened this issue Feb 7, 2017 · 1 comment
Open

Our metadata misses so much content #39

ps2270 opened this issue Feb 7, 2017 · 1 comment
Labels

Comments

@ps2270
Copy link
Contributor

ps2270 commented Feb 7, 2017

quantities, tools, measurement terms; processes; etc

@tcatapano
Copy link
Member

Yes, no description is ever going to be sufficient to describe all the aspects of an entry and be sufficient for all purposes. The current exercise first aims at gaining experience with using metadata in a tabular data structure (that is, records with fields; fields with labels and values, etc...). Secondly, we are trying to get used to "data modelling" to come up with the sets of fields which describe the entities of interest (in this case the entries of the Ms) to enable tracking, quick lookup via filtering, sorting, etc... of entries or sets of entries. The adequacy of any data model depends and can only be evaluated based on some purpose which the model is to be served. Ideally the purpose for the metadata, and later the edition, will be for the purposes we have defined (as started in the User Story process) All models will be inadequate for every purpose, but all models should be sufficient for some purpose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants