Building Foundry Part 3: From archive to creative search | Weaviate
Sep 8, 2026

Summary
This post details the implementation of Foundry's scanning process, which includes capturing source path, project, file type, size, modified date, and content hash. It also describes the preparation stage where descriptions, tags, extracted text, relationship roles, and a source URI are added to records. The synchronization step with Weaviate is explained, highlighting the creation or update of the 'Foundry' collection and the use of deterministic identifiers for updating objects. The post also contrasts keyword, semantic, and hybrid retrieval modes and mentions the possibility of adding filters for project, file type, and relationship role.
More from the Semantic Search for Creative Assets trail
- How to extract meaning from charts and tables in PDFs | Weaviate
- Building Foundry Part 2: Where creative workflows break | Weaviate
- Building Foundry: AI isn’t replacing creativity, it’s removing friction | Weaviate
- Import & Vectorize Data with Weaviate at Scale | Weaviate
- Your LLM Is Only as Good as What It Retrieves | Weaviate