Campaigns
Callico has several campaign systems to meet different annotation needs. There are currently six types of campaigns:
- classification to classify documents,
- element group to group elements,
- elements to create new typed elements on documents,
- entity form to extract entities from documents,
- entity to extract entities from document's transcriptions,
- transcription to transcribe documents.
Create a campaign
Warning
Only the project managers are allowed to create campaigns.
When creating a campaign, you will be asked to provide a name and a description. This is what will be displayed to contributors.
Info
The description of the campaigns supports Markdown.
Once the campaign is created, you will be automatically redirected to its configuration.
Configure a campaign
Warning
Only the project managers are allowed to configure a campaign.
Number of tasks to assign per volunteer
Number of allowed assignments for available tasks
Ancestor configuration
An optional configuration parameter is available for almost all campaign modes except Element group, Elements and Transcription ones. It allows the manager to decide in which context the element to annotate will be displayed.
For example, let's say we have a table with three columns, lastname, firstname and age, one wants to annotate each text_line of this table using an EntityForm campaign. We will end up with one task per text_line element but the user won't be able to properly annotate since they wouldn't see the table header. Using the context ancestor parameter, the manager would be able to specify that they want users to annotate text_line elements in the context of their first ancestor of type table if it exists.
Following the use case detailed above, here are some screenshots taken with various configurations using the following page (table element is in green and text_line elements are in red):
Context ancestor undefined, annotating the first text_line of the table:
Context ancestor defined as table, annotating the first text_line of the table:
Context ancestor defined as table, annotating the text_line outside the table (no context shown since this text_line isn't the child of any table ancestor):
