Signals Notebook: Configuring Experiment Notebook Requirement

The Experiment Notebook Requirement feature in Signals Notebook allows administrators to control whether experiments must be associated with a notebook during creation. This configuration determines if the Notebook field is mandatory or optional when users create new experiments. This article explains how to enable or disable this requirement and the implications of each setting.

Solution:

Understanding Experiment Notebook Requirement

The Experiment Notebook Requirement setting determines whether:

• Users must select a notebook when creating experiments (required)
• Users can create experiments without associating them with a notebook (optional)

By default, this setting is disabled for both new and existing tenants, making notebook association optional.

Enabling Notebook Requirement for Experiments

1. Log in to Signals Notebook Configuration with administrator privileges
2. Click on the System Objects smart folder
3. Select Experiment from the list of system objects
4. Click on Notebook Requirement
5. Check the "Require experiment to be in a Notebook" checkbox
6. Click the Save Settings button

Once enabled, the Notebook field becomes mandatory when users create new experiments. Users will not be able to create experiments without selecting a notebook.

Disabling Notebook Requirement for Experiments

1. Log in to Signals Notebook Configuration with administrator privileges
2. Click on the System Objects smart folder
3. Select Experiment from the list of system objects
4. Click on Notebook Requirement
5. Uncheck the "Require experiment to be in a Notebook" checkbox
6. Click the Save Settings button

Once disabled, the Notebook field becomes optional when users create new experiments. Users can create experiments without associating them with a notebook.

Impact on User Experience

When Enabled:

• Users must select a notebook before they can create an experiment
• The system will prevent experiment creation if no notebook is selected
• All experiments will be organized within notebooks

When Disabled:

• Users can create experiments without selecting a notebook
• Experiments without notebooks will appear at the root level of the experiment hierarchy
• Users can still optionally associate experiments with notebooks

Considerations for Configuration

When deciding whether to enable or disable this requirement, consider:

1. Organizational Structure:

   • Required notebooks create a more structured hierarchy
   • Optional notebooks provide more flexibility

2. Data Management:

   • Required notebooks make experiment organization and retrieval more consistent
   • Optional notebooks allow for standalone experiments that don't fit into existing notebook categories

3. User Workflow:

   • Required notebooks may add an extra step for users who need to create experiments quickly
   • Optional notebooks give users more freedom but may lead to inconsistent organization

4. Compliance:

   • Required notebooks may better support audit trails and regulatory compliance
   • Optional notebooks provide flexibility for non-regulated work

Best Practices

1. Consistent Policy: Establish a clear policy about notebook usage and communicate it to all users
2. Training: Ensure users understand the organizational benefits of proper notebook association
3. Notebook Structure: If requiring notebooks, establish a clear notebook hierarchy and naming convention
4. Regular Review: Periodically review the experiment organization to ensure the chosen setting continues to meet organizational needs

By properly configuring the Experiment Notebook Requirement setting, organizations can balance structure and flexibility in their experimental data management approach.