Access And Metadata¶
Access Pattern¶
Every reusable source should be easy to reach and easy to interpret.
Recommended access pattern:
- point to the source system or folder
- identify the owner
- describe the access skill or retrieval method
- describe when the source is authoritative
- describe the metadata required when assets derived from it are published
Placeholder Access Surfaces¶
| Resource Surface | System | Placeholder Pointer | Assistant Access Intent |
|---|---|---|---|
| Raw media | Cloudinary | https://cloudinary.com/ |
retrieve raw images, video, and derivative assets |
| Company information | SharePoint | TBD | retrieve organizational and reference information |
| Discussion resources | Microsoft Teams via Azure | TBD | retrieve relevant discussion context and collaboration history |
| Product and articles | Odoo BFF / SPOT | TBD | retrieve product facts, article content, and linked references |
| Structured documentation | docs.omnivoltaic.com |
https://docs.omnivoltaic.com/<doc-sites> |
retrieve canonical structured documentation across doc sites |
Access Skill Pattern¶
Each external source should eventually define:
- how it is reached
- what identity or permissions are required
- what kinds of data can be pulled from it
- what should be treated as canonical versus contextual
- how retrieved content should be cited or traced in project outputs
This repo should treat access methods as reusable skills, not one-off instructions.
Metadata Descriptor Set¶
Use the following descriptors for created media wherever possible:
| Field | Meaning |
|---|---|
asset_id |
unique identifier for the published asset |
project_id |
project lane that produced the asset |
campaign |
campaign or initiative name |
channel |
destination channel or medium |
asset_type |
video, carousel, brochure, article, banner, and so on |
locale |
language or market variant |
owner |
accountable person or team |
source_resources |
key resources used during creation |
approval_status |
draft, in review, approved, published, archived |
published_path |
final URL or storage location |
Why This Matters¶
Structured descriptors make the same asset usable across project tracking, compliance review, and gallery inventory.