Configuring Datasets in KDP4

Changing Data Set Settings

To change settings for a data set, click on  ‘Settings’ in the top right hand corner of your dataset. The settings tab allows the data set details to be viewed and changed.

From this tab you can perform the following functions:

  • Rename your Dataset
  • Add data to your dataset
  • Make changes to your index settings/policy
  • Add/Change permissions for users & groups to maintain access controls to your dataset
  • Delete the dataset, which will permanently remove the dataset, and the data held

Add Data to your dataset

If you want to add data to an existing dataset, simply click the ‘Add Data’ button right above your existing data, and you will have the option to either load files or connect to an external source, as you would on initially importing data into Koverse.

Index Settings

The index settings tab makes it easy to configure which attributes of a data set are searchable. By default, Koverse indexes all attributes found. Any new attributes showing up in newly imported data will also be automatically indexed., in order to make changes to your index settings, auto indexing must be turned off.

Enabling search without specifying field names allows users to search datasets using general search parameters.  This increases storage usage. Disabling this feature will require users to input specific search parameters when querying a dataset to return results.  This option optimizes storage usage.

To prevent a particular attribute from being indexed, and therefore being searchable, click the radio button labeled ‘Index Specific Fields’. This will allow you to select whether to index attributes by checking or unchecking the box next to each attribute. Once the set attributes to be indexed is selected, click the ‘Save’ button at the bottom of the page.

Changing the set of attributes indexed will cause a background reindexing job to be started. When this job is complete the index will have been updated to reflect these settings and any newly imported data will be indexed according to these settings. Please note that it may take several minutes for the changes to be applied.


Organizations can define groups, associate users to groups, and grant permissions to groups for system actions or data set-specific actions.

In some cases the mapping of users to groups is defined by an external system such as Active Directory, LDAP, or another single-sign on system. If not, Koverse provides a built-in method of defining users and groups.

Regardless of how users and groups are managed, Koverse will manage the permissions granted to groups for Koverse-specific system actions and for access to data sets.


Making a Data Set Private

A newly created data set is controlled by the user who created it, known as the ‘responsible user’. By default this user is the only user that can see that this data set exists, and this user can perform all actions on the data set.

To ensure that a data set is private and accessible only by the responsible user, remove all groups from the list on the data sets Permissions tab. Do this by clicking the trash can icon column in the permissions list for all groups.


Making a Data Set Available to a Limited Group of Users

To grant specific access to a limited group of users, first add the group that you wish to allow access to by typing in the name of the group in the input box labeled ‘Search for Group’, if the group does not already appear in the permissions list.

Even though the group is now added to the permissions list, the users that belong to this will only be able to know of its existence until specific actions are granted. Select the specific actions to grant to this group from the list, which includes:

Read: This allows members of the group to query this data set. Write: Members of the group can import new data to this data set and can delete existing data. Manage:  Members of the group can grant permissions to other groups, can change the name, indexing options, and other settings for this data set.

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


Article is closed for comments.