The FSA signup form on Bedrock (https://www.mozilla.org/en-US/contribute/studentambassadors/join/) currently sends information into 2 different data extensions in ExactTarget: Master_Subscribers (to host newsletter subscription information) Student_Ambassadors (to host FSA program specific field information) This program's data is being integrated into SalesForce CRM this quarter (Q3) - and will be synced across the 2 systems (SalesForce + ExactTarget) on an ongoing basis via an IT software service: Dell Boomi. (Hooray, we don't have to make Basket talk directly to SalesForce AND ExactTarget!) However, there is an extensive bit of cleanup work for the data so that it can be properly setup inside of SalesForce. We're cleaning up this data retroactively, but will need to make sure we have a way to make sure that data is vetted/clean before it goes into ExactTarget moving forward. Crux of data quality: we need to standardize these 2 fields: University City In addition to standardizing these 2 fields, there needs to be some changes made to the form in general. This needs to be spec'ed. Creating this bug as a placeholder to get work spec'ed on this in Q3, so that changes to the form can be made in early Q4. (Per convo on 7/16 between Michaela and Ben S. - this is a priority in early Q4.)
Note: In Mozilla Communications section, "Firefox Flicks" and "Firefox for Android" need to be removed. We may want to add "Firefox OS + You" signup here. TBD.
Should we remove the two mentioned for now? or wait for additional communication?
If it's "easy" to remove the 2 mentioned, and leave this bug open for the additional improvements on this page, then go for it! If it's better to wait and make all the changes at once, then it's okay to leave as is for now.
For business case and requirements, See https://docs.google.com/a/mozilla.com/document/d/1MKvLTF0H8UXvQRNlsMt2i3fd67aSjoQOsh8dBtzry2Y/edit?usp=sharing
Jessilyn: This bug was brought to my attention as blocking CRM work. Can you give a status update. Should this still be resolved in Q4? If so, do we have enough information to move forward or are you still spec'ing things? Thanks!
Ben, It is blocking CRM work; however, it was punted to start work in early Q4 (per #c0 and https://docs.google.com/document/d/11UeacKqgxJr8yGHEMgahQDNivVzBFh-T6xf8P3pqVDU/edit ) - and at the beginning of Q4 we realized the need for the email platform Audit, and potential re-architecting of our email system (Bedrock/signup forms + Basket + ET + Boomi + CRM); thus this bug became stalled. There's enough information in the business case and requirements that Sean put together in #c4 to begin thinking about how to solve; however, I'm unsure if we want to spend dev resources solving with Basket if we end up re-doing our calls/system. Do you have a recommendation on how to approach this bug?
Let me read through the docs here and come back with a recommendation.
Jessica: How many entries has this form generated in the past year.. on average how many per month?
Here are my thoughts on each of these. 1. Standard School Name The traditional way to do this is via an auto-complete on the signup form that pulls from an exhaustive list. However I do not think this will work here as we would need an exhaustive global list of schools. An alternate would be to use existing schools entered into salesforce, this way the most popular schools would auto complete. We would need to investigate if salesforce provides a webservice that supports this. 2. New School Name I think this notification would be on the salesforce side. 3. Confirmation of new entry. I think autocomplete based on entered data in salesforce solves this problem. 4. City Standardization. a. Real City - this would be hard to confirm automagically since this is a every city in the world :) b. City in selected country - see above c. Correct Case - JS validation on form, easy. 5. Last Name Correct Case JS validation on form, easy. 6. First Name Correct Case JS validation on form, easy. 7. Prevent Bad Characters JS Validation on form. 8. Under 18 Warning Does this warning occur in salesforce or on the form? Is this really needed as users must check a box stating they are over 18? 9. Remove Flicks & Android Easy, form edit. I will need-info pmac to verify the above. I do not see anything here that involves basket. This is all bedrock + salesforce. From my perspective the big question for #1 is, does salesforce expose this data in a manner that we can use? So we will need a contact on their side to ask.
I agree with all of this. The form should remain mostly dumb apart from the basic validation things like characters and capitalization. If we can get some info from the salesforce API about school names we already have then great, otherwise it should be on the salesforce side to recognize when a new value is added and flag it as such. And I don't know of a way to validate every country/city combination in the world. That data changes so often that I doubt such a thing is reasonably possible.
5k from June 17 - today 400 for Nov 1-17 200-250/week
Based on the meeting on 11/18, I am going to break this out into individual bugs and use this as a tracker. So expect lovely bugmail shortly.
Jessilyn: I converted all the bedrock tasks to sep bugs. There are a few tasks in here that we think are salesforce (2 and possibly 8), you should file those in what ever system you use to manage salesforce tasks.
Hey Jess- Is this still an open bug or can I close? Thx, Jen
Would like to keep this bug open - but will reclassify it out of Bedrock component. Putting it in Marketing -> Newsletters as a placeholder. Sean/Joel - we should find a place to file SalesForce CRM specific bugs and: 1) Reclassify this bug in that component 2) File a new bug that blocks this bug to accomodate item #2: How to handle entry of "New School Name" into a place to be vetted before adding as a new Account in SalesForce. I assume these 2 Salesforce bugs would be assigned to the new CRM Admin to triage and figure out how to fix?
Component: Bedrock → Email
Product: www.mozilla.org → Marketing
Version: Production → unspecified
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.