DeleteRecordingSchedule - Revision history

Id02660 at 11:31, 30 May 2019

2019-05-30T11:31:03Z

Id02660 at 11:25, 30 May 2019

2019-05-30T11:25:03Z

Id02660 at 10:53, 8 April 2019

2019-04-08T10:53:42Z

Id02660 at 10:29, 5 April 2019

2019-04-05T10:29:44Z

Id02660 at 10:29, 5 April 2019

2019-04-05T10:29:25Z

Id02660 at 10:29, 5 April 2019

2019-04-05T10:29:10Z

Id01213 at 15:41, 18 March 2015

2015-03-18T15:41:57Z

Id01213 at 15:41, 18 March 2015

2015-03-18T15:41:28Z

Id01213 at 08:58, 18 March 2015

2015-03-18T08:58:17Z

Id01213 at 16:37, 17 March 2015

2015-03-17T16:37:05Z

@@ Line 97: / Line 97: @@
 :    "Limit": 10,
 :    "Count": 48,
-:     "Content":[ Array of [[RecordingSchedule|RecordingSchedule]] objects ]
+:     "List":[ Array of [[RecordingSchedule|RecordingSchedule]] objects ]
+}

@@ Line 97: / Line 97: @@
 :    "Limit": 10,
 :    "Count": 48,
-:     [ Array of [[RecordingSchedule|RecordingSchedule]] objects ]
+:     "Content":[ Array of [[RecordingSchedule|RecordingSchedule]] objects ]
+}

@@ Line 43: / Line 43: @@
 |ParamType=int
 |ParamRequired=required
-|ParamDescription=Live Channel ID (EPGLiveChannelReferenceId; as appearing in EPG file)
+|ParamDescription=Live Channel ID (GVP_EPG_LIVE_CHANNELS.REFERENCE_ID; as appearing in EPG file) available in contentApi (LSC.EpgChannelId) info not available in IPI, sent blank in that case
 }}
 {{Api_Parameter|

@@ Line 142: / Line 142: @@
 ! 7.1
 {{!}} Changed behavior for OpenPlatform. SeasonNumber
-{{!}}
+{{!}} José Manuel Escartín
 {{!}}}

@@ Line 140: / Line 140: @@
 {{!}}
 {{!}}- valign="top"
-! 3.0
+! 7.1
 {{!}} Changed behavior for OpenPlatform. SeasonNumber
 {{!}}

@@ Line 74: / Line 74: @@
 |ParamRequired=optional
 |ParamDescription=Allows identifying the user's device (STB) on which the application will be applied, in the case that several DVR devices may exist in the household (does not apply to MiView and Mediaroom)
 }}
@@ Line 91: / Line 97: @@
 |Exceptions=
 Possible error results (included in the GVP general error list) are:
-*8	MissingRequiredParameter		''Mirada''
+*8	MissingRequiredParameter		''OpenPlatf, Mirada''
-*211	RecordingSubscriberNotFound		''MiViewTv, Mirada, Mediaroom''
+*211	RecordingSubscriberNotFound		''OpenPlatf, MiViewTv, Mirada, Mediaroom''
-*212	RecordingSubscriberNotSubscribed	''MiViewTv, Mirada, Mediaorom''
+*212	RecordingSubscriberNotSubscribed	''OpenPlatf, MiViewTv, Mirada, Mediaorom''
-*213	RecordingUnknownError			''MiViewTv, Mirada, Mediaroom''
+*213	RecordingUnknownError			''OpenPlatf, MiViewTv, Mirada, Mediaroom''
-*220	RecordingChannelNotFound		''Mirada''
+*220	RecordingChannelNotFound		''OpenPlatf, Mirada''
-*221	RecordingAlreadySubscribed		''Mirada''
+*221	RecordingAlreadySubscribed		''OpenPlatf, Mirada''
-*223	RecordingProgramNotfound		''Mirada''
+*223	RecordingProgramNotfound		''OpenPlatf, Mirada''
-*228	RecordingProgramNotFinished		''MiViewTv''
+*228	RecordingProgramNotFinished		''OpenPlatf, MiViewTv''
-*235	RequestedLanguagesUnavailable		''Mirada''
+*235	RequestedLanguagesUnavailable		''OpenPlatf, Mirada''
-*236	RecordingUpdatedFromAnotherDevice	''Mirada''
+*236	RecordingUpdatedFromAnotherDevice	''OpenPlatf, Mirada''
-*237	RecordingProtected			''Mirada''
+*237	RecordingProtected			''OpenPlatf, Mirada''
-*238	RecordingHavingChildren			''Mirada''
+*238	RecordingHavingChildren			''OpenPlatf, Mirada''
-*239	RecordingNotFound			''Mirada, Mediaroom''
+*239	RecordingNotFound			''OpenPlatf, Mirada, Mediaroom''
-*240	RecordingRemoteManagementNotEnabled	''Mirada''
+*240	RecordingRemoteManagementNotEnabled	''OpenPlatf, Mirada''
 *241	RecordingIncorrectIntervalDefined	''Mirada''
 *242	RecordingIncorrectStartDate		''Mirada''
