Organize a Knowledge table

Created by Laura R, Modified on Fri, 7 Aug at 12:48 PM by Laura R

Permissions	Admin: all rights User with WRITE access on the collection: all rights User with READ access on the collection: can see the table but not interact with it
Related readings	Organize your resources Create and manage a Knowledge table Create and manage policies

Use fields, views, sorting, filtering, and sub-collections to organize data and support efficient screening workflows.

TABLE OF CONTENTS

Manage fields

Field actions are available from the column menu.

Available actions include:

Editing a field automatically marks all affected cells as stale and launches recomputation after validation.

Views save the visual configuration of a Knowledge table.

A view stores:

Views are shared using the same permissions as the collection.

Each user can define a personal default view.

When modifying a view, you can either update the existing one or save it as a new view.

Rows can be sorted by one or more fields.

Supported sort orders depend on the field type:

Sorting priority follows the order of the selected fields.

Three filtering mechanisms are available.

Filter rows using field values.

Supported operators depend on the field type.

Display only rows matching one or more conditional formatting rules.

Create filters directly from selected rows.

You can choose to:

Manual filters override the other filters.

Only visible rows are processed when computing newly added fields.

A sub-collection can be created from the visible rows of a view.

This is particularly useful for progressive screening workflows.

Collections are linked as a chain.

For example:

A → B → C → D

Key behaviors:

When a parent view changes, you can propagate the updated file list to the child collection, and decide how to update the fields in the child table.

Field definitions and extracted values are not synchronized after creation.