Jump to content

ICT:Metadata Strategy

From Costa Sano MediaWiki
Revision as of 10:39, 12 February 2026 by Mngr (talk | contribs) (Created page with "== Metadata Strategy: Controlled Vocabulary == To maintain data integrity across our 500GB archive, we use a '''Keywords''' table. This ensures all five members use identical tags. === 1. The Keywords Table === This table acts as our "Master List." <pre> {{#cargo_declare:_table=Keywords |TagName=String <!-- e.g., Heliotherapy --> |Category=String <!-- e.g., Medical Treatment --> |Description=Text <!-- Definition for the researchers --> }} </pre> =...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Metadata Strategy: Controlled Vocabulary

To maintain data integrity across our 500GB archive, we use a Keywords table. This ensures all five members use identical tags.

1. The Keywords Table

This table acts as our "Master List."

{{#cargo_declare:_table=Keywords
|TagName=String         <!-- e.g., Heliotherapy -->
|Category=String        <!-- e.g., Medical Treatment -->
|Description=Text       <!-- Definition for the researchers -->
}}

2. The Form Constraint (The "Secret Sauce")

In your Page Form for Digital Assets, do not let users type tags freely. Instead, force the form to pull from your Master List:

{{{field|Keywords|input type=tokens|values from table=Keywords|values from field=TagName}}}
  • Benefit: The `tokens` input creates a "pill" interface. Users start typing, and the form suggests only the tags that already exist in your Master List.

3. Relational Queries

Because they are linked, you can query for assets based on the Category of the keyword, even if the asset doesn't have that specific word in its description.

{{#cargo_query:
|tables=DigitalAssets=DA, Keywords=K
|join on=DA.Keywords HOLDS K.TagName
|fields=DA.FileName, K.Category
|where=K.Category='Architecture'
}}