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.
How to use GitHub
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
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.