Programmatic Conflict Detection

[Mike DiBella]

Regarding API 4.7.1 in case it matters.

When I call BTVScheduler.GetRejectedRecordings(), I get a response that includes items where RejectionEnum=Conflicts and RecordAnyChannel=True, and the scheduler has already resolved the conflict by targeting the recording for another channel. Since these recordings aren't really in conflict anymore, they don't require attention.

I'm trying to figure out how I can get a list of unresolved conflicts that would match the behavior of the Show Conflicting Recordings page in web admin.

Any thoughts on how to do this?

Mike

[Fonceur]

As you said, many of those conflicts are false positive, so you need to actually check that it won't be recording on another channel or that it isn't already in the recent recording list...

[Mike DiBella]

Are you saying that the only way to acheive functionality comparable to the Show Conflicting Recordings page in Web Admin is to iteratively call BTVScheduler.GetExistingConflicts() passing the Job Guid for each item where RejectionEnum=Conflicts and RecordAnyChannel=True from returned from GetRejectedRecordings, checking each GetExistingConflicts response to see if there is a conflicting item?

This would mean that GetExistingConflicts itself would have to behave differently than GetRejectedJobs, and only show "unresolved" conflicts...is this your experience?

Is this the way you are populating the Conflicts tab in BTV Negociator? I noticed that your program behaves the way I'm looking for mine to.

Thanks,
Mike

[Fonceur]

Originally Posted by Mike DiBella

Is this the way you are populating the Conflicts tab in BTV Negociator? I noticed that your program behaves the way I'm looking for mine to.

Yes and if you dig up ccarlin's older posts, you'll see that's also what he had to do in the web admin... I think I am actually using the rejected jobs with the conflict flag instead, since as you noted the dedicated method is useless...

[Kilrsat]

You can see exactly what the web admin is doing:

WebSVN - WebAdministration - Rev 190 - /WebAdministration/SetupRecordings.aspx.cs

Specifically this block:

else if( queryString == "ur_cf" ) {
RemoveSelectedEpisodes.Visible = true;
BlockSelectedEpisodes.Visible = true;
DeleteSelectedJobs.Visible = false;
ChangePriorities.Visible = false;
//We need to pass thru anyway to determine conflicts...
Dictionary<string, int> epgids = FillUpcomingRecordings();
FillUpcomingBlockedRecordings( epgids );
epgids.Clear();


Should point you at the functions to look at in more detail.

[Mike DiBella]

Here's what I think I see...can either of you confirm?

It looks like two lists are being built, a list of rejected recordings from BTVScheduler.GetRejectedRecordings(), and a list of upcomming recordings from BTVScheduler.GetUpcomingRecordings().

Any rejected recording whose EPGID also appears on the list of upcomming recordings is a "resolved conflict" and does not need to be included in the list of "unresolved conflicts".

Do I read that right?

[Mike DiBella]

Well, that's what I implemented and it seems to work. Still interested in comment from either of you...

[Fonceur]

As I said, you can take it a step further and make sure it's not in the recent recordings list either, as technically that wouldn't be a real conflict either...