editor
278
edits
Changes
Jump to navigation
Jump to search
GetAllRecordingSchedules (view source)
Revision as of 09:22, 31 October 2014
, 09:22, 31 October 2014no edit summary
{{Api_Method_Spec|
Description= Get a list with all the Schedules (as a paginatedList of [[RecordingSchedule|RecordingSchedule]] objects) for the current user with a given Recording State.
<p>In the case of series/recurrent recording schedules, the method also returns the individual recordings (not only the recordingschedule/RecordingDefinition/"parent" recording), due to backwards compatibility reasons and because of client (Go app) requirements:</p>
<p>Client apps need to know the individual recordings in order to show them graphically to the user ("drawing"/marking all the precise episodes that will be recorded in a series recording, etc.). Recordings created as "series recording" are marked (as "series" type) and associated with the corresponding seriesId (and rest of relevant fields such as the scheduleId, programId, etc.)</p>
<p>* '''Mirada comments''':</p>
* Clients should store the lastModified parameter included in the [[RecordingSchedule|RecordingSchedule]] object(s), as future invocations to cancel/delete recordings methods will require submitting the "lastModified" value in the request. When a client wants to request a cancel/delete, it will need first to retrieve the information (via GetAllRecordingSchedules).
* In Mirada, when creating a "series recording schedule", UNIAPI only creates the "containter"/parent recording, and the STB will add all the associated episodes automatically (as a recording "Linked" to a parent recording). When retrieving the list of recordings from Mirada, "child" recordings will have a reference to their parent (series recording schedule), properly filled in the corresponding fields of the [[RecordingSchedule|RecordingSchedule]] object.
|Parameters=
