monicapatel21
commented
1 month ago Works in most cases; annoying in some cases:
Special Requests Issues
- Not standardized
- Need customizations to each events form
- Sometimes form gets posted in multiple places
- Translation -- twice as much work, some differences in how fields are handled (e.g. data in portuguese)
At event set up, have admin-user put in more information about fields they want to collect. A custom form for each event based on field admin-user has checked.
Cross posting often goes beyond wri.org and IOs (Land and Carbon Lab uses this approach) -- embed form dynamically over JS. Based on ID, form gets pulled through and form parameters are stored elsewhere. So we can integrate this feature outside wri.org
Need: Research technical drawbacks of embedding via JS Pro: Allows us to go outside Drupal / We'd use another webservice for the forms.
Event hosts want a list of all registrations outside of Zoom and Orto (we don't want all data they collect in Orto) (they still want to know the answers to their specific questions and then bury the default questions under those questions)
More central content repositories (staff, events) so we don't have to create in multiple places (it gets ported where it needs to from the main place).
Status
No emergencies or urgent issues, pause until early October and then see what requirements we can build out for current needs. 1.5 version can address some of the above and then we can keep going.
Now that the initial functionality is in the wild we want to discuss next steps.
issues
multilingual sites are importing data incorrectly (dupes)?
improvements
Building new forms: we're getting requests for variants on the form fields, we may need a more robust module that lets us build event forms more easily?