Cloud Pak for Data

We are a large Cloudpak for Data user with multiple projects and multiple users spanning multiple internal applications and departments.  We are running 4.0 and plan to upgrade to 4.5.2 soon.  Our problem is that once a project loads assets and publishes them, other users or projects can load the same asset and end up overwriting the work that has been previously accomplished.  Often this happen by accident.

Looking for a way that we can flag an artifact as owned by a specific person/project and only that person or project can make updates/changes to the artifact and its associated Terms and Assets or Data Classes.  Others would be able to read but not touch.
Alternatively if there were a way to lock an artifact so that if changes occur they would need to be approved by the artifact owner prior to the change occurring.

Looking for some document/white paper or best practice that would show us how to setup the system to stop this from happening beyond telling our data stewards to be careful and just don't do that.

------------------------------
William Felton
------------------------------

#CloudPakforDataGroup

William,

You can mark catalog assets as private and add members to the asset with various roles. Then the asset is restricted:

• All asset members can find the asset and see its properties. 
• The asset owner, asset members with the Editor role, and all collaborators in the catalog who have the Admin role can use the asset.

This also means that only the asset members can find the asset in the catalog. If you want many catalog collaborators to be able to find the asset but not use it, create a user group for those users and add the group as a member of the asset with the Viewer role.

See Controlling access to an asset in a catalog (Watson Knowledge Catalog)

I hope this helps!

------------------------------
Inge Halilovic
------------------------------

Original Message:
Sent: Mon October 17, 2022 03:27 PM
From: William Felton
Subject: Multiple Projects/Multiple Users need to be isolated

We are a large Cloudpak for Data user with multiple projects and multiple users spanning multiple internal applications and departments.  We are running 4.0 and plan to upgrade to 4.5.2 soon.  Our problem is that once a project loads assets and publishes them, other users or projects can load the same asset and end up overwriting the work that has been previously accomplished.  Often this happen by accident.

Looking for a way that we can flag an artifact as owned by a specific person/project and only that person or project can make updates/changes to the artifact and its associated Terms and Assets or Data Classes.  Others would be able to read but not touch.
Alternatively if there were a way to lock an artifact so that if changes occur they would need to be approved by the artifact owner prior to the change occurring.

Looking for some document/white paper or best practice that would show us how to setup the system to stop this from happening beyond telling our data stewards to be careful and just don't do that.

------------------------------
William Felton
------------------------------

#CloudPakforDataGroup