Home » Uncategorized » Co-op 2 Highlights 14

Co-op 2 Highlights 14

It’s funny, but I have been about a week behind all semester – I’m not sure how that happened, but we’ve come down to the last week of classes and I will be posting #14 here today and #15 sometime in the couple of days.  I met last night with the capstone instructor and we tweaked just a couple of things on VARI (Vineyard Attendance Reporting Index).  One of those was to show just one date near the delete button instead of looping through the model to see how many events could have occurred on that day (it could be 2 at Middletown or 10 at Tri-County).  I didn’t want to have 10 dates of the same date showing next to the delete button.  The other thing we tweaked was styling my back/cancel button to make it look like a button, while really being a link.  There are several opinions and ways about how best to do this.  With MVC, you can’t have more than one submit button on a form, so one way to get around that it to have 2 or 3 forms on a web page, each with their own submit button.  With the situation of a cancel button, it doesn’t really get ‘submitted’ anywhere, it would just redirect the user back to the home/starting page, so it’s more like a link in that aspect.  This post, from StackOverflow, gave some options on how to do that.

I’ve started adding in the historical data from the original Excel spreadsheet, so that everything is converted over to the SQL database.  This is easy in a way, but time-consuming.  For things like the Saturday night church service or the Wednesday or Friday services, those are all listed with the Sunday date for that week, so the dates need to be adjusted for each of those.  I’m unsure yet about how much historical data to include, but for now, I will import the last year to be able to provide some decent reporting comparisons.

Reporting – the final hill!  One of our web/IT people at work suggested using the Google Charts API and I’ve begun implementing that.  It almost seems to easy!  I need to read up on how to connect my datasource (the database) to the Google javascript, so that the chart is pulling data from the database (and not the pizza array that Google gives as an example).  There has never been really great dynamic ways of reporting on the attendance data, so I think it could prove pretty valuable.  It’s one thing to see a plus or minus number on an Excel spreadsheet and say ‘oh, we are down for the month,’ but it is a whole new world to see that represented in color on a pie chart or bar chart.  This introduces the infographics topic again – I think I wrote about that earlier this semester or last semester.  Infographics are graphical representations of data.  The use of color, trendlines, sizes, and shapes really help to convey the meaning of the data they represent.

I’m planning to present this project to our IT team and a couple of other interested parties at work next week.  Then, I can get feedback and together, we can determine if it is a useful enough product to present to the leadership team and possibly launch for real-world use.

One thought on “Co-op 2 Highlights 14

  1. Google charts API will work out so well in our environment! I’m glad that the data conversion has gone smoothly. I agree that capturing data from one year out is a good place to draw the line on this project.
    It is exciting to see this all come together. Great work Kim!

Thoughts?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s