Add views_data_export module to GovCMS8

[saifullahakber]

** What value does this module/package add to GovCMS?
Views listing page with big data will be easy for users to download in excel format.
** Please provide a brief outline of what this module does.
When you create a page with views and display huge number of records it will take so much time to load all in same page or you can have pagination. But sometime user do not want to go via pagination. They would like to see all in one page. The best way they can view the full data records of a views page is download that data records in excel format.
** Who does this module benefit:
[x] end users
[x] content editors
[x] site builders
[ ] themers
[x] developers

** How could you provide/replicate the functionality of this module using alternative methods, eg in your theme?
There is no alternative option for SaaS platform
** If this module styles or alters HTML or JavaScript output, can the functionality be provided via the theme? What alternatives have you considered.

** What is the maintenance and support status of the module. Describe the issue queue activity.

** What permissions are needed to utilise the module (and are any new permissions provided by the module)?

** Does the module modify the database structure and/or store additional metadata on nodes or other entities? If so, why? What are the risks for future updates?

** Is the module designed to capture anonymous user data?
No
** Is the output of the module typically fully cacheable? Would the inclusion of this module potentially render pages uncacheable.

** What is your assessment of the quality of this module, the contribution history of the module's maintainers, and the uptake of the module within the Drupal community?

** Additional information

[saifullahakber]

Hi,
Is there any update on this @thisisalistairsaccount ? Do you any more questions? Please let me know. This is one of our priority task and top business requirement. Thanks

[thisisalistairsaccount]

@saifullahakber we require information on the following fields which weren't initially provided before we consider a module request:

** If this module styles or alters HTML or JavaScript output, can the functionality be provided via the theme? What alternatives have you considered.

** What is the maintenance and support status of the module. Describe the issue queue activity.

** What permissions are needed to utilise the module (and are any new permissions provided by the module)?

** Does the module modify the database structure and/or store additional metadata on nodes or other entities? If so, why? What are the risks for future updates?

** Is the output of the module typically fully cacheable? Would the inclusion of this module potentially render pages uncacheable.

** What is your assessment of the quality of this module, the contribution history of the module's maintainers, and the uptake of the module within the Drupal community?