nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Dataset ownership should be transferrable or allow other to edit definition th

Sean McArthur

Organization Name

Leidos

Description

Currently, there is no way to allow a user other than the owner to Edit the Definition of a Dataset.

I see two possibly solutions:

1) allow ownership of a dataset to be transferred

2) add a new permission on the dataset to allow editing of the dataset definition. Strange thing is that there is no 'Modify' option as documented below.

https://docs.oracle.com/en/cloud/paas/analytics-cloud/acubi/add-or-update-data-sets-permissions.html

Use Case and Business Need

All datasets are inherently owned by one user. What happens if that user is suddenly denied access to the application? Is there is no way to recover the dataset without the owner? We would like to have the ability for admins (perhaps implicitly) and other users (given access explicitly by name or possibly by role) other than the owner to modify the definition of a dataset.

Original Idea Number: bbd91ab112

Find more posts tagged with

Under Review

Data Connectivity

Administration

Status: Under Review

Comments

Branden Pavol

The point made where admins should always be granted full control is the easiest solution. Not only would an admin not be able to support it, they wouldn't even know it exists. Where's the traceability/accountability here? It's set up to be the wild west here. This should not only exist for Datasets. It should be for all objects: Datasets, Data Flows, Connections, Sequences, Schedules, Projects. If a Data Flow fails to run one day and the owner is not available, the rest of the business who use that project/report are stuck until that one person returns.

Bret Grinslade - Oracle Analytics-Oracle

There are two different issues here I think.

1) Allow admins to control/assign permissions to objects owned by other users.

2) Allow users with read/write permissions to modify / edit the data set.

#2 should already be possible with either read/write to allow modification or full control for deletes, etc.

For #1 - this is under review as a feature for an administrator.

Michal Zima

When speaking to data set admin actions, I have also one tip for change - which would be very helfpull for DevOps (deployment) operation - moving DV artefacts from one environment to other (DEV2PROD):

Ability to change/switch connection assigned to data set (created from database connection) - when you deploy from DEV to PROD you usually redirect data sources from development data source to production data source. This is happening for OBIEE metadata as well - when you change definition of Connection Pool object (changing DSN) when deploying RPD from DEV to PROD.