In some cases, you may be in a situation when two teams need to moderate the same content for two different displays/use cases. The issue here is that one team may chose to Publish a post to their display, whereas the other team does not want to include it in theirs.
For example, your events team is displaying all of the newest content on a handful of monitors around their venue, and your web team is highlighting only the best content on the event's website. What happens when the events team publishes almost all of the new content as it's aggregated? Unfortunately, it displays on both the venue monitors, and the the event's website.
Using the example above, the below setup, and slight shift in moderation workflow will allow both teams to moderate this content simultaneously.
- Create a new Tag for each of the teams. One team can call their tag “Events Published”, the second “Web Published”.
- Note: You are not creating these tags when you set up a new Term. Do not automatically apply these new tags to content. Go into Curate → Manage Tags → Create Tag.
- Ensure that your current setup is using separate filters for the two displays. Assign the newly-created tag to it's respective filter for each display.
- Update your terms to auto-publish all content.
- Don't worry, this will not actually publish the content to your displays.
Provided that these new “-published” Tags are now the only connection to your filters, then only the content that is both Published and associated with one of these "-published" tags will appear in the displays.
Moving forward your teams will no longer utilize the status buttons (publish, queue, disable) to moderate. Remember, all content is now automatically being published by default.
- To include a post within a display, your teams will now need to add their respective "-published" Tag to the post.
- For example, if your events team chooses a post to include on the venue monitors, they will simply use the tag dropdown, and add the "event-published" tag to the post.