nextcloud / nextcloud/server

Embedded table Folder and file location as a filtered view

Open
#55,264 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

Duplicate of https://github.com/nextcloud/tables/issues/1340, but wanted to highlight it to a broader team as I believe this feature would be a game changing feature for the Nextcloud suite.

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

In an organization, you might want to set procedures and rules. Those rules need to be applied to different teams.
Nexcloud has done extensive work to file sharing capabilities in terms of read and write permissions.

The Tables from the table app can be embedded into file => By doing this, they can become a form who can be accessed by the people who have access to the file.

Embedded table today would display the view filtered set on the app's settings, I recommend creating a new filtered view. (Location filtered view)
A new default column type is created (File location view) and in each row the user can set one or more location where the row can be seen.

If it's in a folder => All the files who contain the embedded table in the folder have access to the row.

If it's in a file => Only this file has access to the row.

By default, it is set to nothing it has access to the table.

Describe the solution you'd like

Reduce the numbers of filtered view !
This would only work for embedded table.
In a column, select a folder or file within Nextcloud to decide the row(s) which would be displayed.

This would allow for very clever things.
Describe alternatives you've considered

Creating a filter view by teamid see https://github.com/nextcloud/tables/issues/142#issuecomment-3022381153

Additional context

To follow the rules of RGDP I want my organization to track any contact in a certain way. To delete them after a certain amount of times etc.... I want this table to be centralized. I do not want contacts to be seen by other teams.

I create a table with my rules with the Tables app.
In /Collectives/ i have 4 folders and 4 identifical files
/project nextcloud => File A
/project super top => File A
/huh=> File A
/why not => File A

=> Set a filtered view based on file location - use the file location as a filtered view

On adding a new row the file location is automatically set. =
Contact 1 is created in /project nextcloud => File A
Contact 2 is created in /project super top => File A
Contact 3 is created in /huh=> File A
Contact 4 is created in /why not => File A

Contact 1,2,3,4 are completely independant when viewed by the same filtered view use file location as a filtered view.
Only one filter is needed.

Create a new file E
=> Create a filtered view based on folder location - Define to use the folder location "Collectives" as a filtered view
All the contacts are visible.

Create a new file J
=> Create a filtered view based on folder location -Define use the folder location Collectives and add an extra filter contains project as a filtered view
the contacts 1 and 2 are visible.

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 with the duplicate issue nextcloud/tables#1340 and the alternative discussed in #142. Done would require an embedded-table filtered view based on folder or file location, automatic location assignment for new rows, and the described visibility behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
authorization, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.