Design Metadata Schema Skill
Develop a comprehensive metadata schema for content management. This skill defines structured fields, validation rules, and standards compliance to improve searchability and management.
Inputs
PATH - The content domain to apply the schema to (e.g., "/content")OUTPUT_FORMAT - (Optional) The output format for the schema, e.g., "json-schema", "xml", "markdown" (default: "json-schema")DUBLIN_CORE - (Optional) Boolean, whether to align with Dublin Core standards (default: true)CUSTOM_FIELDS - (Optional) List of custom business-specific fields to includeVALIDATION_RULES - (Optional) Boolean, whether to define validation logic for fields (default: true)
Workflow
Step 1: Requirement Analysis
Analyze the content types at PATH to determine metadata needs.
- Identify common attributes (Title, Date, Author).
- Identify specific attributes (Product ID, Version, Region).
Step 2: Schema Definition
Define the fields and their properties.
- Standard Fields: Map to Dublin Core (Title, Creator, Subject, etc.) if enabled.
- Custom Fields: Define fields specified in
CUSTOM_FIELDS or discovered during analysis.
Step 3: Constraints & Validation
If VALIDATION_RULES is true, define:
- Data Types: String, Date, Integer, Boolean, Enum.
- Required/Optional: Cardinality constraints.
- Controlled Vocabularies: Allowed values for specific fields.
Step 4: Schema Output
Generate the schema definition in the requested OUTPUT_FORMAT (e.g., JSON Schema, XML Schema, or Markdown Table).
Required Outputs
A METADATA_SCHEMA object in the specified OUTPUT_FORMAT containing:
- Field Dictionary: Name, Description, Type, Multiplicity.
- Validation Logic: Rules for data entry.
- Mapping: Correspondence to standards (like Dublin Core).
Quick Reference
- Purpose: Standardize content tagging for consistency and interoperability.
- Standards: Dublin Core, Schema.org.
1---2name: design-metadata-schema3description: Design comprehensive metadata frameworks. Develops structured metadata templates and tagging systems.4---56# Design Metadata Schema Skill78Develop a comprehensive metadata schema for content management. This skill defines structured fields, validation rules, and standards compliance to improve searchability and management.910## Inputs1112- `PATH` - The content domain to apply the schema to (e.g., "/content")13- `OUTPUT_FORMAT` - (Optional) The output format for the schema, e.g., "json-schema", "xml", "markdown" (default: "json-schema")14- `DUBLIN_CORE` - (Optional) Boolean, whether to align with Dublin Core standards (default: true)15- `CUSTOM_FIELDS` - (Optional) List of custom business-specific fields to include16- `VALIDATION_RULES` - (Optional) Boolean, whether to define validation logic for fields (default: true)1718## Workflow1920### Step 1: Requirement Analysis2122Analyze the content types at `PATH` to determine metadata needs.23- Identify common attributes (Title, Date, Author).24- Identify specific attributes (Product ID, Version, Region).2526### Step 2: Schema Definition2728Define the fields and their properties.29- **Standard Fields**: Map to Dublin Core (Title, Creator, Subject, etc.) if enabled.30- **Custom Fields**: Define fields specified in `CUSTOM_FIELDS` or discovered during analysis.3132### Step 3: Constraints & Validation3334If `VALIDATION_RULES` is true, define:35- **Data Types**: String, Date, Integer, Boolean, Enum.36- **Required/Optional**: Cardinality constraints.37- **Controlled Vocabularies**: Allowed values for specific fields.3839### Step 4: Schema Output4041Generate the schema definition in the requested `OUTPUT_FORMAT` (e.g., JSON Schema, XML Schema, or Markdown Table).4243## Required Outputs4445A `METADATA_SCHEMA` object in the specified `OUTPUT_FORMAT` containing:46- **Field Dictionary**: Name, Description, Type, Multiplicity.47- **Validation Logic**: Rules for data entry.48- **Mapping**: Correspondence to standards (like Dublin Core).4950## Quick Reference5152- **Purpose**: Standardize content tagging for consistency and interoperability.53- **Standards**: Dublin Core, Schema.org.
dandye