nextcloud / nextcloud/metavox

Emit events when metadata are created, updated and deleted so it can trigger webhooks

Open
#86 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
Dominant language
PHP
Stars
25
Forks
6
PR merge metrics
No merged PRs in 30d

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Feature request

Which Nextcloud Version are you currently using:

33.0.5

Is your feature request related to a problem? Please describe.

We are interfacing our Nextcloud (including MetaVox) with an external document indexing tool.
The tool relies on Nextcloud webhook listeners to react to changes as soon as they happen.

At the moment, MetaVox metadata can be read through its OCS API, but we could not find any documented event emitted when file metadata is updated via MetaVox.

As a result, metadata changes can not trigger webhook listeners and external systems must fall back to a periodic full or batch synchronization.

This makes metadata synchronization less efficient and less reactive than file synchronization.

Describe the solution you'd like

Emit a dedicated event whenever file-level metadata is created, updated or deleted in MetaVox.

This would allow external integrations to use Nextcloud webhook listeners to stay in sync.

Describe alternatives you've considered

  • Requesting the MetaVox OCS API regularly
  • Running frequent batch synchronizations

These alternatives works, but they create additional load and do not provide near real-time synchronization.

Additional context

In our case, documents are synchronized incrementally, and metadata changes should be propagated with the same event-driven approach as file changes.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the MetaVox OCS API paths for file metadata creation, updates, and deletion, then inspect how existing Nextcloud events reach webhook listeners. The work is done when each metadata change emits a documented event that external webhook integrations can receive and distinguish.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend-api-design
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.