Open Stack

Can you explain what normalisation you would like to do ?

Tim

From: Jimmy Mcarthur [mailto:jimmy at tipit.net]
Sent: 31 March 2015 18:10
To: user-committee at lists.openstack.org
Subject: Re: [User-committee] OpenStack Surveys moving forward



March 31, 2015 at 8:12 AM
If we create new rows for new data entry for an existing deployment, can we keep the same deployment id ? It is useful to have a unique identified for each deployment, especially if we eventually get to an automated way of reporting the current deployment state.
Right now we're maintaining the deployment ID and re-populating questions from the past survey, where appropriate. That way users have a head start on the survey and can update data where appropriate.


We're not adding a huge number of questions each year so if it is easy to change the technology, that's OK but it would seem like a lot of work only for the delegation rights on its own.
This year was a bigger lift than previous years, but you're right it's not a big shift from survey to survey. The driving force IMO is to normalize the data.

Thanks!
Jimmy


From: Jimmy Mcarthur [mailto:jimmy at tipit.net]
Sent: 31 March 2015 00:49
To: user-committee at lists.openstack.org<mailto:user-committee at lists.openstack.org>
Subject: [User-committee] OpenStack Surveys moving forward

Hello all -

We've been working on the development side of the user survey for OpenStack Foundation for the last two years. During that time, I've noticed a few issues which we'd like to address with the help of the stakeholders.

* Because of some earlier limitations with Silverstripe, the data isn't normalized. I'd like to propose a true relational data model. This is a problem for many reasons: data analysis, ease of updates, year over year changes, etc...
* Users are updating the same Deployment and Survey rows year over year. Literally we're writing over historical data, which eliminates our ability to track data trends for companies and deployments.
* Due to the current data model, updating the survey must be done by someone familiar with Silverstripe. I would propose a survey builder, built around the needs of the most current survey. This should allow the User Committee to create/edit their own questions and answers, including the style of the question (e.g. radio buttons, checkbox list, ranking of answers, etc...)

We would be happy to put together a blueprint of what we're thinking, but I'd like to first get general feedback from you all. You're much more familiar with both the data and what you want to do with it than we could ever be, so we welcome any input you might have in improving the process of both creating the surveys and managing the data.

Thank you!
--
Jimmy McArthur / Tipit.net<http://Tipit.net> < jimmy at tipit.net<mailto:jimmy at tipit.net>>
m: 512.965.4846
o: 512.481.1161

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20150401/2c85e56c/attachment.html>