Journal Entry Week 6: Resource Description

Resource description is can be defined as the process of describing a resource or an item for easy access to the user. With this said the resource should be accurate and organized so that users can categorize resources between databases. Due to the fact that there is consistency in cataloguing, two standards of cataloguing have been introduced. These standards are known as the Resource Description and Access (RAD) and Anglo-American Cataloguing Rules (AACR). Both of these standards have their advantages and disadvantages.

In comparison, I feel as if the RDA is clearer and better. According to JSC Secretary (2009), RDA is a flexible framework for describing resources and is independent of encoding schemas. RDA is a newer standard and was developed for the online environment. According to Zabel & Miller (2011), RDA was designed for online environment, is more principles-based, and better accommodates formats other than print. AACR is a standard used that was designed before online environments. In our technologically advancing world, AACR would not be a suitable standard for an online environment. I found more difficulties in reading AACR due to the fact that I found some trouble in terms of understanding what all the abbreviations meant since some of them were in English and others were in Latin. Tillet (2011) states that despite being altered over the years, the lack of logical structure and individual rules make AACR2 an illogical choice for 21st century cataloguing. Nevertheless, RDA helps users navigate through library resources easier as it is more appropriate for the online environment.

References

JSC Secretary, (July, 2009). Joint Steering Committee for development of RDA. Retrieved on August, 9^th, 2013, from http://www.rda-jsc.org/rdaimpl.html

Zabel, D.& Miller, L. (2011). Resource description and access (RDA): An introduction for reference librarians. Reference and User Services Quarterly, 50(3), 216-222. Retrieved on August, 2^nd, 2013, from http://rusa.metapress.com/content/wrg1501514721g7n/

Journal Entry Week 4: Information Organisation on the web

Information Architecture can be explained as organizing information in a certain way to meet user needs. Ryan (2012) states that it defines your site’s goals, is the foundation for great web design, and establishes a clear and well-documented plan for what you are about to do. Information architecture is significant as it simplifies the process of users finding and/or retrieving information. So basically, information architecture is the organization of information to support findability, manageability, and usefulness from the infrastructural level to the user interface level (Downey & Banerjee).

In the “Do” activity for Week 4 it was required that we visit 3 local council websites and observe them closely. The website that belonged to the City of Perth council was the most user friendly in my opinion due to the fact that the interface was simplest and the designs used was the most attractive. It also had a search box to simplify the search process for the user without looking through the menus. Nevertheless my experience using this site was the most enjoyable. All the sites had elements that improved the user experience; elements such as methods to navigate and retrieve information.

Incorporate a search box for a local council website is appropriate because users for this site tend to be searching for information on the city and information about the city. Thus, using a search box was very suitable for this sort of website. This is an example of how taken information architecture into account can greatly improve the experience of the user.

References

Downey, L. & Banerjee, S. (2010). Building an information architecture checklist. Journal of Information Architecture, 2(2). Retrieved from  http://journalofia.org/volume2/issue2/03-downey/

Ryan, D. (2012). The Role and Importance of Information Architecture. Retrieved from http://www.verndale.com/Our-Thinking/The-Role-and-Importance-of-Information-Architecture.aspx

Journal Entry Week 2: The Information User

In this week two’s learning activities, we were required to watch a video and offer our thoughts about user experience. After watching the clip, I figured that it may be hard to grab the concept of an entity without getting the bigger picture. Therefore, when designs develop a database or an online information tool, they should assess everything before designing and implementing their design. According to Weedman (2008) design requires and deep knowledge of who is using the system and what their needs and abilities are. Designers must know their users, their needs and evaluate how to simplify how the user satisfies their need.

Part of this week’s activity was to observe an individual using an information system.  Katz-Haas (1998) has stated that user-centred design is "a philosophy that places the person (as opposed to the 'thing') at the center". With this said, I observed a friend of mine while they used Google to search locations on where to organize his upcoming birthday celebration. He typed in the keywords “book location for birthday party in Brisbane”. The first website he clicked revealed a large amount of venues in addition with their guest capacity and price ranges for bookings. Bell (2008), states that it is important to understand the needs and challenges of the user as a first step. Thinking of this statement, I observed my friend and realized that he wasn’t facing any challenges as of yet. He initially estimated the cost of how much it will be in order to book a location without pursuing the subject for any longer.

I didn’t offer the user much aid due to the fact that he was only conducting a quick search and only wanted a rough idea about planning his event. In my database, I will research the elements required for a good user experience. Due to the fact that I prefer the technicalities involved with user experience I may use Garrett’s model for elements as a guidance to formulate my evaluation.

Bell, S. (2008) Design thinking. Retrieved from CMD on 28th August http://stevenbell.info/pdfs/ALdesignarticle.pdf

Katz-Haas, R. (1998). Ten Guidelines for User-Centered Web Design Usability Interface, Vol 5, No. 1, July.

Weedman, J. (2008). Information retrieval: Designing, querying and evaluating information systems.  In Haycock, K. & Sheldon, B.E. (eds). The portable MLIS: insights from the experts. Westport, Con. Libraries Unlimited.