Story

A Story is an organizational component made up of one or more facets. The primary use is as an organizational mechanism for the sole and/or different versions of a single story. (For example, a radio script and a text article)

A Story can have associated:

• Facets (And by extension Image Assets, Document Assets, Audio Assets, Video Assets)
• Notes
• Tasks
• Events (& Calendar)
• Simple Images, Simple Documents (images and documents used for the Story but not intended for publishing)

A Story can be collaborated on with a network or specific partners from a network.

---

Story

Considerations

The initial version of the platform will focus on one main utility for series:

• creating connections between relevant stories to better facilitate cohesive editing, management and use of shared assets.

---

Fields

Story

name

• Should allow for diacritic marks, spaces and hyphenation.

story_description

• Short profile description.

owner

• The User who created the Story.

organization

• Organization of the User that created the Story.

team

• Users directly affiliated with the Story. (TK Functionality: Users in team fields will receive notifications regarding updates, edits, etc)

creation_date

• The date and time the Story was created on the platform.

sensitive

• A Story marked sensitive will not appear in dashboards of Users who are not the owner of the Story or on the team of the Story.

original_story

• True or False value indicating if the story was originally created by the user's Organization or if the story has been received from a Network partner.

embargo

• Indicator of whether the story is under embargo.

embargo_datetime

• The date and time the embargo ends.

share

• Indicator of whether the story will be shared with Network partners.

share_with_date

• Time and date the story is expected to be shared (This is used to give partners a heads-up that a story is forthcoming)

ready_to_share

• When marked True, the story becomes available to selected Network partners.

share_with

• Selection field for choosing which organizations will be able to pick up the story.

collaborate

• Indicates whether a Story is collaborative.

collaborate_with

• Select Organizations from Network memberships to include in the collaboration.

archived

• Archiving a Story removes it from the dashboard without deleting any of the content. (Functionality to consider, should archiving freeze editing of all fields?)

notes

• Notes associated with a Story that are viewable to all team Users of the Story.

discussion

• The discussion and comments associated with a Story. All Users can participate (TK Functionality: Team Users will get notifications for new comments. )