The Story Status and the platform-specific Publication Status primarily represent the stages of story planning.
In addition, there are Task Statuses that can be used to track task-specific workflows, e.g., for a video workflow.
All statuses can be easily customized or deactivated entirely if needed.
As a Kordiam user with administrator rights, you can access these settings under "Settings > Statuses."
Story Status
The Story Status is a status for an entire story (or event), regardless of how many tasks or publication platforms are assigned to the story.
This status can represent a decision-making process, prioritization, a combination of both, or any other workflow that applies to the entire entry.
The Story Status is primarily displayed in two places:
- In story planning views as a vertical colored bar.
- In the Story Entry Mask, both as a vertical colored bar and as a button.
Relevant questions you should ask yourself regarding the Story Status:
- Should the entire decision-making process be represented in Kordiam?
- Are additional status levels such as "Optional", "Pitch", or "Top Story" needed?
Publication Status
This platform-specific status can reflect the following internal workflows:
- Platform-specific decision-making
- Production and publication processes
You can specify exactly which platform a Publication Status applies to, allowing you to define platform-specific workflows.
Task Status
Several tasks, such as "Text" or "Responsible", can be assigned to a story.
For each task, it is possible to define a workflow, such as Requested > Received > Approved.
You define these workflow stages on the familiar "Statuses" admin page.
Each workflow stage can be assigned to one or more tasks. For example, assigning a status to all image and video tasks is possible, but it does not apply to text or graphic tasks. The Tasks page and the Story List can be filtered according to these status levels.
Examples
Platform-specific decision process:
For Social, a story planned for the website will be given a "Proposal" status before considering whether to use that story for Social and setting the status to "Planned".
Platform-specific production status:
A story might have already been published online but still awaits publication for a print edition.
Default Publication Status
Each platform can have its own default Publication Status. This status is selected by default when adding this platform to a new story. For the platform "Website", for example, this can be "Planned", as stories that are entered for this platform are usually always scheduled for publication. For Social Media or Newsletters, for example, it may be "Proposal" because stories for these platforms go through a different decision-making process.
The default Publication Status for a platform can be set in the "Settings > Platforms" menu and is accessible to administrators.
Special functionality of the "Published" Publication Status
The Publication Status "Published" serves as a timestamp. It would be beneficial if Kordiam were connected to an external system that returns the exact publishing time of a story in real time.
However, if you want to set the "Published" status manually, we recommend you turn off the default Kordiam "Published" status instead of creating a personalized status. This custom status will not have this timestamp functionality, which will help avoid errors.
Disable the Statuses
Individual statuses or the entire status type can be deactivated if not required. Deactivated statuses remain in the system and are not removed from existing stories and events.
However, they are no longer available when entering new stories or events. The Publication Status "No status" cannot be deactivated and is the fall-back solution if no other status is defined.
Comments
0 comments
Please sign in to leave a comment.