>The timestamp at which the current flow through the funnel began >(will need to be stored in a cookie and reset at loads of step 1) I would strongly advise against using cookies for this purpose. Cookies will easily get bloated if we set a precedence of using them to 'support' event logging metrics. Bloated cookies are a concern from both the performance and architectural stand point.
On Wed, May 14, 2014 at 2:58 PM, Aaron Halfaker <[email protected]>wrote: > Hey guys, > > Here's how I'd do it. > > *Assumption:* Only logged-in users can start the UW funnel > > *Schemas:* > > UploadWizardStep > > Stored when the user loads a new step of the Upload Wizard > > > - user_id : int -- The user's identifier > - flow_initialized : str -- The timestamp at which the current flow > through the funnel began (will need to be stored in a cookie and reset at > loads of step 1) > - step : int -- 1 - 4 of the UW process > > UploadWizardRightsSelection > > Stored when the user selects a "rights" option. > > > - user_id : int -- The user's identifier > - flow_initialized : str -- The timestamp at which the current flow > through the funnel began (will need to be stored in a cookie and reset at > loads of step 1) > - rights_selected : enum("own", "other) -- The rights that a user > selected (note that multiple selections actions can take place for a single > flow) > > I'd make a pass over the DB, to identify the last RightsSelection for each > flow_initialization (if any) to figure out what an uploading user settled > on during a particular flow. I'd also look at how many selections a user > makes per flow to see evidence of confusion & indecisiveness or maybe just > exploration of the UI. > > Make sense? > > -Aaron > > > > > On Wed, May 14, 2014 at 3:53 AM, Gergo Tisza <[email protected]> wrote: > >> On Wed, May 14, 2014 at 1:16 AM, Lars Aronsson <[email protected]> wrote: >>> >>> Yes. But is this a given fact, or something that might change? >>> >> >> We do intend to change it. You can see out plans (in a somewhat >> undigested form) at >> http://etherpad.wikimedia.org/p/design-multimedia-uploader >> But usage metrics from the current interface can still be helpful for >> designing a different one. >> >> So how much energy and resources are we >>> spending on making it slightly better, rather than designing >>> something very different? >>> >> >> That's the million dollar question... given that small improvements will >> have instant effect (but is wasted time in the long run), while a big >> redesign will take several months (I am being optimistic here...), we will >> have to do some mix of the two, but exactly what mix that will be is an >> open question. >> >> _______________________________________________ >> Analytics mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/analytics >> >> > > _______________________________________________ > Analytics mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/analytics > >
_______________________________________________ Multimedia mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/multimedia
