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
People typically want to track metadata on the level of a document such as the speaker(s) who produced the text contained in the document, the date and place a document was collected, privacy levels of the document (sometimes speech that is e.g. ceremonial is specifically not made public due to its culturally sensitive nature).
Proposed Feature
Some "layer" system similar to the structural layers used in the core document schematic system that would allow users to decide on a per-project basis how to structure their metadata is probably best.
Alternatives
We could make metadata keys just a free-form K/V pair field, but it's probably better to make it structured unless people specifically request a schemaless solution.
The text was updated successfully, but these errors were encountered:
Motivation
People typically want to track metadata on the level of a document such as the speaker(s) who produced the text contained in the document, the date and place a document was collected, privacy levels of the document (sometimes speech that is e.g. ceremonial is specifically not made public due to its culturally sensitive nature).
Proposed Feature
Some "layer" system similar to the structural layers used in the core document schematic system that would allow users to decide on a per-project basis how to structure their metadata is probably best.
Alternatives
We could make metadata keys just a free-form K/V pair field, but it's probably better to make it structured unless people specifically request a schemaless solution.
The text was updated successfully, but these errors were encountered: