tackley / live-dashboard Goto Github PK

from Jonathan Haynes:

Display a little content type icon next to non-article content, just like you get on the front

as it seems to indicate sharing activity

If the information is available in the API or via R2, it would be useful to have a toggle switch to show which user launched the story.

Currently these links go through to the details page. For most users it'd be more useful to link though to the actual article.

From Steve Abbott:

I just spotted one thing which would also make the Big Top 10 and Top 20 parts of the SEO Dashboard very useful: would you be able to provide a link to the stories from the headlines or next to the headlines?

At the moment, it's difficult to get to see the story straight away unless you copy the URL over.

To help the Guardian moderation team, it would be very useful to have a marker next to stories where comments are turned on

Can we add a manually editable notes field for every story so that editors can put in individual notes to suggest how stories should be used on the network front?

Currently the NF marker in recently published only shows up if we've seen traffic referred from the front.

Instead:

• poll the source code of the front to see if the URL can be found (rather than relying on seeing traffic)
• poll both guardian.co.uk & guardiannews.com

I'm a bit suspicious that much of the traffic to /search is actually from internal traffic.

Provide an option to filter out internal traffic.

From Chris:

Add a little marker - icon or colour block - for when an external referrer is bigger than the front

Possibly as simple as highlighting non gu referrers in a different colour (or lolighting to g.co.uk ones)

Could we copy over the functionality of the Recently Published Editorial Content dashboard with a different content API query to make a dashboard for recently launched content from our Business & Professional Networks?

Here are the relevant API queries:

http://explorer.content.guardianapis.com/#/search?section=culture-professionals-network+%7C+government-computing-network+%7C+healthcare-network+%7C+media-network+%7C+local-government-network+%7C+housing-network+%7C+higher-education-network+%7C+public-leaders-network+%7C+social-care-network+%7C+sustainable-business+%7C+voluntary-sector-network+%7C+teacher-network&format=json

http://content.guardianapis.com/search?section=culture-professionals-network+%7C+government-computing-network+%7C+healthcare-network+%7C+media-network+%7C+local-government-network+%7C+housing-network+%7C+higher-education-network+%7C+public-leaders-network+%7C+social-care-network+%7C+sustainable-business+%7C+voluntary-sector-network+%7C+teacher-network&format=json

I used this section filter:

culture-professionals-network | government-computing-network | healthcare-network | media-network | local-government-network | housing-network | higher-education-network | public-leaders-network | social-care-network | sustainable-business | voluntary-sector-network | teacher-network

1. aggregate referrer urls that are the same into a single entry with a count, e.g. http://www.wowwiki.com (17)
2. make urls clickable

Greasemonkey and Chrome UserScripts are related so this should be easy

Can we use the Octopus IDs now passed over to the content API to provide an 'Edit this story in InCopy' link for subeditors in case urgent changes or alterations need to be made?

ESD can advise on the best way to achieve this

Would be be possible to introduce filter by section tick boxes at the top of the dashboard so that if an editor only wants to see Media and Technology content, they could tick those boxes and these filters would only show all launched content from the Media or Technology sections?

The start and end time of the data range is displayed at the bottom on the screen.

This should highlight in red when either there is less that 15 minutes worth of data (ie. after restart) or if the data is more than a few minutes old.

So that I don't take action in response to invalid or old data.

It would be very useful to be able to see when stories have hasStoryPackage = true

From Jonathan Haynes:

It's useful to be able to use the content screen as a narrow window at the side of the screen. This doesn't work at the moment because the table stops resizing under a certain size.

GT: should just be a matter of following instructions at http://twitter.github.com/bootstrap/scaffolding.html#responsive

From Chris:

Make both tabs show top 20 rather than 10

My suggestion here is to create a new suitable-for-desktop view that shows 20 on one screen.

so we can see in absolute terms whether today is a high traffic day or not

From Chris:

Split it into two tabs - one for articles and one for fronts etc - could just do one tab only for articles and the other containing everything. This is simple as all articles contain the date in urls

... because the scanner spots links even when they are within the automated "latest published content" block ...

spotted by chris

Exclude non-browser agent strings.

Exclude some of the stuff that shows up which is irrelevant (e.g. post comment).

Can we change the colour of the story links for a user once that user has clicked on them in order for subeditors to keep better tabs on whether or not they've checked content already

Highlight stories in the recently published list if it is marked as "lead" for the section tag of its section.

On 24 February 2012 11:24, Stephen Abbott [email protected] wrote:

2. Are we able to query for lead content in the content API yet? The editors
   want a way to signal that a story is important. I know they can just do this
   by talking to each other or using email - but they've very keen on this. If
   we can't query for lead, is there a way to add an 'important' manual tick
   box next to stories? Or would that be shit?

Lead content is in the api, but you can only find out by asking a tag
for its lead content - you can't discover that a paticular item of
content has had the lead item ticked. So it's not really practical to
find out from the api right now. (I'd have to ask the api for lead
content info for each tag on each item of content.)

The "important" tick box idea - is that just to be able to flag up to
other users of the dashboard that something is important? (Kind of
like a +1 button). That'd be relatively easy to do, although with the
caveat that if the dashboard restarts the information gets lost.

Yep. It's kind of like a manual +1 for the editors to mark which stories should definitely go on the front. Would be great to do if we could properly query the API to ask for only the content where lead is ticked next to the section tag on the content (I put in a request with Sharath to be able to query for lead and star ratings months ago) - but for now, it would really placate the editors to be able to note that the story is important. Not worried about losing these ticks if dashboard goes down

So you're only interested when the item of content is lead for its section tag? Not when it's lead for any tag?

That's sounding much more doable - what I'd have to do is once I see a new item of content I then query the api for the lead content for its one and only section tag (or the first section tag it has) and see if it's in the list. That's practical - only one more call to the api for each item of content. Is the content always set to be lead before it's launched, or do I need to check regularly afterwards to see it become lead?

Amazing to hear we might be able to do this. Lead story is always set on the tags before launch (or at least it should be).

So if you could show if the story has lead for its section tag, that would be incredible useful as an automated way for editors to show importance.

It will also help us to reinforce that the editors need to mark things as lead for them to work across everywhere.

So a simple marker which says LEAD next to anything which has its section tag ticked for lead would make my production dreams come true.