Hey all;

I need a little help remembering what this concept is in iNews. I remember John Perry told me what it referred to during training a few years back, but for the life of me, I can't remember what that definition was!
On top of which, none of the documentation seems to have any reference to the term, and Google searches return precisely zero results.

I've had a dblines cv . running for a couple of months(!) now on our iNews server, and I'm seeing a lot of these kind of messages:

SYSTEM.MEDIA-INDEX: singleton storygroup fb64fe74-2e7a-4c39-b84d-d143dc8f35f2 entry, record 25071188

Consecutive stores in an iNEWS queue can be linked together as a group in the iNEWS workstation.

Sometimes, if a group is broken up or a story moved out of the group, the markers aren't cleaned up properly so that a story may remain marked as belonging to a group, but the group has no other members. A single-story group makes no sense so the warning is thrown

Thanks for the speedy reply Philip.

As there must have been millions of these errors thrown over the past couple of months of running dbvisit, is that an indication of something critically wrong with the way our producers work in iNews?

Given your clear description of the cause:

1: is it possible iNews is reporting individual wire stories as singletons?

2: Should I be asking my producers to start grouping slugs into story-groups in rundowns?

3: Or are you saying that individual stories aren't usually singletons unless they're the result of a group being broken up or a story being moved out of a group?

I might have an idea of the cause; despite me telling them numerous times not to do this, producers here have a nasty habit of floating stories to move them around in the rundown, but then never unfloat them. This has gotten so bad, even our template rundowns have a bunch of floated stories tucked away at the end.

Apologies, I'm not an Inews expert and don't have the expertise to answer that question... 

Feel free to create a support case to get these answers: Support - Broadcast & Video Post Support - Avid

No worries Philip, thanks for putting me on the right track!

As suggested by you Philip, I raised a ticket through the support portal, and got a very quick response from César.

I hope he doesn't mind, but I'm going to quote him here so that others may benefit:

1) I would start by turning off the media index trait.

- NEWS-A# dbtraits . -mi

2) After that, empty the media index request queue:

- INEWS-A# dbtraits system.media-index purge 0 (y for yes)

3) If you run a dblines now, you should see a difference from the previous one - there should be no reports of storygroup errors in SYSTEM.MEDIA-INDEX.

4) Now, I would run dbvisit offline at soon as possible.

- INEWS-A# dbvisit -d

5) Finally, you would need to turn on the Media Index trait

- INEWS-A# dbtraits . +mi

He also recommended not performing these steps unless you are in a similar suggestion.

I've got a maintenance window coming up on Saturday the 2nd of March, so I'll run through this then and report back.

Thank you for updating the forum!

A further update;

Performing the steps outlined by César resulted in our dbdump dropping from >30GB to ~2.5GB!
I'm really happy with this result!

Kind Regards,

Mat