Showing posts with label ideation. Show all posts
Showing posts with label ideation. Show all posts

Saturday, 10 October 2015

Week 10: Modules

This was a little more of the same.  Once I got the api/images/angular working for the sport category I then repeated the process for all the other categories, checking nothing broke as I copy-and-pasted code.  

I also started into php for the first time for this project.  Lyndon had created log-in and sign-up pages in php and I edited them and styled them to look like the rest of our site.

The other large change was to simplify the html content that users edit and validate.  Some of the feedback we had was that the errors panel was too complicated and the easy level wasn't that easy.  To counteract how complicated it is, we decided to break down each website into smaller modules.  I took our cricket website (which we seem to use as our test case for everything) and broke it down into 8 different modules.  I tried to pick obvious break points in the module and had to edit the code a little to make sure all tags in each module had both opened and closed.

By changing the website into modules, we also had to change the easy/hard approach.  Instead of each website having easy or hard mode, now, depending on how modular each website is, it is now easy OR hard.  And we added more instructions to the website hover, 'begin restorations'.

Sunday, 6 September 2015

Week 6: Experiences in the Poster & Pitch

Concept, project and design process  

Documentation

Writing up part A document was fairly similar to project documentation I have written for projects at work.  While it seems like a lot of writing and a lot of work, it is an important skill with workplace application.  It is also important because it clarifies a lot of the detail of our project and outlines our plan for how we will turn our concept into an application.

Design thinking

Design thinking last semester taught us a lot of different processes and design techniques.  They were all clearly prescribed and written into our assessment criteria.  The criteria for this project doesn't have the same level of detail and I found myself thinking back to those pieces of assessment as a guideline.  I imagine my design thinking toolbox will get easier to remember the more I use it.

The brief

Student briefs are generally comprised of two elements, the 'client' needs and the assessment needs. One of the problems we have already come across (as detailed in a previous post) is which APIs we will need to use to complete the project.  The 'client' needs is to highlight an area of Trove, the assessment needs is to learn how to use API calls (in particular the Trove API).  It was good to find out that there was a little room to move so that the 'client' need still came first.

Feedback

I did a quick write-up of the feedback we received from our Part A presentation on our team blog. We also went over the feedback in more detail in our Part A document.  The piece of feedback that stood out most to me was around help.  Our intention for our concept was never to provide training but for it to be a tool students could use to practice html skills and in the process learn about web standards and practice validation.  It hadn't occurred to me to provide help information or how our users would go about getting help if they were stuck.  There were many suggestions from class including a discussion board, chat or links.

I recently did the AngularJS track in Codeacademy and really liked the way they did help.  One problem with chat (and other types of help) is that it requires staffing or moderation.  The way codeacademy approach is to leverage existing methods of getting code help and incorporating it in context (i.e. where the student needs it). Here are some screen shots.







Even though they use other services to provide the help, they still guide the user there with questions. This is a much better approach than just providing links or a discussion board.  While we can put together information on tags and tag depreciation to get users started, if they are looking for more in-depth help, Stack Overflow would be the best source for this.  The other benefit of this is familiarising users with standard help channels for code that they can use in future for other coding problems.


Other teams

Seeing other teams progress was good inspiration.  It was interesting to see how they had divided the team responsibilities and how technical their projects will be.  I know there will be quite a lot of learning ahead of me to be able to complete the project but I found it encouraging listening to other teams proposals and how they are approaching the different components.  The other concepts were also interesting to see, especially the shipwreck one (Atlantis).  Early Australian shipwrecks was the individual concept I presented and I'm really interested to see how another team will pursue and change the idea. Seeing it progress to a more complete interface from the wireframes I presented was great.

My process

Completing the part A presentation and documentation has reiterated to me the importance of planning in design thinking techniques to a project.  It would be easy to plan a project considering only the end product and the technical needs (i.e. how am I going to make this).  But it is important to plan in time for research, testing and feedback.  I know that there are a lot of design resources (like the d.school) but I also think it might be good for me to keep a record of the different techniques I've used to add to as I progress.

Thursday, 27 August 2015

Week 5: 6 thinking hats activity

For this week's contact session, we ran our concept through the six thinking hats.

From http://johnkapeleris.com/blog/?p=418

Concept:

This project, Web Historians, aims to highlight the importance of archived websites and their potential decay, by providing a solution through an interactive educational experience.  It will use a combination of Trove and Wayback Machine APIs to access archived websites that are then evaluated through a HTML5 validator.  Users will be able to choose websites in a category of interest to them, select a specific site to restore, fix the highlighted problems, and save the completed, restored files for the future. Users will also be able to save their progress by creating an account.

White hat

The information in our concept is the html of archived websites.  The html is validated and is presented to the user as html mark-up, a list of errors, and the displayed website.

Red hat

Our concept has feelings of nostalgia and a respect for history and its preservation.  

Yellow hat

Best case scenario, we complete the app with all the 'if there's time' features, the technical requirements are challenging and we learn a lot but is not beyond our skill level.  The product is useful for our target audience and provides users with a positive experience of html. 

Black hat

There are a lot of technical components and it will be hard to draw a line in the sand for what we deliver.  There are a lot of things I would like to do with the project (like use web components) but not necessary to the delivery of the project.  Worst case scenario is we don't get the minimum requirements over the line and spend too much time in getting individual elements right at the expense of the bigger picture

Green hat

The initial concept is a creative way of using archived content by turning it from something static to something interactive.

Blue hat

