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
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.
quantities, tools, measurement terms; processes; etc
The text was updated successfully, but these errors were encountered: