Open isaactownsend opened 2 years ago
@isaactownsend we're currently reviewing this module internally. There's some benefits for those looking to get data out from sites. As you've mentioned, some options for conversion aren't necessarily available to end users.
@thisisalistairsaccount brilliant, thanks!
Infrastructure Australia has also requested this module to be added.
@thisisalistairsaccount just to update our internal team(s), what was the current status of this request?
Morning,
Any updates on the internal review?
Thanks, Isaac.
+1 to add this, it works very well for exporting data (via views_data_export) to CSV which is a common requirement with govt clients.
+1 to add this, current client moving to GovCMS SaaS from another hosting already had this but now losing the functionality. Any update on this one?
Looks like we've recently had a D10 version for this module come to fruition
Hey team,
Any updates on the internal review?
Cheers, Tony
+1
Hey @thisisalistairsaccount - is this module still being considered internally?
Morning @thisisalistairsaccount - any updates for CSV serialization?
What value does this module/package add to GovCMS?
This module allows views data to be exported in CSV file format, as opposed to XML or JSON.
Recreating this request form @joshua-graham-adelphi GovCMS8 issue queue (https://github.com/govCMS/GovCMS8/issues/395).
Several departments including DFAT endorse support (ticket above), now including our DAWE websites.
Please provide a brief outline of what this module does.
The module allows export to CSV files.
Who does this module benefit:
[ ] end users [X] content editors [ ] site builders [ ] themers [X] developers
How could you provide/replicate the functionality of this module using alternative methods, eg in your theme?
XML/JSON and conversion tools. Departments often have many of these "free conversion tools" blocked and it's not always appropriate to rely on these as sometimes data is not public.
Current solution is to write formatters in the theme layer which is becoming a grey area for writing module functionality in the theme.
If this module styles or alters HTML or JavaScript output, can the functionality be provided via the theme? What alternatives have you considered.
As above.
What is the maintenance and support status of the module. Describe the issue queue activity.
No critical issues. 41,000+ active users (very strong community) and maintained by Acquia as a supporting organisation.
What permissions are needed to utilise the module (and are any new permissions provided by the module)?
No additional permissions. Out of the box REST permissions.
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?
No database changes, just facilitates data export.
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.
Cached by Drupal cache API.
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?
Small module, all critical issues dealt with, very strong community. Have had experience using this on several sites over the past years and encountered no major issues.
Additional information
N/A.