@@ Line 132: / Line 138: @@
 ! 3.0
 {{!}} Changed behavior for Mediaroom: method deletes completed (child) Recordings, not RecordingDefinitions
 {{!}}
 {{!}}}

@@ Line 129: / Line 129: @@
 {{!}} Added support for Mirada and Mediaroom. Introduced new parameters recordingScheduleId, lastModified and targetDeviceId
 {{!}}
 ! 3.0
 {{!}} Changed behavior for Mediaroom: method deletes completed (child) Recordings, not RecordingDefinitions

@@ Line 128: / Line 128: @@
 ! 2.4 drop 1
 {{!}} Added support for Mirada and Mediaroom. Introduced new parameters recordingScheduleId, lastModified and targetDeviceId
 {{!}}
 {{!}}}

← Older revision		Revision as of 08:58, 18 March 2015
Line 3:		Line 3:

	Returns an array of [[RecordingSchedule\|RecordingSchedule]] objects, filled with the results and status parameters.		Returns an array of [[RecordingSchedule\|RecordingSchedule]] objects, filled with the results and status parameters.
		+
		+	<p>* '''MiView (ALU) comments''':</p>
		+	* MiView does not establish a clear distinction between RecordingSchedules and Recordings.
		+	* In MiView, since it is a true "network PVR" model, recordings are stored "in the network" (not in the user's STB).
		+	* DeleteRecordingSchedule, when invoked for a MiView backend, deletes (or cancels) the recording (schedules), so subsequent requests for listing the user's "recordings" result in that the recordings/RecordingSchedules do not appear. "Physical" recordings do not make sense in this case, as they are stored and handled by MiView platform (so, although a user removes a recording, the media may be kept to be used by another user).

	<p>* '''Mirada comments''':</p>		<p>* '''Mirada comments''':</p>

@@ Line 10: / Line 10: @@
 <p>* '''Mediaroom comments''':</p>
-DeleteRecordingSchedules is intended for deleting individual ("child") recordings, existing in the user's STB, but not cancelling or deleting the whole definition (RecordingDefinition).
+*DeleteRecordingSchedules is '''intended for deleting individual ("child") recordings, existing in the user's STB''', but not cancelling or deleting the whole definition (RecordingDefinition).
+* Clients must invoke DeleteRecordingSchedule sending the id of the Recording (not RecordingDefinition in the case of Mediaroom) to delete within the recordingScheduleId. If several recordings must be deleted, client will have to request it through sequential requests (one by one)
-Clients must invoke DeleteRecordingSchedule sending the id of the Recording (not RecordingDefinition in the case of Mediaroom) to delete within the recordingScheduleId. If several recordings must be deleted, client will have to request it through sequential requests (one by one)
+* Since the behavior of DeleteRecordingSchedule in Mediaroom is "to remove the completed recordings on the STB", it does not make sense to request the deletion of a whole series, so '''method will return an error if it is invoked requesting an entireSeries deletion in Mediaroom'''.