You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Daily Bruin, all articles go through a certain workflow. They are first created by an editor. Then they are assigned to a contributor. Once the contributor finishes the first draft, they go back to the editor for feedback. This process keeps going for a bit. Lastly, it lands copy editors. They fact check the article and then it can be published.
For meows, a similar workflow is being used. Content Editors (and sometimes copy or social editors) create blank meows and then link the story in the notes section. Then contributors pick meows to write. Once the contributor finishes, asst social editor looks at it, then top social, then original editor who made the meow.
We want to build this workflow into meow. So from the user's perspective, whenever it is their turn to look at a meow, they should be notified. In cayamak, they listing the user's current tasks in a "desk". For meow, we want something similar. We want people to be able to click on their desk and then it will only show posts they are the next person in line. Note: as of now, meow only shows posts scheduled for the day selected in the calendar. We do not want that for desks. If some steps happen the day of, the people next in the workflow might not get a chance to work on it before the deadline. As of now, the design for this is up in the air.
We have also been considering having meow slack people when a meow comes to their desk. We haven't definitively determined this. However, this functionality will be useful in other places and since the exact details of this tasks are still up in the air, I think this is the safest place to start. Neil will arrange a meeting with social and design people so we can work out something there.
Important details:
The newsroom is chaotic. Often times, they don't follow the workflow exactly. This system must allow for users to manually choose who should edit it next.
For now, we don't need to the ability to customize the workflow. For now, we will just hard code it.
Roles can be determined by slack channels. Ask Neil for details
## First steps 1. Make a function then sends a slack message to a user. It should take the User object (defined in user_profile/models.py) and a string message.
2. Add new states to SMPost. As of now, we have ready to post, copy edited, draft and sent. We will need more.
Christine David (Social Editor):
Hey Neil! (sorry you can respond in the morning haha) is there a way to monitor the progress of meows to editors? like how we have "ready to send" and "copy-edited"
maybe we can have one that's like "ready for second edits" "ready for content editors"
and then pairing that with the ability to notify a certain person once meows are ready to them? so notifying the assistant social when it's ready for second edits, or notifying an a&e editor when the meow is ready for content editors
like a meow progress bar LOL
Everyone besides sports has generally the same social production workflow: it'll go assistant social->top social->content editors->copy
we're still working on how we'll do sports next year but i imagine that it'll be the same thing
In the process we might have to make slack messages: #323
Related but not necessary: #271
The text was updated successfully, but these errors were encountered:
In Daily Bruin, all articles go through a certain workflow. They are first created by an editor. Then they are assigned to a contributor. Once the contributor finishes the first draft, they go back to the editor for feedback. This process keeps going for a bit. Lastly, it lands copy editors. They fact check the article and then it can be published.
For meows, a similar workflow is being used. Content Editors (and sometimes copy or social editors) create blank meows and then link the story in the notes section. Then contributors pick meows to write. Once the contributor finishes, asst social editor looks at it, then top social, then original editor who made the meow.
We want to build this workflow into meow. So from the user's perspective, whenever it is their turn to look at a meow, they should be notified. In cayamak, they listing the user's current tasks in a "desk". For meow, we want something similar. We want people to be able to click on their desk and then it will only show posts they are the next person in line. Note: as of now, meow only shows posts scheduled for the day selected in the calendar. We do not want that for desks. If some steps happen the day of, the people next in the workflow might not get a chance to work on it before the deadline. As of now, the design for this is up in the air.
We have also been considering having meow slack people when a meow comes to their desk. We haven't definitively determined this. However, this functionality will be useful in other places and since the exact details of this tasks are still up in the air, I think this is the safest place to start. Neil will arrange a meeting with social and design people so we can work out something there.Important details:
Desks in camayak:
https://www.youtube.com/watch?v=4u3eH8uP7LI
## First steps1. Make a function then sends a slack message to a user. It should take theUser
object (defined in user_profile/models.py) and a string message.2. Add new states to SMPost. As of now, we have ready to post, copy edited, draft and sent. We will need more.
Christine David (Social Editor):
Hey Neil! (sorry you can respond in the morning haha) is there a way to monitor the progress of meows to editors? like how we have "ready to send" and "copy-edited"
maybe we can have one that's like "ready for second edits" "ready for content editors"
and then pairing that with the ability to notify a certain person once meows are ready to them? so notifying the assistant social when it's ready for second edits, or notifying an a&e editor when the meow is ready for content editors
like a meow progress bar LOL
Everyone besides sports has generally the same social production workflow: it'll go assistant social->top social->content editors->copy
we're still working on how we'll do sports next year but i imagine that it'll be the same thing
In the process we might have to make slack messages: #323
Related but not necessary: #271
The text was updated successfully, but these errors were encountered: