Tag Archives: technical library

Information Architecture and Digital Libraries (Part 4)

Posted on by acrystelle
Reply

The Information Architecture and Digital Libraries series is now up to Part 4. The previous three posts have discussed: -

  1. The (potential) role of information architecture principles and practices for digital libraries;
  2. Understanding the information environment as a key enabler of information architecture implementation, and
  3. Defining findability, its role in information architecture and practices involved in making content ‘findable’.

Discussion of key concepts and principles continue to be situated within an information setting involving an engineering technical library at an airline using a company intranet to deliver an online information service.

In this post, the concept of ‘usability’ is defined and separated from the concept of ‘findability’.

On a side note, let’s break up the term ‘usability’, it can have more than one meaning for digital libraries. Okay, so ‘usability’ would mean ‘able to be used’. But what is ‘able to be used’ for a digital library? The content? User interface? I would argue that it would mean both. A digital library needs to consider the format of the content being made available online (or on an intranet), as well as interface used to retrieve from the library collection.

Most of the information architecture literature concerning usability is focused on a website’s (or intranet) ability to be used. Little discussion is evident regarding the concept being applied to a digital library setting.

Usability is, of course, user-centric, and like ‘findability’ requires a comprehensive understanding of the information environment. For the most part, this will include the context and users – their information seeking behaviour, experience with using the intranet, tasks required to be completed with the information, and preferences (and operational requirements) for ways in which to search and retrieve information. Usability of an information architecture, or digital library is then defined by the user/s, and each situation will be different to the next.

According to Jeffcoat, King and Jannik (2005), usability is a “measure of success a user achieves when utilising a product or system” (p. 236). Usability is not an absolute concept, and may also be defined by the extent to which a website (or intranet) is 1) easy to learn; 2) efficient to use; 3) memorable; 4) error (in)frequent, and 5) achieves satisfaction of the user (Jeffcoat King & Jannik, 2005, p. 236). What is not discussed is defining a measure for ‘easy’. What is ‘easy’? What makes an architecture ‘efficient’? And how is satisfaction achieved amongst the system’s users? Answers to these questions are, and will be, subjective.

The concept of usability is often discussed interchangeably with findability. A separation between the two terms is required to understand the role of each in information architecture practice and implementation. Design of an information architecture, its structure, organisation of content and navigation facility, comes from effective content collection development and management. That is, the content of the digital library collection is relevant, accurate and applicable to the airline’s information environment and aircraft fleet, as well as each technical document’s description is complete and recorded in a consistent manner. It becomes clear, as shown in the diagram below, that usability is not only dependent on the findability of content, but is also defined by how the content metadata is used to develop a usable interface from which to search and retrieve technical data and documentation from the digital library’s intranet site.

Distinguishing the concept of usability from findability….

Focus: efficient, ease to use search and retrieval.

Orientataion: experience and user.

Achieved by: building on the established and maintained findability of library content, organising content and designing navigation in a way which effectively responds to user information seeking behaviour and operational requirements for task completion.

Jeffcoat King, H. & Jannik, Catherine. M. (2005). Redesigning for usability: Information architecture and usability testing for Georgia Tech Library’s website. OCLC Systems & Services, 21(3), 235-243.

An Alternative Flight Path – An (upcoming) Conference Presentation

Posted on by acrystelle
Reply

I have a paper to write and present for a half-day conference happening in Brisbane next month – ALIA People Power. One of the themes is ‘out of the ordinary’ library roles. Well, mine is exactly that. I’ve been asked from time to time, mostly at networking events, what a librarian can do in aviation. I like talking about my job, so the conference is a perfect opportunity to share what I do in my role in aviation, in engineering and maintenance for an airline.

The Australian aviation industry’s governing body, the Civil Aviation and Safety Authority (CASA), impose a responsibility on airlines to effectively maintain and provide access to approved technical data (and publications) for continued airworthiness. The engineering technical library contributes to the airline’s compliance in holding an Air Operator’s Certificate (AOC).

In my paper (and presentation), I will be introducing delegates to the unique information environment – regulations, information needs and operational requirements, and the type of content held in the library collection. I will discuss the importance of accuracy, currency and control of publications, as well as describe my role and outline library processes.

