A timeline of how it all came together. Click on the line to read in detail about each stage in the project.
Week 13In the final week of the project, the group was pre-occupied with some final touch ups- the editing of the film and getting our individual research papers together. Aoibheann covered the editing of the video, Lorraine built a last-minute photo gallery for the website, and both Cathal and Brian worked on refining some features and minor details of the app. We also managed to get our presentation together for the final review on Monday September 2nd.
Week 11-12On August 15th, having received permission from the Buildings Office in Trinity, we hung the laser-cut QR tags in each designated location within Front Square. We collected video footage of their erection, their use by the public and also the distribution of the leaflets we had produced the previous week. Unfortunately, on account of vandalism, four of the fifteen QR tags were stolen on the evening of the 18th. Luckily, as this was towards the end of the launch, it did not impact greatly on the collection of data.
Week 11 In order to promote the QRKY facts App and encourage use amongst visitors in Front Square, we designed A5 leaflets to be distributed during the launch. Using Adobe Design Suite, we developed a simple design which followed the colour coding of each topic, the QRKY facts branding and the aesthetic of the website. The leaflets included a brief introduction to the project, instructions on to how to use the QRKY facts App and also a map delineating the exact location of each QR tag in Front Square. The leaflets contributed to the number of users and so played an important role in producing more interesting statistics at the end of the launch.
Week 11 We decided that the collection and visualisation of data would enhance and expand on our project. Thus, in advance of launch week we began coding up aesthetic and visual info-graphics for inclusion on the website. These info graphics were developed with temporary statistics so that later we could plug in the actual data collected using Google Analytics during launch week. The info-graphics can be found on the STATISITCS page. The first uses a small JavaScript library entitled Raphael to produce interactive vector graphics and also dynamically feeds data into the chart using PHP. The second is static, but delineates the popularity of each topic on each day of the week. This info-graphic is built entirely using HTML and CSS3 only.
Week 10The website was designed to both analyse and compliment the web based app. Thus it follows a simple aesthetic to correspond with the visual design of the app, uses the QRKY topic colours and also simple descriptive imagery. The website also acted as a means of exploring the interactive and visual potential of using HTML, CSS, jQeuery and JavaScript in conjunction with one another. It also provided an opportunity to experiment with open source libraries such as Raphael and plugins such as BigVideo.js.
Week 9With the content gathered, the database underway, and the web app structure in place, it was time to begin creating the physical signs. It was important to us that the QR codes be as aesthetically pleasing as the app and website. We looked at some of the new methods of fabrication which are coming to the fore in digital manufacturing at the moment: 3D printing and laser cutting.
The company FabAllThings, based on Dawson St, agreed to help us create our digitally fabricated signs. On their advise, we cut and engraved our signs in different coloured 3mm thick acrylic sheets. As we had divided our questions into three categories (Pop Culture, Architecture, and History), we chose three colours to print each category on (Pink, Turquoise, and Navy respectively). Once we created an individual QR code for each URL, we began to work on them in Illustator, which can send files directly to the laser cutter. Colours needed to be inverted in order to make them legible once etched: The laser cutter etches white onto coloured acrylic. We also created a new laser-etchable logo for the signs.
Week 7-9The implementation of the server side programming took on several stages. As none of the group had worked with php before, nor was particularly comfortable with server-side programming, there was a large learning curve in this part of the project. Once the basics of the languages (PHP and MySQL) and how they interact with each other was mastered, it was a case of converting our HTML templates into PHP pages. The user interaction in the mobile application is powered by a HTML form that uses PHP to process these interactions. Through a series of if/else statements and some relatively straightforward MySql statements, it was possible to retain information about whether a user had selected “True” or “False” as their answer.
Cookies were then implemented so that users could be uniquely identified and also so it could be determined whether or not they had previously scanned a QR tag. If they had not previously scanned a QR tag they could be redirected to a special “splash” page that revealed information about the project. The use of cookies allows us to see more clear trends in individual users which can then be utilised in visualising data surrounding the project
Week 5-6As the kernel of QRKYfacts was the myths and stories which students know about Trinity, it was essential to research the stories to ascertain whether they are true or not. Conducting research into the history of Front Square seemed the best place to begin, for which the Glucksman Map Library proved helpful. The Early Printed Books Library was unfortunately closed for the summer, so its resource was inaccessible, however, the Glucksman contained a number of books about the early college grounds as well. While it gave some clues as to the medieval grazing rights on the grounds in front of Trinity (Hoggen Green), it did not hold any information regarding the statutes of the college.
In an attempt to find out about the old statutes of the college, we met with official tour guides of the university, the Registrar of the University, Shane Allwright, and a number of Professors from the law department, including Dr Eoin O’Dell. Dr O’Dell, expert on the more recent college statutes, was able to offer insights into the older statutes and what they may have said. Knowledge of them in limited due to the fact that they were written in Latin until the 19th Century. However, with Dr O’Dell’s help, we were able to verify or disprove all of the stories we had gathered.
Week 3-4 Our project went through numerous models and wire-frames, but ultimately we decided to create a location-specific mobile application. We wanted it to be location based in order to augment the user’s experience of the physical space with technology, but not replace it entirely. The requirement to be physically in the space in order to engage with the project gives legitimacy back to the space. Front Square is not only about the information you can gather about the buildings or the space, but how you experience the space as you learn.
The final idea for QRKYfacts was born from two main factors. The first of which was a technical problem: location detection, while the second was an ideological issue: physical versus virtual space. After we decided to impose a locational restriction, we needed to make sure we could detect location accurately, while not detracting from the user’s experience. Mobile GPS was our first avenue, however the GPS on even the most modern handsets was not precise enough to detect one point on a building from another. QR codes had been mentioned and dismissed early on in the project, however when we re-explored the idea, it seemed to be the answer to our technological problem: it requires the user to stand in close proximity. Our ideological issue was also answered: users would look for physical signs on the buildings around them and not to a blinking dot on their phone-screen, therefore augmenting their experience and not detracting from it.
Week 1-2As each member of our group had very different ideas on what direction to take the project in, we had to spend a large portion of the first few weeks brain-storming to find an idea we all wanted to bring to life. We looked at our space: Front Square, and tried to find some common interest, with little success in the beginning. We discussed the possibility of a game, or a tour guide app. Something humorous versus something serious. We explored our strengths and interests as well, and quickly turned towards a more aesthetic project. Whatever the content, we were all concerned with using the technology we have learned to create something beautiful. Something which engaged users as much for its form as its function. Once we decided this, it was a matter of how best to implement our ideology and where to look for content.
We all agreed that myths about Trinity were an interesting topic, especially since we had all heard them as students ourselves. We liked the idea of asking students what myths they know about the college. Should we have a virtual message board, where anyone could post stories and myths about each building around front square? Or should we provide the data and allow users to interact with it instead? In the end we settled on researching the content ourselves to ensure it was accurate and therefore relevant.
