Delete one or more folders

The action described here is a soft deletion of the folder. It does not permanently delete the folder from the database.

Select the folder to be deleted in the browser.
Click and select Delete from the pop-up menu.
Or
In the panel, select in the toolbar.
In the Delete pop-up, click OK to confirm the folder deletion.

In the Contents tab, click to the right of the folder to be deleted.
In the Delete pop-up, click OK to confirm the folder deletion.

In the Contents tab, check the boxes in front of the folders to be deleted.
Check the first box, in the column header, to check all of the boxes.
Click in the column header.
In the Delete pop-up, click OK to confirm the folder deletion.
Because you are making a change to the contents, an electronic signature is required. In the popup, enter a reason for the change, the password used to log into Integral, and then click Sign.

Load a prior state of an folder

A “normal” folder is one where each item it contains is treated independently. That is, each item is versioned independently. A Save Point represents the state of a folder at a point in time, where the state is the collection of file revisions that are currently active in that folder and all children, recursively. Basically, a Save Point is a “snapshot of the analysis at a point in time. A Save Point from the root folder level can be used load an experiment from a historical state or to clone a study to disk from a historical state.

The entire contents of a Save Point enabled folder is treated as a single entity. Any versioning occurs at the folder level.

Saving an experiment from Phoenix to Integral automatically creates a Save Point to record state of experiment after the save has completed.

If two users are simultaneously working on the same version of a Save Point, the version that is saved later is branched off and saved as a new file. The history of the branched version will show the origin of the Save Point.

With the folder for the desired experiment selected, go to the History tab.
Expand the Save Points section of the page.
Expand one of the Save Points.

There are two categories of information stored with a Save Point: file and dependency information.

Files

Expanding Files shows the full path to each file saved in that Save Point and its revision number.

Click next to a file to download the state of the file as it was when the Save Point was created.

Use the popup at the bottom of the browser window to specify what is to be done with the file.

Dependencies

Expanding Dependencies shows the full path to each identified by Phoenix as a dependency when the Save Point was created, its revision number, status (indicates if the file has been updated since the Save Point was created, and notification settings.

Experiment dependencies are saved to track dependencies on objects that exist in Integral. A very common dependency is when analysis output is dependent on the data collected as part of a study.

Integral is configured by default to store study data files in the “Data” folder. In Phoenix, when a new experiment is created from the Integral plug-in, the user can select multiple source files to be included in the experiment. Phoenix retains the source of these objects associated with the objects in Object Browser.

When saving experiments back to Integral from Phoenix, Phoenix will determine what dependencies to save with the experiment by locating all objects in the project that have an External source that is an Integral object.

Levels of dependency that can be set when saving to Integral include:

Invalidate and Notify: New version of referenced object is created or object is deleted, dependent experiments are marked as out-of-date (invalidated), and notifications are created.

Invalidate: New version of referenced object is created or object is deleted, dependent experiments are marked as out-of-date (invalidated).

Notify: Do not invalidate experiments but create notification for any user with access to experiment.

Neither: Dependency references particular revision of file and user is not concerned if new versions are created. Notifications are not created and experiment is not marked as out-of-date.

Click next to a file to download the state of the file as it was when the Save Point was created.

When a dependency is broken, a notification is sent to the user who created that dependency.