Release Notes 2.9 (January 2023)

Replace for Capsules and Data in Pipelines

This feature allows the replacement of a Capsule in a Pipeline with another Capsule or Data with other Data, while maintaining all the connections and mappings.

This allows for the seamless swapping of Capsules and Data without having to manually remap the Pipeline connections and paths.

Note: The Data modal will only show Data that is attached to the Pipeline

R Shiny for Release Capsules

With the R Shiny Cloud Workstation accessible in Release Capsules, Capsules with R Shiny can be released as an app, accessible directly from the Internal Release page. Users will be able to access and run the app without being able to make any changes to the Capsule.

The owners of the original Capsule can toggle R Shiny on via the Metadata page, prior to Capsule release to release it as an R Shiny app.

Note: If a release capsule has multiple versions, the Open R Shiny button represents the latest Release version from the Internal Release page.

Git Sync for GitHub Integration

For Capsules created via GitHub integration, the Sync feature in the Capsule timeline updates the local Capsule with any new commits on the remote repository. Sync will also push any new Capsule commits to the remote repository.

Note: There is an additional requirement to Sync before Release.

Custom Metadata

Custom Metadata for Data improves the search, management, and organization of Code Ocean Data Assets. Metadata is managed at the deployment level by Admins, and have the following properties: Key Name, Value Type, Input Type, Value, Units, Required, and Active. Metadata is added by users and can be edited as experiments progress.

Note: Once created, Metadata Keys cannot be edited or deleted, only deactivated, due to system-wide implications. Ensure Metadata Keys are carefully created to avoid errors.

Release Capsule Improvements

• Different Release versions can be accessed through a new dropdown.

• Improvements to the existing Edit dropdown menu allow users to go to their Original Capsule and/or any duplicate copies they have made.

• The compute resource configuration of Release Capsules are now versioned. The specific resource used is reflected and maintained when users switch between versions in Capsules, improving traceability and reproducibility.