Current Behavior
Extracts and reductions are not public by default on new workflows. To make these resources public (i.e., accessible to API calls by external apps and Python Client by anonymous individuals or non-collaborators), an owner/collaborator must edit the workflow configuration settings and tick the "public extracts" and "public reductions" options.
Proposed Behavior
Change the default to public -- tick boxes are already filled for new workflows.
Discussion / Reference
In this Slack conversation, the team reached consensus that changing extracts and reductions to be public by default was acceptable (given that there is still an option to make private / non-public), especially given that remembering to change the workflow settings to "public" is a significant gotcha for ALICE and Zoo Notes use cases.
Current Behavior
Extracts and reductions are not public by default on new workflows. To make these resources public (i.e., accessible to API calls by external apps and Python Client by anonymous individuals or non-collaborators), an owner/collaborator must edit the workflow configuration settings and tick the "public extracts" and "public reductions" options.
Proposed Behavior
Change the default to public -- tick boxes are already filled for new workflows.
Discussion / Reference
In this Slack conversation, the team reached consensus that changing extracts and reductions to be public by default was acceptable (given that there is still an option to make private / non-public), especially given that remembering to change the workflow settings to "public" is a significant gotcha for ALICE and Zoo Notes use cases.