Recording requests

The Recording Requests report lists all the recordings made on the system over a period of time. The reporting period is end-user selectable.

Availability

This report is available where all of the following module versions (or later) are present:

LKR: 2.8.4

UAV: 1.1.6 (provides userUID support for authorisation checks at the API level)
CDG: 1.1.12 (requires full metadata transfer from CDG to UAV)

Report columns

Column name	Description
accountNumber	The STB user's account ID.
CreationDate	The day of the request.
programmeId	The ID of the programme recorded.
deviceType	The type of device.
isprotected	Whether the recording has been protected by the user.
availabilityEndDate	The date up to which the recording will be available for playback.
title	The programme title.
definition	The display definition of the content.
eventId	The ID of the programme.
locale	The locale of the programme.
language	The language of the programme.
serviceRef	The channel reference.
seriesRef	The series that the recording is be linked to (if any).
contentRef	The actual content ID.
isCatchUp	Whether the content is catchup-enabled.
isStartOver	Whether the content can be started over.
periodDuration	The duration of the programme.
periodEnd	The start of the programme.
periodStart	The end of the programme.
ratingCode	The programme rating.

Input parameters for report generation

Parameter	Type	Description
Lower date threshold of report period	DateTime	Start Date for the report, including the specified value.
Upper threshold of report period	DateTime	End Date for the report, including the specified value.

Data extraction files

The data extraction files can be found in the "/opt/npvrlocker/reporting/bsm/etl" directory. The following file is is used for this report:

Extraction file

Summary

Notes

Query

npvr-activity-notifications-uav.ktr

Transforms data from the UAV's cassandra database to the reporting Mongo database to support activity type reports directly in BSM's "uav_activity_notifications" collection.

Data in the UAV activity_notifications collection is timestamped to expire after a specified period.

This extraction will retrieve all the data and insert it into the BSM reporting MongoDB, thereby eliminating duplication, and enabling the system to take only the latest data from UAV, rather than replacing the MongoDB collection with a full copy every time the extraction is run.

SELECT * FROM activity_notifications

BIRT design template file

File name	Summary	Reports collection	Query
STBPlayoutReport.rptdesign	STB Playout Reports	npvr-account-sdp	{ "collectionName" : "uav_activity_notifications" , "findQueryExpr" : "{name: 'record', value: 'Success'}}

Sample report

The following image shows an example of a Recording Requests report:

Sample CSV export

The following shows a sample of a CSV report export:

Field	Row 1	Row 2	Row 3	Row 4
AccountNumber	SUI-ZZ33NQ	SUI-ZZ33NQ	SUI-ZZ33NQ	SUI-MGSJXX
CreationDate	May 22, 2015	May 22, 2015	May 22, 2015	May 22, 2015
ProgrammeId	NPVR-EVT-101	NPVR-EVT-102	NPVR-EVT-103	NPVR-EVT-102
DeviceType
isprotected
AvailabilityEndDate	May 22, 2015	May 22, 2015	May 22, 2015	May 22, 2015
Programme.title	NPVR-Football	NPVR-Locker1	NPVR-Football	NPVR-Locker1
Programme.definition
Programme.eventId	101	102	103	102
Progrmme.locale	en_GB	en_GB	en_GB	en_GB

Programme.language
Programme.serviceRef	NPVR-CH-001	NPVR-CH-001	NPVR-CH-001	NPVR-CH-001
Programme.seriesRef
Programme.contentRef
Programme.isCatchUp
Programme.isStartOver
Programme.periodDuration	7200	7200	7200	7200
Programme.periodEnd	Jan 17, 1970	Jan 17, 1970	Jan 17, 1970	Jan 17, 1970
Programme.periodStart	Jan 17, 1970	Jan 17, 1970	Jan 17, 1970	Jan 17, 1970
Programme.ratingCode	13	13	13	13