Action: Create Projects

Automate project creation using files from your external object storage.

This action relies on two required components:

• External object storage: The system accesses files from a specified path in your bucket.

• Project template: The system uses a project template that defines the configuration that each created project will follow.

Create or edit an action

• To create, click the New action button on the page.

• To edit, click the three-dot menu on an action, then click Edit.

Step 1

All fields are required:

1. Name your action.

2. Project template: The projects that will be created by the action will follow this configuration. You must create a template before setting up the action.

3. External object storage: The action will fetch data from this bucket for the projects. You must set up your object storage before creating an action.

4. Input path: The system will read files from this path when the action runs. Each folder represents a project, and each file inside it becomes a document.

   1. This path is relative to the root of your bucket. So, if you want to process S3://test-external-object-storage/input, you will only need to fill input as the value.

   2. If multiple folders exist under input, the system creates one project per folder. From the example below, two projects will be created:

      • Project 1 → ipsum.txt, lorem.txt

      • Project 2 → lipsum.txt

      
5. Result path: After the projects are created, the system moves processed files to this path.

   This prevents files from being processed again in future runs. Do not move files in this result path, as this may prevent the system from accessing them properly. If file conversion is applied (for example, .docx → .pdf), converted files are also stored here.

6. Tags (optional): Add custom tags to projects created by this action.

Step 2

1. Assignees. Select labelers and reviewers to assign to projects created by this action. You must select at least one labeler and one reviewer.

2. Number of labelers per project. Defines how many labelers are assigned to each project. If this number is lower than the total selected labelers, assignments are distributed using round-robin.

3. Number of reviewers per project. Same as above, but for reviewers.

Step 3

1. Number of labelers per document: Defines how many labelers are assigned to each document.

2. Conflict resolution: See detailed documentation for how conflicts are handled.

Step 4

Review all settings in one place. You can also see a preview using sample data, including how assignments will be distributed when the action runs.

Run actions

From the Datasaur app

1. Go to the Actions page.

2. Click Run on a specific action. To manage an action (delete or update), use the three-dot menu on the card.

3. To view the activities of an action, click View run.

   1. Each run appears as one Action run (one row), showing details of the automation process. You can also see the previous runs.

   2. One run can create multiple projects. Click View details for breakdowns.

   3. If the View details button is unavailable, then there is no new data found in the bucket. No projects are created in this case.

4. Action run details show each project creation attempt. Each row represents one attempt.

Through API

To do an API call, start from here.

• Mutation: runAction.