Severity: 8192
Message: Return type of CI_Session_files_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 132
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 292
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 166
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 235
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 315
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 356
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 282
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 294
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 304
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 314
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 315
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 316
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 317
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 375
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 110
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_start(): Session cannot be started after headers have already been sent
Filename: Session/Session.php
Line Number: 143
Backtrace:
File: /home/igmpiindia1/public_html/www.imciindia.org/imciblog/index.php
Line: 315
Function: require_once
After nearly two years of discussion, the merger of the Lok Sabha TV and the Rajya Sabha TV has finally been announced and will be replaced by a single entity Sansad TV. On March 1, retired IAS officer Ravi Capoor was appointed the Chief Executive Officer of the channel.
Under the banner of Sansad TV, sources said, Lok Sabha TV will continue to telecast live proceedings of the Lok Sabha and Rajya Sabha TV that of the Rajya Sabha.
Notably, in November 2019, after deliberations between Lok Sabha Speaker Om Birla and Rajya Sabha Chairman Venkaiah Naidu, a committee headed by former Prasar Bharati Chairman Surya Prakash was set up. It submitted its report in February 2020, regarding the merger of Lok Sabha and Rajya Sabha into Sansad TV.
Why the decision?
Lok Sabha Television was launched in 2006 by then Speaker Somnath Chatterjee, while Rajya Sabha TV hit the airwaves in 2011.
Apart from broadcasting the proceedings of both Houses of Parliament, the channels aired discussions and other programmes on a range of topics. According to sources in the two channels, the secretariats of the two Houses started deliberations on the merger in 2017.
On 7 November 2019, a committee was constituted and tasked with chalking out the modalities of the merger, and preparing guidelines for pooling of resources and technology.
The panel was headed by former Prasar Bharati Chairman A. Surya Prakash, and its members included additional secretary to the Rajya Sabha Secretariat A.A. Rao, Ganpati Bhatt of the Lok Sabha Secretariat, RSTV financial adviser Shikha Darbari, Manoj Kumar Pandey, and Dr Aashish Joshi, former LSTV CEO. The committee held several sessions with parliamentarians across parties.
A senior official associated with LSTV told The Print that the panel said in its report, submitted last year, that there should be just one integrated channel for Parliament.
“There was a lot of duplicacy of efforts and resources between the channels and this was leading to an additional financial burden. The merger came through because of that,” the official said.
“For instance, the office space hired by RSTV at Talkatora Stadium had Rs 30 crore as rent, which was later reduced to around Rs 16 crore, but that was also too high,” the official added.
The new Sansad TV, the official said, will function from the same space as LSTV at Delhi’s Mahadev Road.
Panel chair Surya Prakash described the merger as a welcome step that will provide a more integrated approach to the parliamentary content that is broadcast.
“It will reduce additional burden on finances by pooling in the resources of both the channels and synergising the broadcast of parliamentary proceedings through an integrated channel that will not compete with any private channel and will have a different mandate,” he said. Former editor-in-chief and CEO of LSTV Joshi offered a similar assessment, saying the step will go a long way towards synergising parliamentary content, and reduce additional financial burden.
How will the move pan out?
Sources in the channels said the merger panel had said in its report that there should be two separate channels under Sansad TV — Sansad 1 and Sansad 2. This is aimed at serving two purposes — to ensure parliamentary proceedings of both Houses can be telecast simultaneously, and, in times when Parliament is not in session, to cater to English and Hindi audiences. A senior official privy to the report said Sansad 1 was mooted as the channel for Lok Sabha proceedings and Sansad 2 for Rajya Sabha proceedings. When Parliament is not in session, the first channel can air Hindi content and the second, English content, the panel is believed to have recommended. “The Sansad TV umbrella… will be headed by a single person. But there are plans to have two different channels under it on the lines of the recommendations of the panel so that content of both Houses can be aired equally and all audiences can be catered to,” the official said. A lot of the programmes on Rajya Sabha TV, the official sought to note, were in English. Both channels are likely to have separate editorial heads. A few sources said a Doordarshan channel could also be engaged to air some of the RSTV proceedings. However, several aspects with respect to human resources and funds will now need to be streamlined, the aforementioned official added. Apart from airing the parliamentary proceedings of the two Houses, Sansad TV will air multiple daily and weekly programmes on news and current affairs, on the themes of democracy, and awareness of the Constitution, among others. During the times Parliament is not in session, there will be several common programmes telecast by the channels, sources said.
02-03-2021
Copyright © 2023 Institute of Marketing Communications India (IMCI®) . Trademark duly registered under The Department of Industrial Policy and Promotion Ministry of Commerce & Industry, Government of India. Trademarks are the property of the owner. All Rights Reserved