Support for Document Versioning or Year-Based Metadata #84

Feature Title

Support for Document Versioning or Year-Based Metadata

Describe the feature

Problem

I work with documents that evolve over time and contain multiple yearly updates. For example, a single PDF may include information for 2025 and 2026, and it will be updated again in future years.

Currently, it is unclear what the best practice is for representing these evolving documents in the graph. Storing them as separate documents may create duplication, while keeping them as one document makes it difficult to distinguish between versions or time-specific data.

Example
Document: report.pdf

Versions:

• report_2025.pdf
• report_2026.pdf
• report_2027.pdf

These documents typically share the same structure but contain updated data each year.

It would be helpful if the system supported document metadata such as version or year, allowing users to:

Track different versions of the same document

Filter or query the graph based on document version or year

Maintain a relationship between document versions

Example metadata:

{
"document_name": "report.pdf",
"year": 2026,
"version": "v2"
}

Motivation

No response

Alternatives considered

One workaround could be creating separate workspaces for each year, but this may lead to fragmentation and make it harder to maintain relationships between documents over time.

Use Case

This feature would be useful for:

Annual reports

Versioned documentation

Periodically updated technical documents

Time-based datasets stored in PDFs

Having built-in support for versioning or time-based metadata would make it easier to manage evolving documents and maintain a consistent knowledge graph.

Additional context

No response