It would be great if we had the ability to branch stories, in particular wire stories.
As you know, an update to a wire story over-writes the previous version. If we had edited that previous version, all the edits are lost.
We can of course clone and then redirect, but doing so generates a new Ellipsis ID and URL. We want the branched versions to maintain both of those, so that analytics, comments, and other related data are maintained. Cloning/redirecting sets all of that back to zero.
Thanks
Ken
Ken Carriere
| Categories | Editor, User Workflow, New Functionality |
It'll be nice if a branch can be created for print.
Just to add to this: the branch would primarily be used to start writing and ultimately to publish a staff version of the text to replace the wire version. So it would be important to be able to see and/or edit either branch in Ellipsis even while one is live on the site and the other is still being worked on, and then to allow the new staff branch to take over as the published branch without (as Ken said) creating a whole new URL or even Arc UUID for the story.
Finally, we would expect that wire updates to existing stories could still flow in (update) the wire branch should the wire service move any such updates, regardless of the presence of other branches.