The Process of Learning through a Project

“Give the pupils something to do, not something to learn; and the doing is of such a nature as to demand thinking; learning naturally results.”

― John Dewey

After working on this post for some time, I realized it would be best to break it up into a series of posts as it is getting quite long.  To start, I will explain my project and share the final product (actually a modified product for sharing purposes).  I will then share several posts that explain how I developed solutions to each part of the project and the learning that occurred.

Defining the Project
With data being the priority for so many decisions, my team was tasked with collecting numerous ratings from others.  The data included criterion-based ratings on a scale of 1-4 as well as we wanted to collect additional information gathered from check boxes and open-ended responses.  Because this data collection was important for us (but may not be as important to those inputting), we wanted to make it as user-friendly as possible.  Additionally, we wanted the end-users to be able to reference prior ratings (when possible) so they could be more informed while making current ratings as well as see trends.




I found this experience so valuable I wanted to share it!  Learning how to create these solutions by having an actual end-goal in mind truly epitomizes the quote above by John Dewey.  I find myself learning so much more when I truly have something to do!  Dewey also notes, "We do not learn from experience...we learn from reflecting on experience."  Therefore, I am hoping to solidify my learning by sharing it with you (as my way to reflect).

I do need to note I do have some self-taught programming experience from other projects: I have made simple websites using HTML (not CSS), have basic experience with C and Java...primarily in the realm of educational robotics, have dabbled with Javascript in Google spreadsheets, and have learned basic structure of database queries.  This experience is probably "above average"; however, almost all of my coding experience is from searching the internet, watching online videos, and testing code out.

The Final Project
The final product was a collection of webpages for data collection of self-ratings on specified areas (each page was a different area).  In order to collect the most accurate data, the form needed to include a variety of features as follows:

1. A customized form that included embedded mouse over features (to save space) that would display/hide more detailed information as needed;
2. Focused, specific past data from an online source that was located next to relevant form questions (this provided past ratings to inform current rating);
3. An automatic email response that included a PDF of the responses provided in the form in a easy-to-read format (basically a report of what was submitted).

Now, here's your chance to play with a sample of the end product!  Please note that any data you submit will be PUBLIC, so keep that in mind if you fill out the form.

Here is a image (and link if you click on the image) to a sample of the final product:

And...if you want to see the data submitted using this form click here to go to the Google Sheet.  If you do not want to enter an email address, you can still see the auto-generated forms in this folder.
NOTE: If you go to File --> Make a Copy, you will have access to edit the spreadsheet AND form.

In future posts, I will share how I was able to develop this end product.  These posts will include most of the key resources that I found and share my insights into these solutions.  To help you find a feature faster, each post will focus on a key feature that could be implemented on its own.  My process to the solution may seem linear as I explain it, but it often was a result of jumping from one feature to another and tinkering with solutions.  Here is a synopsis of the future posts (links will be added as posts are completed):

1. a customizable method to collect information from the user (preferably with Google forms),
2. detailed descriptive information for the user so they select the correct rating on the form without overcrowding the page,
3. access to past data so the user can make a more informed rating (and possibly see trends),
4. a record of what was submitted sent to the user (without having to create too much work for myself).

Knowing these "must-have" components really allowed me to keep focused as I tried many different solutions and gave me an easy way to gauge if I was successful.  Knowing this end-goal, I began searching for solutions.