Thursday, 28 May 2015

App Accomplished

The absolute final steps of modifying and completing the app had to be finished by the end of last week (ish). From the invaluable points of improvement provided to me by those testing the app at Breary Banks, I was then able to alter the scripts of the audio for each stop and record myself (which did get a bit repetitive!). For the Memorial and Tree stops, all that was needed was to give practical guidance to the audience, for example to point out that the site was private property and not to enter the fields (otherwise, the sheep wouldn't be too happy!). However, the final audio for the trench had to be changed quite drastically due to the difficulty of navigating yourself to the position on the pathway. The other two stops were very emotive and engaged with the participant's senses so that they feel more involved with the landscape's history. This injection of appealing to the audience's imagination had to be inserted into this script, for example, imagining the sounds of boots marching, the soldiers 'chatting' to one another, which I think added to the content and individual stories. 

Once again, we spent most of the day with Tom Smith, to work on the visual effects on LiveCode for each stop. The idea for the Tree stop was to dissolve a photograph taken by us with one taken 100 years ago to give the audience an idea of the structure of the camp and how to orientate themselves, and then loop the imagery. To do this, we created a video using iMovie, with text inserted to differentiate the different time periods (but it's pretty obvious when you look at them both). 
Screen shot of the present day 'tree stop' 
Screen shot of the dissolved effect from the present day to 100 years ago
Following on from this, I had to create a similar effect on the Trench stop, as those who've tested it on site commented on the confusion of finding the firing range and the focusing on the connection to the audio. By creating yet another video using the same software, I was able to use the photo we took on site and highlight the firing range and zoom in, so that the audience can look at their screen and be able to see what they are meant to be seeing! This worked really well, as now you won't be worrying that you are looking at the wrong field, and you'll be able to engage with the audio and the surrounding landscape. 
And finally, the Map page had to be modified so that each stop was easy to find, going in an upwards formation up the road/pathway. 

Screen shot of the firing range being brought into focus.

Screen shot of the transition from the above image to a close up image of the
firing range.
Screen shot of the firing range which will be seen on the mobile's screen.
Screen shot of the 'Map' page, we've circled the three stops so visitors can
direct themselves and have a more direct impression of how the app operates. 
Hopefully, now, this is the end! Since going to Breary Banks to see how the first draft worked, it made me realize how beneficial it was for the whole organisation of the app and to highlight other practicalities that were thrown at us. For me, only being on site for 5 days caused a few problems in that I had to take in every detail straight away, from where visitors would be parking which would dictate where my first stop would be (this would most likely be by the Memorial), having to state that the site was under private ownership and the weather played a big factor in what the audience will be able to see or not see. Now, the next step is to send the app and get feedback from various stakeholders, other staff members in the Department here in York and the Nidderdale First World War Project, such as Amanda Walters who supplied us with invaluable resources and information. I've devised a survey in which those who receive the app can write as much or as little as they want about each individual stop. They probably won't be able to make it to the site to test it out for the full experience (most likely, they'll be in a warm, wind-free room, which is not what Breary Banks is like at all!), but by getting their critical responses, we will know whether we have satisfied the expectations of bringing Breary Banks closer to the public and being more accessible. 

Monday, 18 May 2015

Time to Tweak

After the madness of last week, we were finally going to see how the app was going to work on site. It was the last day of excavating, so this was our last chance to be able to test the overall format and use of the app with others (such as students and supervisors) to get their responses. 

For practical reasons and to avoid confusion with the participants, the whole app was made into a video, so the cursor would move by itself to each stop, therefore the participants would only have to press 'pause' to stop the video after each stop. Both Sara and I used the guide when we first arrived, and it wasn't as bad as I expected! Our main improvements were the quality of the audio, which was slightly crackly making my voice sound slightly robotic and some of the content/order of content might have to be re-arranged and re-written.  
Me taking Dr Jonathan Finch through the format of the app
(photo by Dr Sara Perry)
Me taking a student through the app
(photo by Dr Sara Perry)
I guided and recorded the module leader for the Excavation Fieldschool, Dr Jonathan Finch, and two students who had been taking part in the excavation for the last three weeks through the app. There were no major faults that were detected, just little niggles that could've been portrayed better. For example, the 'Trench' stop is probably the most problematic in being able to navigate where you are supposed to look, especially if you didn't even know there were training trenches there! We found a way around it, replacing the existing visual imagery on the screen with a photograph of the fields that the participant is meant to be focusing on, annotated to illustrate the features. Other than some of the content being re-written or being put in another order, the differences between someone who knows a lot about the site's content and students who haven't been able to appreciate the wider landscape because they've been covered in mud all day was quite apparent. Jonathan mostly picked up on the content, whereas the students picked up on trying to be more specific in clarifying particular features. 

The day finished around 2pm, and as a celebration of finishing the excavation, we all went for a tour around Theakston's Brewery Visitor Centre in the nearest village of Masham and enjoyed a free drink - which certainly woke everybody up!

Next, time to completely finish the app! 

Tuesday, 12 May 2015


To understand the makings of a museum environment and the behind-the-scenes experience, I undertook a day of volunteering at the Yorkshire Museum in the centre of York. For most of the day, I was based in the Roman Gallery interacting with members of the public, conducting a survey about how the displays and the overall presentation could be improved. As I progressed through the day of listening to the same video over and over again, I actually had some very pleasant conversations with people, who enjoyed their experience of the Museum and its beautiful surroundings. However, as you can imagine, on a sunny Friday, it was pretty quiet. Kids soon emerged and dictated where the adults went, so that was fun and loud. At about 3pm, the Curator of Archaeology, Natalie McCaul, saved me from standing up any longer and asked me to do some research for a teaching programme, on an Iron Age bronze and copper alloy horned God, quite possibly Brigantia, the Goddess of the tribe Brigantes who was situated in the North of England. 
Replica of a Roman mosaic floor in the gallery (photo by author)
It was interesting to see how other forms of communication in interpreting archaeology and heritage are incorporated into the format of a museum. From experience, museums can have too much information to take in and you can feel a bit lost as its content has to appeal to multiple audiences. You normally have to visit a few more times to feel that you have covered the whole spectrum of its information. But the Yorkshire Museum's multisensory and interactive content is engaging and well done. So much so that I went back again the next day as a visitor!

In relation to my app, its content will be minimal in comparison to that of a museum. Being an audio guide also will enhance the user's engagement and be more of a tactile experience with the surroundings. I appreciate the work that museums do and was grateful for my time there. It's made me realize that heritage interpretation is varied and is being developed constantly to satisfy the user's participation. 

Working Wonders

Early last week, it was full steam ahead. After collecting all the appropriate content for the audio, my Module Leader, Dr Sara Perry, went to site whilst I stayed in York writing up the scripts for each individual stop. By doing it this way, I could then email the scripts to her and then Sara would read it out loud to see how long the breaks in between paragraphs would be, whether the directions I was giving were relevant and easy to follow, etc. Because I wasn't present on site, it made it a lot harder for me to orientate myself! Sara then emailed me back the script for me to record. I had decided not to have the Chapel as a stop, purely because I could not find enough content to support the audio, which was a shame as no one seems to know an awful lot about it. This back-and-forth process, with one of us on site, and one back in the lab at York was actually really effective, and highlighted the importance of getting the audio and other content right in terms of its connection to the landscape.

Mind map for the app title
(photo by author)
Back at King's Manor, the whole first draft of the app had to be completed. Once again, Simon Davis was on hand to assist in editing the three scripts on the software, Audacity. When I was in my room on campus recording the audio, I was conscious of getting the right tone, so not to sound too enthusiastic but to not sound monotone and uninterested, so finding my 'voice' if you like took a while. Listening back to the audio, there were background noises (shuffling paper, breathing etc), long gaps which proved unnecessary and some stumbles/re-starting of sentences which obviously had to be erased. I learnt that you could spend hours on one recording to get it spot on, but we had 2 hours to ideally do three recordings - so it was quite repetitive in listening to the same bits over and over again! I learnt that I had to be brutal in erasing the pauses, again, by not being on site and not knowing how long the user would need to break for (to look for certain features etc) was tricky. So after 2 hours, I had one recording which was cut down from 6 minutes to about 2 and a half, the process feeling very long, but the outcome being very short!

A screen shot of deleting background noise in Audacity (photo by author)
Screen shot of home page of mobile app (photo by author)

I was then able to edit the other two scripts back on campus, ready for the following Monday, when both Sara and I would test the app on-site. Following on from this, in the afternoon we met up with Tom Smith once again, so we could construct and finalize the app's format on LiveCode. We began by designing the home page: I'd done a black and white sketch (well, a pencil sketch), which we scanned into the Drive and then I drew an outline of the huts that would've been the focal point of the site. These huts we thought could be the buttons to lead you from one stop to the next, but we ended up lining them up next to each other, to create the illusion of them being how they would've been 100 years ago. My next task was to learn how to import audio into the app. On each card I had inserted two buttons, a 'play' and a 'pause' one which would then correlate to the playing and pausing of the audio. By selecting the button, and clicking on 'code', I was then able to insert a script code as to what I wanted the button to do once I clicked on it. I then repeated this method for the next two cards. 

Screen shot of importing audio (photo by author)

After a whole day of basically making the entire app, making sure the visual imagery, the audio, the content and the design of the app was usable (at least), I then was able to continue this process over the weekend of completing the editing of the audio, making sure the codes were in the right place and took you to the right page and any other small details were perfected. Then hopefully, it will all work out on the Monday! 

Tuesday, 5 May 2015

Stop By Stop

Entrance to Breary Banks, with a few sheep! Credit to Alice Toso
Being chased out of a field by a flock of sheep was not something I expected to happen whilst I was on site last week. They certainly made themselves known! I went to site to gather more content about the history of the site, to establish my four 'stops' for our forthcoming audio guide and to get a firsthand account of the changeable weather that is unpredictable, to say the least. Before I went to site, I was introduced by the university's E-Learning Adviser, Simon Davis, to a computer software called Audacity, which enables you to edit all formats of audio. I will use this once my four recordings have been completed to ensure my audience can clearly understand the spoken content for each stop. Since the weather in the remote village of Colsterdale is pretty erratic, it would be preferable to record each audio file in a quiet studio/room, so no interference is detected. I was also presented, by the university's Collaborative Software Specialist Tom Smith, with another resource called LiveCode, which will provide my framework for building my app, so I will be able to insert commands and audio within a card that will measure up to the format and size of an iPhone 5 (and, eventually, other mobile devices).

A long-standing feature of the site and a stop for the app
Credit to Alice Toso
By having this information at my fingertips, I was then able to develop a storyboard of what my app would look like visually and interactively. It will be fairly fragmented, as the stops can be accessed and listened to in any order. If you visit this site having downloaded the app, I would recommend starting at the Memorial to the Leeds Pals, as this is what sets the scene, if you like, by illustrating the context of the site. From there, you can either turn right to go back down to the start of the road, or turn left to go up to the end - either way, it doesn't really matter.

The entrance to the village, with the Chapel located to
the left of the image.
Credit to Alice Toso
The second stop could be the Chapel as you come up to the village, this is a Methodist Chapel built in 1911 and used by all the site's occupants. The third stop could be the ash tree that is to your left past the memorial, which is a prime focal point of the camp. This tree is in photographs from the start of the site's development in the early 1900s, and gives a good perspective of the structure of the landscape and the huts which once stood there. 

Finally, if you carry on past the tree, you come to a fork in the road, and to the right ahead of you, there is a firing range and a field which has trenches in it. This stop will highlight the training and 'handicrafts' that the soldiers had to master in order to survive and be prepared for the life of trench warfare and 'going over the top'. Depending on the different aspects of each stop, the audio will differ, experimenting with ways to make the audience consider possibilities associated with the site's usage and importance.

Myself interviewing Dr Jonathan Finch
Credit to Alice Toso

I went through the app's format quite a few times during the day, to make sure my audio will be descriptive and simple enough for listeners to follow. The module leader for the Excavation Fieldschool at Breary Banks is Dr Jonathan Finch, and I took him through the structure of the app last week and interviewed him as if he was a participant of the app guide. I asked him to describe what he sees from each stop, to divulge historical content that would aid me in my audio and to respond to any unanswered questions I had. This interview proved vital, in order for me to feel confident enough to produce an app that would do justice to the full potential of the wider landscape.