The concept seems like a great way to both save historical content and provide a learning tool for students.

Wednesday, 26 August 2015

Week 5: Trove API limitations

We met today (meeting minutes to follow) to refine our concept and discuss our research so far.

There is an initial problem that we are currently working through regarding the brief requirement of using the Trove API.  During our research we discovered that the trove API does not provide access to the websites listed on the trove website.  We can however, use the Wayback Time-machine API (that Trove refers to) to get this information.

A closer read of what the Trove API can and can't access says:
"Search Trove newspaper articles, lists and works. (Works are made up of “versions”. They can be books, images, maps, music, sound, video, archives, journal articles…) Archived websites, people and organisations have not been included at this point."

We also looked at the search function of the API, and the 'search all' does not include archived websites:
"Search across the records in Trove. The same records you search from the Trove homepage, excluding archived websites, people and organisations."

We are in the process of discussing solutions with our tutors and course coordinator and have contact Trove to see if there is any support or workarounds for accessing archived websites.

Our current suggested fix is to organise the websites accessed via categories (e.g. sport, arts, education, government...) and to illustrate the categories (background, button?) with trove images (related to the category but not the actual websites) which are pulled using the trove API.

We would still need to use the Wayback Time-machine API to get the website details to validate but at least we are not by passing Trove altogether.

One of the risks we discussed today was having to make design decisions based solely on checking off a box in the brief and not on what would make the best product that suits our user needs.  While for the most part these two considerations are not opposites and inform decisions in consort, we are hoping that this problem is not the case of the former.

The core part of the brief that we are answering is to:
"highlight, reveal, [or] focus the content available through Trove ... something that goes beyond the simple search paradigm that they currently have and that sheds light on rarely visited corners of Trove."

We believe our concept definitely does that.  Stay tuned for more concept updates.

UPDATE: The course coordinator emailed back straight away with an OK to go ahead with our proposed suggestions.  We also chatted more with our tutor at the workshop and with the course coordinator after Friday's lecture.

(Originally posted on our team blog: Restoring the web)

Saturday, 22 August 2015

Week 4: Forming Teams

After presenting our concepts, everyone voted on their top 3 preferences for concept/group.  During the following workshop session, we finalised our groups.  Even though my Shipwreck concept received enough votes, I chose to work on another concept:  Restoring the web.  I really liked the problem that it solved.  I will be going into more detail in the near future as our team refines the concept, but here is a brief overview:

Project Description

Restoring the Web is a web-based learning environment aimed at teaching high school students basic web design skills.


Saturday, 15 August 2015

Week 3: Concept Ideation

In our contact session this week, we each bought 5 concepts to discuss ahead of our concept presentation next week.  Before the session was rescheduled due to the public holiday, we thought we might not get a chance to get input from our classmates before the assessment was due.  So, in a small group, a few of us collaborated on a Google Doc with our 5 ideas to help garner feedback. 

Both approaches had their pros and cons.  The benefit of discussing ideas online was being able to take the time to absorb the idea and think about it and give feedback later.  I also got more detailed feedback through this process. The benefit of discussing in person was being able to have a conversation about the idea and have more "well what if I change this or do that" conversations.  The main downside I found from discussing in class was idea fatigue.  Two groups, five people, five ideas each equals listening to forty ideas and talking about my five ideas twice - that's a lot of information!  It may have worked better if we either had fewer ideas to present (e.g. 3) or one group to discuss with but was still a worthwhile exercise.

Here are my five ideas and the feedback I got both from our small group work and the in-class session.

Idea 1: Dear Diary


Choose a date to see letters, logs, newspaper articles and diary entries written on that day. 

"I wanted to come up with an idea that could use the old letters, but I can’t think of anything so far… I like this one though"

"Sounds really good. Maybe need a scope with the dates thought (lot of data)."

Group discussion two: liked this idea.

Idea 2: Shipwreck map


Interactive map marking shipwrecks around Australia.  When you click on a shipwreck, different data is presented.  Photos, drawings, news reports, ships logs, etc.

Group discussion one: favourite idea among group.

Idea 3: Online Quiz


Pick a category or a year and do the quiz online based on past quizzes from newspaper archives.  Maybe similar in style to Google Feud.

"I just tried the google feud quiz, it’s fun! I like this idea"

"It took me a good minute to understand the google feud haha.  I like the use of newspapers as there are the most widely available on Trove."

Idea 4: Archived Websites

http://trove.nla.gov.au/website has a number of archived websites
You could pick a year to see how different websites looked or be presented a particular page and have to guess the year.

"It could be really interesting for the MM student ( see the evolution of trends in website design)."

Group discussion two: liked this idea.

Idea 5: Historical Maps

Might have to be limited to a specific area (like Brisbane.  Overlay old maps over google maps to see how things were and how things have changed.  

Group discussion two: liked this idea.


Presentation of my ideas to first group to discuss

After all that I'm still not too sure which idea to pick to present.  A task for tomorrow :)

Sunday, 9 August 2015

Week 2 Contact: Looking at Trove

Contact session

During this week's contact session, we looked at Trove and the vast amount of data available on it.  It was hard to develop an educational or entertaining way of presenting information in Trove when there were so many options.  Looking at what was available on Trove was similar to going down the rabbit hole of Wikipedia links!

In small groups, we started brainstorming options and once we started, we were able to come up with a few ideas.


What's up next:

We are each going to come up with 5 individual ideas to bring back to class to discuss, refine and pick one for our first project assessment.