Mngr: 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."

 {{#cargo_declare:_table=Keywords |TagName=String          |Category=String         |Description=Text        }}

=..."

2026-02-12T10:39:33Z

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  |Category=String  |Description=Text  }} </pre> =..."

New page

== 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 
|Category=String 
|Description=Text 
}}
</pre>

=== 2. The Form Constraint (The "Secret Sauce") ===
In your [[Extension:Page Forms|Page Form]] for Digital Assets, do not let users type tags freely. Instead, force the form to pull from your Master List:

<pre>
{{{field|Keywords|input type=tokens|values from table=Keywords|values from field=TagName}}}
</pre>
* '''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.

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

ICT:Metadata Strategy - Revision history