I aim to share an insight into an industry I’ve become addicted to. Aviation is an ever-changing and very exciting industry to be involved in. Every day I see airplanes take off and land. Airplanes are remarkable pieces of engineering. I have a much deeper appreciation for them, and the work that goes into designing and maintaining them, than ever before.

Library and information professionals should not shy away from these out of the ordinary roles, but be enthusiastic about broadening experiences and applying expertise beyond traditional library walls.

‘Work’ on the Mind

Posted on by acrystelle
1

For today’s #blogjune post I had plans to write something meaningful, something compelling and with more purpose than what I’m about to write. Instead, all I can think about is work and my day. I’ve only just arrived home, so I guess I haven’t had a chance to wind down yet. But I do have another writing piece to complete tonight…..I shall reflect on my day.

Over the last week I’ve arrived home later than usual. I don’t have to rush home to complete study, now it’s the mid-year break. I’m taking my time throughout my days at work, allowing myself to go out for lunch, stay a little longer to finish tasks and to catch up with my supervisor or colleagues. I haven’t minded at all, actually as I enjoy my job and the place I work.

Today I started training an addition to the engineering technical library. I haven’t trained someone in about three years, so I’m a little rusty with instructions, explaining processes and perhaps minus some much needed patience. Training is exhausting! I’m always thirsty because I’m talking all the time and I have a person constantly ‘hanging’ off me, awaiting the next task or process to be shown. My project work has been shot for another week. I’m only three weeks behind my project schedule (sarcasm). Actually those three weeks worth of project work is crucial to the entire project, so I’m a bit disappointed I don’t have a chance to work on it probably for the next two weeks. I find I need to keep reminding myself that with this person trained up in the ‘everyday’ processes of the library, I can return to paying full attention to my project work and continuous improvement. I’m lucky I already know the new addition. We’re able to have a chat and laugh every so often to break it up.

I went through the two biggest and most important processes for the technical library – incoming and outgoing technical documentation. I wanted to explain these processes in their simplest form, get the basics down pat. I had planned to provide more background information about the role of the central, document control system, but I didn’t get very far before I was side-tracked. Perhaps I should have this person processing and worry about knowledge later. Though I still maintain that it is important to understand the role of each process and the purpose of the system as they contribute to the ‘big picture’.

Lunch went for two hours today. Two hours! I haven’t had that long a lunch since my PR days. The Airbus rep who resides in the hangar took a group of us out. From the team I work with, there was Miss Sheep, The Boss, Maverick and Miss Gravy&Chips. Not so great food, but great company. It appeared the group wasn’t too anxious to return to the office. Hey, that’s just how we roll. ;) But I think this also had something to do with “The Boss” being in attendance. Next time we’ll need to go out for dinner so we can have a drink or two.

Okay, I think I’ve written out my thoughts on the day. A fabulous process for winding down, I’ll say. I could probably move on to my next writing piece now….

Information Architecture and Digital Libraries (Part 1)

Posted on by acrystelle
2

For my last assignment for the semester, I had chosen to look at information architecture for digital libraries. I suggested a framework, defining each element’s role, relationships between them and arranging them in a way that constitutes a “big picture” of information architecture principles and practice.

In a series of posts, I will share my views of information architecture key concepts and principles. I certainly don’t have all the answers (though I make every effort to try!), but the framework I suggest is an attempt to explain each concept as they contribute to the final outcome and ‘state’ of information architecture design.

Information architecture practice is relevant to a digital library as they share a common goal – both are concerned with achieving findability (Batley, 2007, p. 3). Concepts and principles of information architecture need a slightly different approach in their application, primarily because digital libraries not only have a user interface, but also have a collection (of mostly external content) to effectively manage, organise and structure in a way that makes findability efficient for the library user. An example is the engineering technical library I work in. Content is not generated internally, it is gathered from many vendors, all with various ways to describe and label technical data and documentation.

The role of information architecture is to enable access to content with a systematic approach to interface design, organised and structured in a way which facilitates the user’s quest for required technical data or documentation (Toms, 2002, p. 855). Designing functionality, enabling access, starts with identifying and understanding information needs from both the user and organisational perspectives. In the case of my engineering technical library, practices and processes also need to satisfy industry regulations which govern the use, collection, management and access to technical data and documentation, and meet operational requirements which dictate how technical data and documentation needs to be accessed.

