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
The metadata schema currently offers a very limited set of fields, some of which allow free text. To retain a simple schema while allowing richer information, we should support an annotation field (keyword, tags, codes, ...) allowing codes from selected ontologies / subclasses. The allowed set could differ depending on the class.
Importance Level
Low
Affected Components
api, cli, data schema
Technical Requirements
We first need a way tool to browse codes by label, and auto-render label from uri.
Acceptance criteria
Structured codes can be included to instances in modos:
can be dynamically searched by label on data entry
label can be displayed on inspection
(only) code URI is persisted in metadata
The text was updated successfully, but these errors were encountered:
Contact Details
No response
Description
The metadata schema currently offers a very limited set of fields, some of which allow free text. To retain a simple schema while allowing richer information, we should support an annotation field (keyword, tags, codes, ...) allowing codes from selected ontologies / subclasses. The allowed set could differ depending on the class.
Importance Level
Low
Affected Components
api, cli, data schema
Technical Requirements
We first need a way tool to browse codes by label, and auto-render label from uri.
Acceptance criteria
Structured codes can be included to instances in modos:
The text was updated successfully, but these errors were encountered: