Working with Collections

In this guide we explore how to use the Control API to manage collections and inputs.

What are Collections

Collections are used to collect and organize (social) content. They do so by using inputs to follow all sorts of (social) content feeds; by users, hashtags, location and more.

What are Inputs

An input is a (social) media content source which is always tied to a specific service.

For certain social media providers it's only possible to collect content from when it's done on behalf of a user. This means you have to connect your social media account first. See the Social Connect Guide for more information on how to do this.

Content

Content can be controlled in two ways, automatically by using a filter and manually by user moderation.

After filtering, accepted content can be viewed and moderated in the so called content queue. Optionally, this content can be published as a so called publication content feed.

See the Filter Guide and the Publication Guide for more information.

Collection Types

Depending on the type of collection, the retrieved content will be processed differently.

The following types are supported:

  • Breaking Burner; (near) realtime content aggregation.
    • Requires manual input management.
    • Allows content filtering.
    • Allows automated direct publication.
    • Allows user moderation.
  • Amplifinder; content ranked by certain criteria, e.g. shares, likes and more.
    • Requires manual input management.
    • Allows content filtering.
    • Allows automated ranked publication.
    • Allows user moderation.

Which Services and Input Types are Supported

How do Collections and Inputs fit together

Every input has a required reference to a single collection, this allows a collection to group inputs together.

Inputs and collections may have a filter to control content, i.e. filtering content resulting from a specific input, or filtering content resulting from a specific collection (all inputs grouped by that collection). If neither a collection or input have a filter, the default contract filter will be used. For more information about filtering see the Filter Guide.

Every collection and input belong to a single contract. See the Contract Guide for more information.

Collections, Inputs and Filter Relation

Managing Collections and Inputs in the Control API