We Are Here To Help

Follow

Roles & Permissions on Data Lens

Data Lens follows the roles and permissions of the Socrata Open Data product. You can find a comprehensive explanation of domain level and view level actions permitted by roles in this article. As new features and functionality are added to Data Lens this article can be used as a resource to help you understand what abilities are available to different user types on your site.

All Users can:

  • Create a new version of an existing Data Lens page when signed in

All Users with Roles on Site can:

  • Create a new Data Lens page from a dataset

Administrators and Publishers can:

  • Manage the public visibility of a Data Lens page
  • Mark a Data Lens page "Official"

Administrators Only can:

  • Change the Owner of a Data Lens page

All Public and Signed-In Users

Create a new version of an existing Data Lens page

Public users can view public data on your site. If they have a Socrata account and sign-in they experience enhanced interaction with data on the site. When it comes to Data Lens, that means the users can customize and save a version of an existing Data Lens page without having the permissions of a roled user on the site.

To save a version of a Data Lens page, first sign-in and then navigate to the Data Lens page. Then, click on data in a card to filter it or use the customize button to enter customize mode. In customize mode, move cards around, add a card, delete a card or change the aggregation. Once you are satisfied with this customized view, choose “Save As” and give the page a title and description. These Data Lens pages will not be visible in the public catalog without designation from a site administrator or publisher.

All Users with Permissioned Roles

Create a new Data Lens page from a dataset

On your site, users have permissioned roles including Viewer, Editor, Designer, Publisher and Administrator. Any of these roled users can create a Data Lens page from a dataset.

To create a new Data Lens page first sign-in and then navigate to the dataset that is the source of the Data Lens page. Then, click on the “Visualize” button to open the visualize panel and choose the Data Lens option. There you’ll see a “New Data Lens” button.

Clicking this button will create a new Data Lens page that the user can customize and save. Saving a Data Lens page does not necessarily make it visible in the public catalog.

Administrators & Publishers

Manage the public visibility of a Data Lens page

Data Lens pages will inherit their permissions from the source dataset by default, but Publishers and Administrators can change the public catalog visibility for a public Data Lens page at the top of the page, via the "Manage" button in the Info Pane.

To change the public Data Lens page visibility, select the blue Manage button and

 

set the desired catalog visibilty.

If you have View Moderation enabled on your domain, this experience will be different.

Mark a Data Lens page “Official”

More than one Data Lens pages can be made from one dataset, all signed-in users can save versions of a Data Len pages. Marking a Data Lens page “Official” allows site Publishers and Administrators to give a quick indication to users about the quality of the view.

There is no limit to the number of “Official” Data Lens pages that can be created from a single source dataset.

To change the “Official” designation of a Data Lens page, select the Manage button and check or uncheck the box next to “Official View.”

Administrators Only

Change the Owner of a Data Lens page

The original owner of a Data Lens page is the user that first saved the page. Site Administrators can transfer ownership to another Socrata user if desired.

To transfer ownership of a Data Lens page to another user, click the Manage button and find the field with the current owner. In this box, start typing the username or email address of the future owner of the dataset. A dropdown list will appear with possible users, select the desired user and click the save button.

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk