Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Create views for tables #12

Closed
datenangebot opened this issue Feb 19, 2022 · 7 comments · Fixed by #426
Closed

Create views for tables #12

datenangebot opened this issue Feb 19, 2022 · 7 comments · Fixed by #426
Assignees
@Hephi2
Labels
enhancement New feature or request
Milestone
Version 1

Comments

@datenangebot
Copy link
Collaborator

No description provided.

@datenangebot datenangebot added the enhancement New feature or request label Feb 19, 2022
@datenangebot datenangebot added this to the Version 2 milestone Feb 19, 2022
@datenangebot datenangebot modified the milestones: Version 2, Version 1 Jan 6, 2023
@pktiuk
Copy link

pktiuk commented May 14, 2023

Could you elaborate about this feature?
What is such a view look like? Is it something like graphical summary of data inside of table? (like sum of prices of products placed on list, distribution of groups etc.)

@xbluemonkx
Copy link

I am not sure what @datenangebot is going to do, but i would like to add some ideas for this topic.

Tables could / should become something like "objects". E.g. you can have one object/table for artists (name, year founded, label, etc.)
then you can have another object/table for albums (album name, year of release, etc.) and maybe a third object/table for songs (title, length, etc.).

those tables/objects can share keys so that a song can belong to an album and albums belong to artists.

Coming back to "views": you might want to have a view that only show title name + musician name (without the other attributes) and this view could be shared with a small set of people, that is not allowed to see the other attributes of the objects.

or you could have a view showing statistics like number of songs per artist.

going one step further i think that you should be able to define whether or not a person can edit the data in the view. you could use this to create a "add new artist" view, without granting access to the artist table/object itself.

And last but not least: you could think of a deeper right management. e.g. create a view that only show artists from USA or only shows artists, that belong to a usergroup, that the user was added to. etc. etc.

@datenangebot
Copy link
Collaborator Author

Will be tracked here: https://github.com/orgs/nextcloud/projects/80/views/1

@pktiuk
Copy link

pktiuk commented May 23, 2023

Will be tracked here: https://github.com/orgs/nextcloud/projects/80/views/1

Link gives 404.

@datenangebot
Copy link
Collaborator Author

Will be tracked here: https://github.com/orgs/nextcloud/projects/80/views/1

Link gives 404.

Yes, it's a private one and I don't have the permission to change to public. But i asked for it internally. Stay tuned.

@lachmanfrantisek
Copy link

If I may, I would like to add another use case I am looking for:

  • There is a table with attendees of the course with all the tasks/requirements.
  • Organisers fill the table and mark the tasks as done during the course.
  • We would like to be able to share a single row with the attendee in a read-only mode.
  • Attendees should not be able to edit the view properties to get to the other attendee's records.

Ideally, there can be a Share row link or something like that, but a manual process with filtering by name/row-number/... is fine. (Or, I can try playing with the API.)

Or, is there a way how to do this already? (Our current solution is sadly based on the "security-by-obscurity" principle...;)

I can open a new issue if this is out of scope to this.
Thanks for working on all of this!

@datenangebot
Copy link
Collaborator Author

Hi,

okay, we are working on the views stuff and it's quite a hard job.
So it will take it's time, but once the views are there:

  • Share a view with all the tasks in read only mode. Filter for something like attendee = [me] and it will show all tasks for an attendee depending on the individual context.
  • Furthermore you will be able to send a link and preview for a single row via chat, mention it in notes and collectives or send a deep link via mail etc...

No new issue needed.

@Hephi2 Hephi2 self-assigned this Jul 20, 2023
@Hephi2 Hephi2 mentioned this issue Jul 21, 2023
Merged
27 tasks
elzody added a commit that referenced this issue May 31, 2024
@elzody
# This is a combination of 18 commits.
fa68504 
# This is the 1st commit message:

feat: create and edit rows from tables interactive widget

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #2:

fix: set store in widget

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #3:

fix: properly access store to create new row

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #4:

fix: search functionality

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #5:

fix: row reactivity

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #6:

feat: add component testing skeleton files

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #7:

test: start component testing for content reference widget

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #8:

fix: point package.json scripts to webpack.config.js

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #9:

fix(test): properly mount component

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #10:

fix(test): use default options and mix in given mount options

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #11:

fix(tests): add styles for components

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #12:

refactor(tests): move richObject to fixture

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #13:

test: verify table title after mounting component

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #14:

test: test searching in widget

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #15:

refactor(tests): organize mount test

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #16:

fix: resolve pagination issues

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #17:

fix: change viewport dimensions in cypress config

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>

# This is the commit message #18:

fix: refine row selector

Signed-off-by: Elizabeth Danzberger <lizzy7128@tutanota.de>
@barbayellow barbayellow mentioned this issue Jul 10, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Hephi2 Hephi2

Labels
enhancement New feature or request
Projects
No open projects
Views for tables
Status: Done
Milestone
Version 1
Development

Successfully merging a pull request may close this issue.

Feat(Views): Manage data presentation of tables by views nextcloud/tables
5 participants
@lachmanfrantisek @xbluemonkx @pktiuk @Hephi2 @datenangebot