Given the scope of information architecture being applicable to “shared environments”, the practice may therefore lend itself to designing a digital space which delivers an information service, such as a digital library via a company intranet. Intranet users are highly critical of poor usability (White, 2002, p. 47). Integration of information architecture practice into the effective management of a digital library (achieve findability and usability) can only mean benefits in the form of increased productivity. The effects may not be realised directly, but if I can design the technical library’s intranet site in a way that improves usability and decreases the time it takes for library users to search and retrieve information, the ‘flow on’ effects can potentially be seen in other operations and objectives, such as ‘on time performance’. The goal of the technical library is to provide effective access to the library collection, through an intranet, providing a user experience which enables efficient search, navigation and retrieval of information. Information architecture practice can certainly assist with achieving this goal.

 

Batley, S. (2007). The I in information architecture: the challenge of content management. Aslib Proceedings: New Information Perspectives, 59(2), 139-151.

Toms, Elaine. G. (2002). Information interaction: Providing a framework for information architecture. Journal of the American Society for Information Science and Technology, 53(10), 855-862.

White, M. (2002). Information architecture and usability. EContent, 25(4), 46-47.

A Day in the Life of a Technical Librarian

Posted on by acrystelle
Reply

I’m still finishing off my last assignment for the semester, so what little inspiration I have for today’s post (given that I’m so incredibly tired), I’ll draw from my work day as a Technical Librarian at an airline.

7.30am – arrive at work, check Twitter and log onto my computer.

7.40am – start processing Technical Library email inbox – new service documentation and manual revisions to be entered into system and assigned to engineers for assessment; manual/document requests; responses from vendors, and any other notification relating to technical publications or access to websites.

8.00am – log into my Google Reader and briefly check out what is there to read throughout the day. Check Twitter.

8.40am – Goose gets in, says ‘G’day’

8.45am – pop in to see the ‘Dad’ (I didn’t get to this morning, but usually we’ll have a 15-20 minute chat about work and other things)

9.00am – Check Twitter (and continue to check Twitter nearly every hour throughout the day). Goose and I head to the lunch room to grab a tea/coffee.

9.15am – say ‘good morning’ to rest of the team, a bit of banter, a few stories.

9.30am – 11.30am – continue processing email inbox and follow up on a few loose ends between working on a project task. I try to answer and resolve as many issues as possible (from internal or external to the company) by before or just after lunch.

11.45pm (ish?) – an engineer visits the library and shares his latest news of a training course, learning about new aircraft. I am surprisingly fascinated by how fuel systems on an aircraft work.

12.15pm – 1.00pm – (today) catch up chat with supervisor

1.00pm – lunch (finally!)

1.15pm – worked out a plan for tasks to be completed in the afternoon, follow up this and that; checked project status and planned next steps.

1.25pm (approx) – continued working on CMS project.

2.00pm – Goose and I head to the lunch room for afternoon tea/coffee

2.15pm – begin looking over my assignment draft (I usually don’t do uni work at work, but since it was a quiet day…..)

2.30pm – chocolate

3.00pm – headed out of the office, picked up my new glasses on the way home.

4.30pm – started working on my assignment again.

6.15pm – picked up partner from work.

And….now I continue to work on my assignment and hopefully have it reasonably finalised before a final edit at work tomorrow.

It’s been a quiet one at work today. The only major issue I had to follow up was some manuals which were discovered to be out of date. I had contacted the vendor earlier in the week. Only after I followed up my request for current revisions, sending an email to all my contacts for the vendor, did someone respond. I’m hoping the manuals will be sitting in the library inbox tomorrow morning. A maintenance provider need the manuals to carry out maintenance on parts the manuals relate to.

The collection of manuals held by the technical library are subject to regular audits, in order to maintain currency and accuracy. Notifications of new revisions to documents and manuals are usually received by the technical library from the vendors.

So not a particularly inspiring post and I apologise for the somewhat boring day I had. However I am grateful for the quiet day as lately it’s been my “rest” and a bit of social time before hitting the study at home to do assignment work.

 

Nearly there…..