While working through this unit’s readings, I was interested to learn about the crossover between ER librarians and what I understand constitute special librarians (which, for non-libraryland people, probably sounds very funny, but is – in fact – an actual type of librarian). The two seem to both negotiate in the spaces between business and libraries and therefore must be skilled in multidisciplinary professional strengths: business, law, communications, technology, etc.
"Librarians who find themselves in the role of ER manager often experience this same unsettled feeling because of rapid changes in product availability, new technologies, pricing structures, and licensing terms...Like the products themselves, the ER librarian position still evolves. It plays many roles, e.g. traditional librarianship, Web design, systems management, and accepts many responsibilities, e.g., contract attorney, business manager, technology troubleshooter" (Albitz & Shelburne, 2007).
Yikes!
This is probably where the process mapping discussed by Afifi (2008) comes into play. Process mapping is used in systems development and for managing large and complex projects, whereby business processes are mapped and continually re-evaluated to improve performance and productivity. In Afifi’s (2008) own words, "Process mapping itself is a way of breaking down a process into distinct steps with beginning and end points, somewhat similar to a flow chart.” It shows an input and output, starting with the big picture then get more detailed as it continues. It is also called business process reengineering, and the primary benefit is that it helps to create flexible organizations and help illustrate communication breakdowns, which is especially useful for constantly changing environments like in managing electronic resources from back-end delivery perspective. "Process maps can help businesses understand and control how their companies function, what actions are involved and who is performing the necessary steps to manufacture a product or manage a service." (Afifi, 2008). But where would a topic in ERM be without the need for standards! NISO and the Digital Library Federation (DLF) have tried to help in standardizing process mapping, but according to Afifi (2008), there is no concensus yet.
Afifi (2008) isn’t the only scholar to have touched upon the importance of process mapping in our semester readings. In Unit 11, Weddle (2008) mentioned how important workflow is because different departments use the tools and all share that entry point. Also, Unit 11’s Grogg (2006) pointed out in relation to the necessity of external linking when going from one content provider to another, process mapping is very difficult despite the opportunities that come with it because things like external linking is hard to map and manage.
At first, I was surprised to see the Albitz & Shelburne (2007) survey data showed that most people had been in reference or a bibliographer prior to working as an ER librarian, assuming people in the ERM line of work would come from the Tech Services persuasion. However, in retrospect, I’ve realized that it would be more beneficial to come from experience with hands-on time with the resources to truly understand how they are utilized and user needs. Albitz & Shelburne (2007) highlight this when they write about ER librarians’ "...increased complexity of the position and the need to focus the incumbent's responsibilities on ER management rather than on reference or bibliographic instruction.” This, however, got me thinking about whether there should be a separate degree or specialization for this type of work. Back in LIS 450 during my first semester at SLIS, we talked a little about dividing IT people, or computer science, and librarians. However, ER librarians really seem to be the hybrid breed here, needing a little of everything.
In the handy guide for the “serialist” provided by Griffin (2009), I found the suggestions helpful and the guidance it provided to be something that I would expect from the people who hired me in a serialist position. However, I wonder just how much time someone has to actually go through all the extra research and discovering materials through browsing print reference collections that libraries keep on-hand, especially at a place like UW. I think it's hard enough to really get into the system and workflow of a new employment environment, and I've heard multiple estimates on how many years (yes, years) it takes someone to actually get comfortable with the collection they have at their library. Thus, to go into a new job learning all of this at once, I cannot imagine that this is easy. Ha. Understatement of the year. But it was nice to see that Griffin (2009), too, was an English major like myself and could make it in this area of librarianship – there is hope yet!
And just to throw it out there, I think web developers in libraries will follow a similar pattern that ER librarians have, in going from back-burner "on the side" positions to very up-front and vital to library operations. As libraries recognize the importance of a web presence, I think the jobs of “Web Librarians” will be permanent full-time positions sought after with great urgency. It will be interesting to monitor how this changes the theory behind LIS and either the further separation between or blending of libraries and IT.
Image credit: Wikimedia by Petritap
"Librarians who find themselves in the role of ER manager often experience this same unsettled feeling because of rapid changes in product availability, new technologies, pricing structures, and licensing terms...Like the products themselves, the ER librarian position still evolves. It plays many roles, e.g. traditional librarianship, Web design, systems management, and accepts many responsibilities, e.g., contract attorney, business manager, technology troubleshooter" (Albitz & Shelburne, 2007).
Yikes!
This is probably where the process mapping discussed by Afifi (2008) comes into play. Process mapping is used in systems development and for managing large and complex projects, whereby business processes are mapped and continually re-evaluated to improve performance and productivity. In Afifi’s (2008) own words, "Process mapping itself is a way of breaking down a process into distinct steps with beginning and end points, somewhat similar to a flow chart.” It shows an input and output, starting with the big picture then get more detailed as it continues. It is also called business process reengineering, and the primary benefit is that it helps to create flexible organizations and help illustrate communication breakdowns, which is especially useful for constantly changing environments like in managing electronic resources from back-end delivery perspective. "Process maps can help businesses understand and control how their companies function, what actions are involved and who is performing the necessary steps to manufacture a product or manage a service." (Afifi, 2008). But where would a topic in ERM be without the need for standards! NISO and the Digital Library Federation (DLF) have tried to help in standardizing process mapping, but according to Afifi (2008), there is no concensus yet.
Afifi (2008) isn’t the only scholar to have touched upon the importance of process mapping in our semester readings. In Unit 11, Weddle (2008) mentioned how important workflow is because different departments use the tools and all share that entry point. Also, Unit 11’s Grogg (2006) pointed out in relation to the necessity of external linking when going from one content provider to another, process mapping is very difficult despite the opportunities that come with it because things like external linking is hard to map and manage.
At first, I was surprised to see the Albitz & Shelburne (2007) survey data showed that most people had been in reference or a bibliographer prior to working as an ER librarian, assuming people in the ERM line of work would come from the Tech Services persuasion. However, in retrospect, I’ve realized that it would be more beneficial to come from experience with hands-on time with the resources to truly understand how they are utilized and user needs. Albitz & Shelburne (2007) highlight this when they write about ER librarians’ "...increased complexity of the position and the need to focus the incumbent's responsibilities on ER management rather than on reference or bibliographic instruction.” This, however, got me thinking about whether there should be a separate degree or specialization for this type of work. Back in LIS 450 during my first semester at SLIS, we talked a little about dividing IT people, or computer science, and librarians. However, ER librarians really seem to be the hybrid breed here, needing a little of everything.
In the handy guide for the “serialist” provided by Griffin (2009), I found the suggestions helpful and the guidance it provided to be something that I would expect from the people who hired me in a serialist position. However, I wonder just how much time someone has to actually go through all the extra research and discovering materials through browsing print reference collections that libraries keep on-hand, especially at a place like UW. I think it's hard enough to really get into the system and workflow of a new employment environment, and I've heard multiple estimates on how many years (yes, years) it takes someone to actually get comfortable with the collection they have at their library. Thus, to go into a new job learning all of this at once, I cannot imagine that this is easy. Ha. Understatement of the year. But it was nice to see that Griffin (2009), too, was an English major like myself and could make it in this area of librarianship – there is hope yet!
And just to throw it out there, I think web developers in libraries will follow a similar pattern that ER librarians have, in going from back-burner "on the side" positions to very up-front and vital to library operations. As libraries recognize the importance of a web presence, I think the jobs of “Web Librarians” will be permanent full-time positions sought after with great urgency. It will be interesting to monitor how this changes the theory behind LIS and either the further separation between or blending of libraries and IT.
Image credit: Wikimedia by Petritap
No comments:
Post a Comment