Skip to content

Add views #275

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.

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

Open
wants to merge 3 commits into
base: mano/datasets-tab-update
Choose a base branch
from
Open

Add views #275

wants to merge 3 commits into from

Conversation

tothmano
Copy link
Collaborator

@tothmano tothmano commented Apr 30, 2025

@tothmano tothmano changed the base branch from main to mano/datasets-tab-update April 30, 2025 08:07
@tothmano tothmano self-assigned this Apr 30, 2025
@@ -55,6 +56,38 @@ For more information, see [Virtual fields](/query-data/virtual-fields).

Map fields are a special type of field that can hold a collection of nested key-value pairs within a single field. You can think of the content of a map field as a JSON object. The Dataset tab enables you to create map fields, and view unused and removed map fields. For more information, see [Map fields](/apl/data-types/map-fields#create-map-fields).

## Views

Views allow you to grant other users scoped access to your datasets. This means that instead of sharing the whole dataset with other users, you have the option to share only a filtered and transformed representation of the data. You define a view using a query that applies filters and transformations to your dataset, and then you only share the results of this query with another user.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this describes one use case for Views, but there are certainly others. The goal of the suggestion below is to describe the functionality at a high level, in a way that's relevant for all the use cases we have in mind. Very open to other ways of approaching this.

Suggested change
Views allow you to grant other users scoped access to your datasets. This means that instead of sharing the whole dataset with other users, you have the option to share only a filtered and transformed representation of the data. You define a view using a query that applies filters and transformations to your dataset, and then you only share the results of this query with another user.
Views allow you to apply commonly-used filters and transformations to your dataset, and to treat the resulting output like you would any other dataset. The concept of a View in Axiom is similar to the concept of a virtual table in a database.

Comment on lines 72 to 75
### Display view

1. Select a dataset.
1. In the **Views** section on the right, click the view you want to display.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure this section is of much value

Comment on lines 77 to 90
### Grant access to view

To grant other users access to a view:

1. Click <img src="/doc-assets/icons/settings.svg" className="inline-icon" alt="Settings icon" /> **Settings > Roles**.
1. Click the role with which you want to share the view or create a new role.
1. In the **Organization** section, enable read access to views.
1. In the **Individual datasets** section, click **Add dataset**.
1. Start typing the name of the view. In the list, find the view that you want to share, and then click **Add**.
<Note>
It’s enough to grant access to the view. You don’t need to grant access to the underlying dataset.
</Note>
1. Click **Save**.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similar the comment above, I think this is focussing too much on a particular use case of views.

@tothmano
Copy link
Collaborator Author

tothmano commented May 1, 2025

@benenharrington Many thanks for this. I see your point and I've addressed your suggestions: https://axiom-mano-views.mintlify.app/query-data/views

I think it's worth keeping the procedures, especially the one about sharing views, because it explains something that isn't intuitive in our UI at the moment.

@benenharrington
Copy link
Contributor

Looks great Mano!

Added one small suggestion to make it explicit that certain users will have access to a view as soon as it's created (similar to datasets). Feel free to ignore if you don't think it's necessary


1. Click <img src="/doc-assets/icons/settings.svg" className="inline-icon" alt="Settings icon" /> **Settings > Roles**.
1. Click the role with which you want to share the view or create a new role.
1. In the **Organization** section, enable read access to views.
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@benenharrington This should be removed, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants