Collection sets
Table of Contents
What are collection sets?
Collection sets allow you to deliver different content to different users, based solely on user choice. Only one set can be selected at a time, the selection can be changed at any time from settings but this feature wasn't designed with customers regularly changing between sets. Good example of use cases for this are apps that publish the same content in multiple languages, or regional versions of the same publication.
You can assign certain timelines or editions to a set, and if so only users who have chosen that set, will see that timeline in the app. Users make this choice at first launch on a screen that shows before or amongst the original app onboarding screens, but it can also be included as an option in settings.
|
You can assign more than one set to a timeline, and any timeline or edition not specifically assigned to a set will be visible to all users (however to work with search all content will need to be assigned to a set, as mentioned below).
There is no association between versions of an article in different collection sets. For example, the English version of an article will have no knowledge of its Spanish equivalent. If a user bookmarked the English version and then changed to the Spanish collection set, the Spanish version would not appear in their saved timeline. The same applies to sharing or deeplinking in general.
Note that collection sets have no connection to your app's authentication. All users have the ability to see all sets regardless of their access.
Collection sets and Search
In order for search to work correctly with collection sets, all content will need to be tagged into a set. Even if the content is supposed to be visible to all users.
This is because if you have sets enabled search will filter exclusively for content in your chosen set to avoid duplicates. If a piece of content isn't in a set, it won't show up. If it's in all sets then it'll show up once, correctly.
Changing collection sets
Note that while you can add new collection sets (e.g. adding a language) easily, they are not designed to be removed. Currently if you remove a collection set that a user has already chosen, the user will either see nothing (if you reclassify the content) or continue to see the old content without being directed to select a new one.