Monday, May 6, 2013
Wrapping Up the Semester
It seems that every semester when I get to this point, I am shocked at how fast the semester has gone. With the amount of work that I've put into my classes--especially my internship--as well as the extra stuff that I volunteer for, it seems doubly true. At the time of this writing, I have completed 127.5 out of 135 internship hours. I have 7.5 hours left to do, 6 of which will be done when I am on-site this week. I have completed 7 substantial projects, worked on 2 ongoing projects that I will likely continue to do as a volunteer, and performed multiple other tasks. I have a solid working knowledge of Drupal, and between my internship and my Drupal class I am confident that I will be able to perform as a Drupal site administrator for any library that hires me in the future. I would note this semester down as a big success, even considering that I had almost too much work to handle.
After this week, I hope things calm down for awhile. I will still be volunteering with MCFL, but only 8-10 hours a month. The rest of May and June will be time for me to relax and recharge for my final semester taking content classes (my last semester will be devoted to assembling and presenting my e-portfolio). My mom and I took a look at the schedule for my graduation ceremony next May and have already started making plans. I know I have some important graduate deadlines to meet this next year (mainly forms that I must submit to be eligible for graduation).
It's the final leg of my journey that I started three years ago, right here on this blog. It's a very odd feeling because until now it didn't feel like my program would ever come to an end. Well, it is. And I can see it, now.
Monday, April 22, 2013
Can I buy some time from you?
I wish I could buy some time. Or even barter for it. Anyone have any time they would like to get rid of? Do you have an hour you could loan me? It might be very tired when I return it to you, but I would appreciate it greatly! I could pay you in homemade baked goods. *sigh* If only. Is it bad that I'm counting down the days until all my school work is turned in? Hope not--it's helping to keep me sane during the final crunch!
My workload (at work and school) is set to increase exponentially over the next few weeks until all my school work is completed and submitted on May 10th. Part of this increase is self-imposed--I'm going out of town soon for a few days, and so work and school will be put on hold during this time. I'm working to manage my time and tasks wisely before and after my trip so that all work-related and school-related things are done on time. My trip could have had better timing, but it was planned around a set event (which I will probably post about with pictures upon my return), so there wasn't a whole lot of flexibility on when I could go. At work, some of my periodic duties seem to be occurring all at once, which is resulting in a higher-than-normal workload even without the consideration of my time off. So yeah, timing is not great. To make sure everything gets done when it should, my poor little check list feature on Outlook is working overtime to keep me organized. When time becomes a hot commodity, it's important to use all the tools at your disposal.
It will be particularly difficult to get internship work done when out of town. So, to account for this, I've been working a bit extra over the last couple of weeks. Between my extra hours and the last on-site day (scheduled for next month), I should be able to keep on task with hours and work even if I'm not able to spend any time on my laptop while I'm gone. Planning ahead is really going to let me enjoy myself without worrying about what still needs to be done.
And through all the chaos, the same mantra keeps repeating itself in my head: one more year, one more year, one more year...
Friday, April 19, 2013
Vocabulary Adventures Part 2 and Other Things Filling My Time
My other project-in-progress, the controlled vocabulary that I created, is now moving forward again. I had submitted the controlled vocabulary for review, went over everything with my site supervisor during my last on-site day and submitted a final draft; now I am able to take the next step of the process. Using the controlled vocabulary, I have to create a taxonomy on Drupal (this step has actually already been completed at the time this blog was written). The taxonomy is used to automatically generate a selection menu which users (the MCFL staff) can choose from as part of content classification. It will now be available to assign to new content. I also need this selection menu so that the controlled vocabulary can be assigned to forms, policies, and procedures already up on the site. The interface on Drupal for starting this process was very easy to understand and navigate for me since I'm already moderately familiar with Drupal (and becoming more so all the time). I was able to create and define my taxonomy in about an hour, maybe a little less. The next part of the process--assigning controlled vocabulary terms to existing content--is going to be much more time-consuming since I have to edit each content item individually. And I need to compare existing tags with the controlled vocabulary to make sure all relevant topics are being correctly assigned. Almost two hours of work didn't get me through all the forms yet, so I know I have a number of hours still ahead of me on this.
Lastly, I turned in a guide for library staff for adding content to the Resources by Subject pages on the library's public site. You can actually see this area here (scroll down to the Resources by Subject block). The guide explains how to add and edit the four types of content that can appear on the subject pages. See if you can find all four types! Only three weeks left of internship work, and it feels like I have enough to do now to fill those three weeks! And I still have my last on-site day to look forward to.
With my going on and on about my internship, you would think that I haven't had any other fun. Not true. With the warmer weather and Spring now holding fast, I ended up adding yet another planter to the collection slowly growing (forgive the pun) outside my front door. When Scooter and I had that garden project two years ago behind the apartment building where we live, we planted a small collection of herbs--which, two years later, are still growing strong. But we had no basil or thyme--both herbs that my Italian cooking must have! So, Scooter got my new planter situated and hanging off the rail (I've run out of ground space and have to build up), and I found two lovely specimens--one of basil, one of lemon thyme--that went into the planter. My fresh herb stock is now complete. Well, except for maybe Italian parsley. That would be nice to have growing on my porch too. I miss having a large garden full of growing things, but time is a precious commodity that I never seem to have enough of. Once I finish my MLIS, I keep telling myself, once school is done I will have the time for gardening and more cooking and more traveling.
Ah, well. On to more schoolwork!
![]() |
| Basil and thyme are great planter partners! |
Friday, April 12, 2013
Guides, Guides, and More Guides
Again this week I've been working on guides for the staff, two in particular. The Drupal guide I'm working on is a document that predates my time with MCFL, but it is desperate need of updating and the addition of a LOT of missing information. I'm fairly certain that the guide contains everything that was needed at the time it was made, but the library's website has grown and evolved since it was first debuted with the new look, which resulted in a lot of areas being created after this guide must have been put together. So my job is to update what's already in the guide, and add in the information that may be missing based on what options/settings/features/etc. are now available. Not an easy job. The guide is quite extensive; right now, it's a Word document that's over 75 pages in length, and there are still a lot of components missing from it that I have yet to add in. Before even adding in the new information, I had to comb through what was there to make sure instructions were current and links were still correct. I actually had to go back and change a lot of the URL pathways for links because they had changed. Drupal 6 (which is what the MCFL site runs on) has made way for Drupal 7 since the site first went live, and soon Drupal 8 will be released; as a result, Drupal 6 information has moved from its original location and I had to track it down again. Right now, all the information in the document is current; I'm now slowly adding in all the missing information, which takes awhile because I have to include how-to instructions for each process that needs to be added. This is a project that is spanning weeks.
My second project is creating another guide for MCFL staff that guides them through adding content to a specific area of the library's public site (my two previous guides had dealt solely with content procedures for the staff intranet). However, this guide is a little more complex that the first two because there are several types of content that can be added to this area, and each type follows a different process. One process is already partially outlined in another guide, so I merely needed to reference that guide then add the rest of the information. My biggest worry about this guide is that it will be too long. The Drupal guide, monster that it is, is only intended for the staff that works with administering the public site (aka the Webmasters Team); this second guide is intended for all library staff. I know people don't want to read a novel when a few pages would do. I'm alleviating part of my worry by including bookmarks in this guide; staff will be able to go directly to the area that they want for the content type they are trying to add and skip over the rest of the guide that they don't need.
This work will definitely carry over to next week, and possibly later than that. Back to writing!
Sunday, April 7, 2013
Making Lemonade
When life gives you lemons, make lemonade. Well, I had to make lots of lemonade this week. Scooter's car got broken into, and although we were extremely lucky because the car was still there and nothing in it was taken (even though Scooter had cash and tools in the backseat), there was still damage done that we're now having to deal with. Another small blessing is that our insurance has been very helpful and responded quickly.
Then late in the week, I broke my website I had been using for class assignments in my Drupal class. Yes, broke. It was due to two modules (packets of code installed on the Drupal software) being incompatible with each other. The result? My entire website being replaced with a blank page and one line of text describing an error (and not the usual web errors). Of course I panicked, and when my efforts to restore things didn't work I was literally in tears. All my work for the past 10 weeks...gone. Then I remembered when we had to create backup sites earlier in the semester; my backup site was also displaying the same error, but I realized the content had to still be on the server. Checking my server files proved me right. Thank heavens. It took another three hours to fix the problem, but eventually I got my site working again.
So between Scooter's car and my website, things were chaotic this week, and my internship hours and Drupal assignments for the week suffered a major setback. It's a good thing that my instructor and my site supervisor know that life sometimes happens. It's a reality that I think everyone who works with adult students must acknowledge. I have to be aware of it myself, as I work with adult students at my job too. My instructor gave me a few extra days to complete my Drupal work for the week (and I actually got the extension before my site broke--I call that good timing). My site supervisor told me not to worry, that I'm doing excellent work, and that I shouldn't let the internship be cause of needless stress.
Things turned out okay, and even though we're still dealing with the aftermath of Scooter's car, life has calmed down a bit. The lemonade isn't outstanding, but it's at least a little sweet.
Friday, March 29, 2013
On-Site Day #2
One of the goals for me this visit was to meet and do some collaboration with a member of the Technical Services department that I hadn't yet met, but who is highly involved in the management of the Drupal library and staff sites. Unfortunately, she was out because of illness, so my collaboration with her was deferred to a future date (probably via WebEx or some other teleconferencing medium). It is her input that I will need to finalize the design for the Online Book Clubs page I created. Another smaller goal was to review and finalize the controlled vocabulary that I had drafted and submitted early this week. My site supervisor and I sat down and looked over the terminology together, and the feedback I got was overall positive--there were only a few changes that needed to be made. The list has been updated to reflect those changes and the finalized list submitted for approval by the library's Leadership Team. Once their approval has been given, I will be able to create a new taxonomy on the staff intranet with the controlled vocabulary that will be used for forms, procedures, and policies. It will also mean that I will need to update the vocabulary for all those that already exist. But I'm glad to see concrete results from this part of my work so soon.
A major goal that I was able to accomplish during my on-site day was being able to sit in and participate during the Webmasters Team meeting (of which four people were out due to vacation, personal illness or a child being ill). My site supervisor is the chair of the committee, and so my attendance was easily arranged. I appreciated being able to see how a committee addresses issues and see the practical topics that this particular committee is in charge of. We discussed the library's social media; several library-wide (as opposed to branch-specific) web-related issues, including a new site vendor; and the staff survey that I had put together. I was able to provide some feedback and suggestions for the social media topic; I was actually at a social media panel at November's CLA conference, and so remembered a few ideas that were mentioned there--and I did come up with one or two ideas of my own that seemed to be received well. However, my time in the spotlight was really during the discussion of the staff survey. I explained the research process and how I created the survey, as well as the logic behind several of the questions. There were some changes that the members of the committee suggested, but overall the committee was pleased and felt that the questions will be able to tell them about how the staff uses the intranet and what staff would like added to the intranet. So all the hours I put into this project really paid off. I've already made the requested changes, and now that too will head to the Leadership Team for final approval before going live.
During my lunch break (when I was introduced to a really good restaurant that I want to go back to), I got to speak with another person (the cataloger I first met on my last on-site visit) in the Technical Services department at great length. From her, I learned a bit more about cataloging and records--the kind of stuff that was not really addressed in my cataloging class. Then again, the issues she mentioned may not be universal to all libraries but may be a specific issue with this particular library system. I was able to share with her some of my own library experiences, and she very kindly offered her advice whenever I get stuck with cataloging/classifying materials for the collection of the library where I work. She's a very sharp lady and I'm glad I was able to connect with her. Hopefully I will be able to see her and talk more "shop" on my last on-site day in May.
So all in all, a productive site visit despite not going quite the way my site supervisor planned. I also talked with my site supervisor about continuing my work as a volunteer after my internship is over. I would like to see some of the projects I am involved in through to the end, but for the sake of my sanity my hours would need to be drastically reduced (I'm thinking like 10 hours/month). We shall see if things will work out as I hope.
Friday, March 22, 2013
Self-Motivation
As part of my internship class, I also have to interact with fellow virtual interns through the program's Learning Management System (LMS) and complete some work to turn in. This is how the professor who runs the virtual internship program on the school's side can view our progress, know what we've done, and see that we're "on track." It's an accountability thing and provides evidence to show we've earned the units we signed up for. Every week, we go over another topic related to virtual working environments and/or internships. Some of our topics so far have included time management, communication, and networking. For each topic, my professor points us to a number of sources, many of which I have found interesting or enlightening. We are also asked for a response that we post on the class discussion forums for the week--which is valuable because I have the opportunity to learn from my peers and they from me.
This week's topic is self-motivation, a trait that I think I'm rather strong in. It would seem logical for those who pursue an online program of study and succeed in such a learning environment to have strong self-motivation in order to stay on task. I can imagine the struggle that not having this skill could result in. As a virtual intern, I think self-motivation is a requirement for the work environment. You need to be able to stay on task, actually get going (and keep going), and regulate your own work without someone looking over your shoulder to make sure you're doing what you should. It's a big responsibility. No one's watching you to see what you get done and when--all they have to judge your performance is your results, so you need to produce them. This is one skill that definitely carries over into telecommuting too; when you're working from home, you also need to be able to stay on task without physical supervision.
One of the resources included with this week's unit was a self-motivation quiz. You can find it here: http://www.mindtools.com/pages/article/newLDR_57.htm. I have no way to determine how accurate it is, but I think that it's at least a reasonable indicator of one's aptitude. My score was a 49. The other interns that have posted their scores in the discussion note that their scores seem to follow their own self-assessment of their motivation. Feel free to try it and post your score (if you like) in the comments section.
Wednesday, March 20, 2013
Internship Update and Scholarships
I've also been applying to scholarships, some offered by the school I attend and some offered by my program's department. I know a thing or two about scholarships because I collect and distribute scholarship information in the library where I work and the campus it's located on. I haven't really applied for many scholarships until now because my employer offers a tuition reimbursement program that I've been taking advantage of in conjunction with student loans. However, I will only be taking one class (three units) during my last semester, which will not qualify me for financial aid. For those who are not aware, you must be attending school at least half-time (6 semester units for undergraduates, 4 semester units for graduates) in order to receive federal student aid. Without the student loans, I will have to pay for my last semester out-of-pocket until I get the tuition costs reimbursed after the semester is over. Financial aid is not a glamorous issue, but it sure can have big effects on one's ability to attend school. By the time all my applications are in, I will have applied for over fifteen scholarships. I'm keeping my fingers crossed that I will get something.
This weekend, I will be celebrating Swedish Easter with my family. I'll do my best to remember to take pictures so I can post about all the good food!
Thursday, March 14, 2013
Know Your Vocabulary
Controlled vocabulary is not a new concept for me. In fact, it was one I came to know and love during my second semester when I was taking a class on databases (one of the core classes for the program). Controlled vocabulary can be seen as metadata--data (information) about data--that can have a number of uses in a practical sense, particularly as an aid for creating more successful searches. The reason why it's "controlled" vocabulary is because it's a set of predefined terms that are adopted as the "correct" entries for the type of information considered. I know that may not make much sense, so here is an example. Think of a field where you are asked to enter a date. There are quite a lot of ways that you can do that: 2013-03-14; March 14, 2013; Mar 14, 2013; 3-14-13; 3-14-2013; 2013, March 14; and so on. All of them are correct, but perhaps the system reading the information can only understand one type of entry. The field may have a line of text under it, something along the lines of "Enter date as MM-DD-YYYY" so you know the required method of entry. A controlled vocabulary works in a similar way; there is a predetermined "right" way of stating a term or phrase, and you must use the controlled vocabulary when working within its perimeters.
Librarians, especially those who do cataloging, are very familiar with the Library of Congress Subject Headings (LCSH), a type of controlled vocabulary used to enter the subjects a library item is related to or addresses in its contents. The LCSH is quite extensive and covers every subject you can think of. If you want to see examples of these subject headings, go to your library's website and do a search of your choice. Click on one of the books in the results to look at its details, and you'll see entries for the item's "Subject." Tamora Pierce's book Mastiff shows subject entries for "Kings and rulers -- Juvenile fiction," "Police -- Fiction," and "Fantasy," among others. Each of these terms could be rewritten in different ways with different words and still get the same or similar meaning. Having a standard set of terms--a controlled vocabulary--means that the terms can also become useful for searching, since all items on the same subject have the same subject entry and can be found in one search. You don't have to worry about different people using different terminology because catalogers use the same subject heading rules.
Okay, I went off on a tangent a bit there. Back to my project. I had to approach it a bit differently than the projects I did in my database class and my cataloging class that used the idea of controlled vocabulary. On those, I was starting from scratch and coming up with controlled vocabulary terms with a blank slate (although in the cataloging class, I did have to use the LCSH rules). With this project, there are terms already entered for each item on the two pages I'm updating. Terms with no sense of organization or logic. So I first went through and recorded all the terms and the frequency of their use. Then I organized them into sub-classes based on general topic that they relate to (I'm still working on this piece of it). My next step will be to see if there are terms that can be combined into more general terms. The trick with controlled vocabulary is to get just specific enough--not too broad, and not too focused, but just right. One must be Goldilocks, except with words rather than porridge and beds. Lastly, I will designate terms/phrases for each of the old ones (or simply note them as needing to be deleted). This will be my controlled vocabulary.
I will have to post another recipe tomorrow. I made a quick and easy dinner last night and it was good--something I haven't had since my grandmother was alive. Stay tuned...
Wednesday, March 6, 2013
Surveys
The goal of the survey I need to create is to determine what aspects of the staff site are favored and which aren't, and discover what features (if any) the staff would like to include on their site. Because of the problems that arise from too many open-ended questions (mainly problems understanding what respondents are trying to say), I've been given a limitation of only using multiple-choice questions with one open-ended question at the end. Certainly not an easy task, since I'm not in the staff's heads and can't divine what questions to ask to get the desired feedback (though wouldn't that be a useful talent to have?).
So my plan of attack has been to start with research--researching staff sites, commonly liked features, site best practices, etc. I do have a survey that was done to gather feedback for the public site that I can use as a template and a spring board for creating questions. To keep track of ideas that I or others think of, I've also created a spreadsheet of things to suggest adding to the site which will be posted for the rest of the webmasters team that works on the staff site to view and add to. It'll act as a record of ideas for site improvements that can be implemented over time (or tossed if the idea isn't a good fit for the site or the users).
About the research--there is an overwhelmingly large amount of information out there on intranets, intranet design, intranet features, and intranet best practices. I've spent about fours hours of my time this week just reading and learning about intranets, and I've barely conquered the tip of the iceberg. There are a lot of blogs out there, written by professionals and non-professional alike, about how to create a good intranet. One in particular, The Treehouse, had a series of four posts titled The Essential Intranet. Even though the MCFL's intranet already exists, there was still a lot of valuable information from Parts 1-3 that I was able to take away and use as I thought about this survey. I was also able to find pieces of wheat among the chaff in places like forums and company websites that were trying to sell a product (but happened to also include articles about various aspects of intranets). As I was looking for information on intranet features (to see if some could be included in the survey to gauge interest), I found a free short e-book titled 101 Intranet Ideas. Not only that, but I was also able to get some information about a study called the Social Intranet Study done in 2011 that looked at many aspect of intranets and the companies that have and use them. And all this wasn't even a fifth of what I read through (which isn't even a thousandth of what's out there). Needless to say, you can definitely find a lot of literature on the subject.
So there was a lot to absorb and mull over. And since I had never created a survey before, I also looked at some sources that provided survey creation help, and found a couple that were specifically for intranet surveys. I even found an unlikely source in HowTo.gov on their page titled Basics of Survey and Question Design. It provided a lot of survey "basics," and I definitely used the information there while I was trying to create survey questions on Survey Monkey (the survey creator used by the MCFL). I'm fairly happy with what I've created so far--and I'm trying hard to stay away from any double-barreled questions, leading questions, questions with built-in assumptions, and questions that leave out a response choice (basically, all the pitfalls noted on the HowTo.gov page).
Hopefully, I'll get some feedback soon--with a survey like this, there's lots to learn!
Tuesday, February 26, 2013
Internship: First On-Site Day
Yesterday was my first of three (possibly four) days over the course of the semester that I will be on-site at the library where I have my internship. A lot of Marin County is beautiful, so my drive (at least when I got into Marin County) was scenic. I actually pass through the area when Scooter and I are heading to our favorite coastal town, so I was moderately familiar with where I was going. The Technical Services department for the library system is actually located on an old army base. The work area is in a remodeled hangar building, and I was able to appreciate the aesthetics of the building's structure. It was fairly obvious that many of the surrounding buildings had recently been remodeled or built from the ground up, and from the front door of the building you can see newer private homes. One of the neighboring old hangars was still under construction.
The Technical Services team encompasses a group of staff with multiple purposes and duties. There's the staff that's in charge of processing all items purchased by the library before sending it off to the branches for shelving. There's the staff in charge of ILL and Link+ (a program many SF Bay Area libraries are members of) requests. There's the cataloger--there was only one for the whole county library system! I know she must be a very busy lady. There's my site supervisor who oversees my internship and several other Webmasters Team staff, and of course the library IT staff who are often in and out of the office as they head out to branches with malfunctioning equipment. And there's the staff that works with the county library's subscription databases and library catalog data, one of whom I got to speak with for a few minutes. He was discussing some of the growing pains with adopting the Encore interface that they very recently started using, as well as the difficulties of trying to maintain the Encore-run catalog and the classic catalog. He noted that one of the (relatively) nice things about the classic catalog is that the files and data are maintained on a local server; when something goes wrong, they have direct access to the files and can work on fixing the problem. With Encore, as with any service maintained by a vendor, the data and files are all on a remote server; when something goes wrong, they must rely on the vendor to fix it--which can have varying results depending on the vendor. I would say this is definitely a con of cloud services: you have less control over your content. But, as he mentioned, it would cost the library more to hire the people needed to do the same thing on site. It was an interesting conversation, and I appreciate him giving me a few minutes of his time so I could learn.
The main room that houses this team of people is not much unlike the office space in your average building--except for the books and other library items. There were so many of them! My hands were itching to pick up one (or a dozen) and browse the shelves as I would the library stacks or the shelves at a bookstore. The desk area where I worked for the day was right next to a full wall of shelves and I couldn't help but glance at the titles every so often, picking out ones that I knew or at least heard of. My site supervisor mentioned shadowing one of the people who help process items next time I'm there--I'm going to have to be extra-careful to keep on task and not browse as I work. Perhaps I can browse during a break.
Yesterday, I was tasked with updating a page of the staff site. The page where all the library system-wide policies and procedures are kept needed to have some items deleted, and the remainder updated with ownership information. It sounds like something I could do at home, but I was glad to be there to complete it. First of all, I had to work off a paper packet rather than a digital list. Second, my site supervisor made many notations that I had to ask about, mostly abbreviations of the departments that had ownership of the item. It would have been hard for me to ask as many questions as I did if I had been working from home. I liked being able to walk over to her desk and simply ask "How do you..." and "What is..." It's definitely much easier to collaborate in person.
The rest of this week will be spent on updating another page on the staff site in a similar way. Many of the abbreviations are the same, so I will have far fewer questions and am already familiar with the process. I'll also be updating user permissions for all the users on the staff site (something I definitely know how to do since we've gone over users already in my Drupal class). Someone--not sure if it was a fellow internee or the internship instructor for the MLIS class side of the internship--mentioned that as we go along, we start to gain confidence in our abilities. I think I'm starting to see more of that in myself this week.
Thursday, February 21, 2013
My latest web conquest--wireframing!
When I had done this in the past, I would use pencil and paper to map out where certain pieces of content would go, and make notations for special pieces of content. Basically, I would sketch out the page before I created it. Wireframing accomplishes the same thing, except it's a lot easier and faster to make changes to a design that you're not happy with. The program that my internship site uses is Mockingbird. Each of the items that you put on the page (text, links, drop-down boxes, etc.) are called "widgets," which I think can be a little misleading. When I hear "widget," it makes me think of an object that does something--like my desktop widgets. The widgets in Mockingbird don't do anything except act as place holders.
And that's something that I had to get used to--the idea of a placeholder for content, not the content itself. It took me some time fiddling around with links to figure out that there is no way for me to get them to link to anything--they are only there to show where on the page they will be. You can put in the text of the content to see how much of the page it will take up and how you want to arrange it, but links, buttons, images, and the like are only represented and will not work like they will when you create the final page. You're putting together the layout for content, not the content itself. If you put in a drop-down box widget, it won't act like a drop-down box--because it's not the actual box, just the representation of it. I think I had to play around with the Mockingbird program for almost an hour before I really understood that concept. Once I did, my comfort level with wireframing dramatically increased and my progress went much smoother and faster.
The whole point of this project was to put together the layout for a page where patrons would go to find out about the online books clubs offered by the library. But in the process of putting that together, I learned a whole new (and better) way of doing layout. I will definitely take note of this for my future personal and professional online web design/development projects.
Oh, and the feedback from my first project was overall very positive. But since there seems to be some bugs with posting blogs on the staff site, I had to go back and modify it to exclude those features that are still "buggy." My site supervisor and I agreed that it would be better to do so to prevent staff from getting frustrated with not being able to "do it the way the guide says."
Wednesday, February 13, 2013
First Project Complete!
Last week during my weekly meeting with my site supervisor, I had asked why another guide I was using for comparison had a fairly complex process for including pictures in a post. It didn't make sense to me when all that users have to do is drag pictures into the WYSIWYG text box to include them (the system is set up in a way that does not allow users to upload them directly from their computer--hence the complex process). I first wanted to find out if there was an existing policy that said it had to be done the way outlined by the other guide. If there was, I knew that I would have to create my guide to follow suit. But if there wasn't, I felt that the drag-and-drop method would be a lot more user-friendly because it had fewer steps and was similar to dragging a file from one folder to another (which a lot of people have done if they regularly work on a computer). So, I had to wait a bit for feedback since my supervisor needed to check with another individual to make sure that there wasn't a policy we had to follow. I got the OK to include my suggested method (Yay!) but with a few notes that they wanted me to include as well--mainly to let staff know that the drag-and-drop method is only for the staff site, not the public site (the original method would still need to be used for that).
So I finished the guide and sent it off to my site supervisor. I'm still waiting to get feedback from her about my work.
The week before last, my supervisor made a point of saying that I don't need to rush through the tasks and projects that she gives me, even for the "high-priority" stuff. So with the guide, I was able to take my time, plan it out, get the screenshots I wanted and edit the pictures, and basically do quality work. I'm not sure I would have felt compelled to do as many visuals if I felt pressure to get things done quickly. I feel really lucky that my supervisor is not a I-need-results-yesterday kind of person and is willing to let me take whatever time I feel I need to complete a task and complete it well. My paid librarian position definitely demands more awareness of deadlines, so it's a nice contrast.
The rest of the week will be taken up by research. I'll be trying to find out if some of the things that my site supervisor and the Technical Services team wants to do and include on the site is possible. So it's off to the Drupal how-to's to find some clues. I would love to be able to tell them "Yes it is, and here's how you do it!"
Thursday, February 7, 2013
Creating Guides
Before I even started the project, I took a look at the available guides--the original guide that my work will replace and another guide created for posting blogs on the library's public site. The former gave me an idea of what skill level I would need to accommodate, and the latter let me see an example of a much more complete guide that included illustrations. It is important when creating anything to know your audience and make sure that you are keeping in mind the lowest denominator (aka the lowest skill level) of those that will be using it. This is actually a concept that came up in my first coding class of my MLIS program. To be truly "user friendly," your content will need to reach the greatest number of users possible. Because I knew that screenshots of the pages would be particularly helpful for those less computer savvy, this was my first step. I took a number of screenshots, from the log-in page for the staff all the way through the process to where they save and publish their blog entry.
My next step was to start outlining the process--using language that was not heavy in technical jargon, of course--and editing the screenshots to serve as useful illustrations. This is the part I'm still in the process of completing. As I've been editing, I've realized that there are additional screenshots of particular buttons/features that I now want to include. I'm hoping that this guide doesn't become TOO big with everything that I would like to put in it. I haven't been given a maximum page length, but I know that the longer the guide the less likely anyone will read the entire thing. It needs to be useful both in content and in length; since this is for library staff, I must assume that my audience does not have a lot of free time to read a lengthy how-to guide.
I actually made a discovery as I was doing this (never stop trying to learn new things!). I'm creating the original guide using Microsoft Word, with the intent to convert it into a .pdf file for the format that will actually be made available to the library's staff; this is done both for longevity and to make sure users can't accidentally delete content of the guide and not know how to bring it back, which I can foresee happening with an editable Word file (yes I know editing can be restricted, but that can create problems if passwords to allow future changes are lost). Anyway, as I was using Word, I discovered the beauty of text boxes (something I've never used in Word before because c'mon, it's Word!). One in particular was of a style very appropriate to that of the guide, so now I'm using it to compartmentalize information that may seem like a "duh!" kind of thing for those with my skill level, but would not be immediately obvious to those with less computer comfort. That way, more experienced users can easily skip over this information and spend less time reading/skimming through text they don't need. It's a way to increase accessibility through visual cues. Neat, huh?
I'm very pleased with how the guide has turned out so far and hope to have it completed by tomorrow (I would prefer to finish it today). I've definitely enjoyed letting my creativity play a major role in the design--perhaps this is a skill set I can continue to work on and use to market myself for future library positions.
Friday, February 1, 2013
Enlightenment
Now, I have seen the light (metaphorically of course). I had my Orientation meeting where I was able to discuss a lot with my site supervisor. I had the opportunity to ask questions about the paperwork I need to fill out; my position as far as the county administration is concerned is that of volunteer, even though I have probably more access than the average library volunteer (and more interesting projects!), yet I am still required to fill out the usual paperwork required by any bureaucracy. And I have to keep a time card for the county--not something I had expected! I will be diving into Drupal headfirst--without a parachute, or a cushion to break my fall--and I already know I will be quickly outstripping the instruction provided by my Drupal class that I am simultaneously taking. Which is both a good thing and a bad thing. I will be introduced to a lot of functions and features on the admin side of Drupal that I will not get experience with in my class. But, that also means I may not have much crossover between my internship and my Drupal class.
I already have a nice little to-do list that includes actual assignments coupled with things to start thinking about and features to test to discover functionality problems. I also will be researching the ability to integrate specific file types into a Drupal interface. So a nice variety of practical experience. There was a lot of discussion about tasks/projects that will need to be addressed and accomplished in the future, so I also have a decent idea of where my internship will be going. We again talked about the opportunity for me to be on site for additional face-to-face experience, and I will be submitting various dates to my supervisor for days I would be available to go on-site. My goal is to be there two days a month. I'm already planning on attending the Webmaster's Team meeting in March as one of my two on-site days that month.
So all in all, a good (if belated) start to my internship. This weekend will find me diligently starting my to-do list. At least for a few hours!
