Version control on sharing content to network #65
Description
Ensure that a story cannot be marked as "ready to share" until the story's status is "Ready"
Once a story is shared, an organization's edits to their own story do not automatically push to the version shared with network partners. There needs to be some version control here to ensure partners know which version they've acquired and organizations need to be able to edit their own versions without worrying about custom edits being pushed to their partners.
Example:
An organization writes the general version of story that's usable for newsrooms with overlapping audiences or interests. They share that story with their partners. Partners can then pick up that shared story. The original organization is able to make further edits to add details relevant only to their audience. Those edits aren't shared automatically with the partners even though the story is still available to partners. However, if the organization wants to share those edits (perhaps they are to fix an error rather than add detail) a prompt that appears on story save (after a story has been shared) asks if the organization wants to make the new version of the story available to partners and to indicate the nature of the changes.
Partners who've acquired the story get a notification that says an updated copy is available, can see the changes and can see a note indicating why those changes were made and by whom. They can opt to integrate them or not. Updated stories have markers in the display of network stories that indicate an update or correction.