nextcloud / nextcloud/approval

Integrate Metavox json mechanism for approval process

Open
#363 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
39
Forks
10
Avg merge
20m
Merged PRs (30d)
4

Description

Feature request

Which Nextcloud Version are you currently using: (see administration page)
NA

Is your feature request related to a problem? Please describe.
Extend the capabilities of the approval mechanism by using the Metavox data structure.
https://github.com/nextcloud/metavox
Metavox introduced a json mechanism to files, maybe in here one could define the approval structure
Flow 1 and modify needs to be approved etc.

Describe the solution you'd like
manipulation of json metadata of metavox as well as tags if a file is tagged
For example if the json structure contains approval flow 1 needs to be approved => Approval process can be decided

Describe alternatives you've considered
Using the nextcloud tables app => File modified=> Marked for approval => metavox flow (permissions with read/writes => (needs to be developed ) add a row for approval process in table app => Human interaction => File approved .

Will do a similar request for the files app flow => because you cannot add a row

Maybe the windmill flow app integration is done for that....

Additional context
Add any other context or screenshots about the feature request here.

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

The issue does not name files, tests, or an entry point. Begin by reviewing the approval mechanism and the linked Metavox JSON metadata proposal, then define how metadata and tags select an approval flow and how permission changes and approval outcomes should be verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.