For assignment 2, I was tasked with designing a web structure and data schema for the data set I am using. To do this, I reviewed the resources from webstyleguide and lucidchart to gain a better understanding of both information architecture principles.
As seen in figure 1 – my site structure takes on a mostly hierarchical structure. Sub-pages are accessed by first visiting or hovering over the relevant content or page. This then provides access to the sub-pages which sit underneath the parent category. I attempted to allow for internal routing as well – for example by accessing Resources you can choose between accessing an external link or being routed within the site to the College Scorecard sub-page of the Data category. This was an organization that seemed to make the most sense to me, however once actually implementing this structure I’m sure it would undergo revision. This process had me thinking about how a site should be structured and whether the most logical way is necessarily the most user friendly way.
For part 2 of my assignment, I was asked to design a database schema for my data set. This was somewhat difficult as my dataset is a “flat file” with most columns representing attributes of the University ID. I gave it my best shot, though, and focused on dividing into tables and eventually joining 3 key attributes. 1) The university’s key attributes such as size, type, tuition. 2) Its accreditation agency and the compliance needed to be accredited. 3) Its student post-graduate profile on earnings and debt. This wasn’t entirely a straight forward exercise because of the nature of my data, but I wanted to give it a thoughtful effort and tried to split the data as best as I could.
As seen in Figure 2 – the entity records involved ultimately direct to the Accredited College entity record. The idea is to bring all the information from the College record (basic facts), Accreditation profile/agency, and post-graduate survey and federal student loan reporting into the same record of Accredited College. The idea here is that the information is gathered in separate places, not all at once. In order for it to be joined together without significant mistakes, data integrity must be maintained along the way. For example, while each college is located in one state in the data, states can have many different colleges so we need the State to be separated and not stored with the college table. Next, since a University can be accredited by multiple agencies (regional accreditation, national accreditation, program accreditation), the accreditation profile for compliance needs to be separated as well. Overall, I felt this was a good exercise to think through and separate the dataset out logically.