This is a good opportunity for those considering a Spring 2009 internship that haven't finalized their plans.
Job Title: Literacy Specialist Internship - Northeast Library
Closing Date/Time: Fri. 01/02/09 5:00 PM Central Time
Salary: See Position Description
Job Type: Internship
Location: Northeast Library, Minnesota
Department: Library
Literacy Specialist Internship
Hennepin County Library
Hennepin County Library - Northeast Library is offering an internship opportunity to develop programs, services and resources to support literacy initiatives at the Library. This is an excellent opportunity for students in early elementary education, youth services librarianship, or youth development.
Commitment:
Winter semester 2009, 120 hours - part-time, flexible weekday/weekend/daytime/evening.
Wage:
This is an upaid position. The Intern will receive academic/internship credit through the college or university where enrolled.
Location:
Northeast Library, 2200 Central Avenue NE, Minneapolis and Northeast Middle School, 2955 Hayes Street NE, Minneapolis.
Job Duties:
At the school you will lead book clubs two Fridays a month over the lunch break.
At the library you will observe and lead storytimes, assist with storytime preparation, assist with collection management, observe and possibly lead other book clubs, offer informal literacy activities to children in the library, prepare for your book clubs, and observe and assist with reference services to all ages.
Requirements:
This is an excellent opportunity for a student completing a bachelor's or master's degree in elementary education, youth development, library science or a related area of study. Ideal candidates will be creative, reliable, patient, adaptable and possess the ability to approach and engage youth, and will possess a strong commitment to literacy and libraries.
To Apply and for Questions:
Send cover letter outlining qualifications for this position, resume and contact information for two references to:
Tom.Grund@co.hennepin.mn.us
- OR -
Tom Grund
Hennepin County Library - Ridgedale
12601 Ridgedale Drive
Minnetonka, MN 55305
(952) 847-8518
For more information contact Susan Woodwick at smwoodwick@hclib.org or (612) 630-6903.
Wednesday, December 3, 2008
Tuesday, December 2, 2008
Job posting - Washington State
King County Library System, Washington State
Lead Library Assistant II- Full Time
Job number: 2008-272
King County Library System, Auburn/Muckleshoot/Algona-Pacific Cluster
Application Deadline is December 15, 2008
Library Assistants are usually the first point of contact in KCLS libraries. As customer services representatives they provide basic information about KCLS materials, programs and services. This position directs the work of Library Assistants at multiple branch locations. Performs circulation services to patrons and resolves problems and answers questions of patrons.
REQ: A typical way of obtaining the knowledge, skills and abilities outlined above is with a high school diploma or GED, supplemented by some post-secondary training in a related field, plus 2-4 yrs experience in library operations, policies and procedures. Application deadline is December 15, 2008. $21.434 per hour plus excellent benefits. Send completed KCLS application and supplemental questionnaire (available on our website) to:
HR, King County Library System
960 Newport Way NW
Issaquah WA 98027
425-369-3224
Fax: 425-369-3214
www.kcls.org <http://www.kcls.org/>
EOE
Thank you,
Susan Hang
Human Resources Technician II
King County Library System
960 Newport Way NW
Issaquah, WA 98027
425-369-3224
FAX: 425-369-3214
Jobline: 425-369-3222
www.kcls.org <http://www.kcls.org>
Lead Library Assistant II- Full Time
Job number: 2008-272
King County Library System, Auburn/Muckleshoot/Algona-Pacific Cluster
Application Deadline is December 15, 2008
Library Assistants are usually the first point of contact in KCLS libraries. As customer services representatives they provide basic information about KCLS materials, programs and services. This position directs the work of Library Assistants at multiple branch locations. Performs circulation services to patrons and resolves problems and answers questions of patrons.
REQ: A typical way of obtaining the knowledge, skills and abilities outlined above is with a high school diploma or GED, supplemented by some post-secondary training in a related field, plus 2-4 yrs experience in library operations, policies and procedures. Application deadline is December 15, 2008. $21.434 per hour plus excellent benefits. Send completed KCLS application and supplemental questionnaire (available on our website) to:
HR, King County Library System
960 Newport Way NW
Issaquah WA 98027
425-369-3224
Fax: 425-369-3214
www.kcls.org <http://www.kcls.org/>
EOE
Thank you,
Susan Hang
Human Resources Technician II
King County Library System
960 Newport Way NW
Issaquah, WA 98027
425-369-3224
FAX: 425-369-3214
Jobline: 425-369-3222
www.kcls.org <http://www.kcls.org>
Monday, December 1, 2008
Google Gmail Notifier Doesn't Recognize Google Chrome As A Browser
Every once in a while internet users will notice an incompatibility within Google's programs. Today, a user discovered that Google's Gmail Notifier is not compatible with Google Chrome.I thought this pic was worth at least one laugh. I'm sure it won't take long for Google to fix the problem, but it would be good for all of their applications to be compatible.
Google is one of the few companies that doesn't get to make an honest mistake because they seem to be under such very strong public scrutiny.
One of the first things I noticed when I started using Google Chrome was that it was a very fast browser. One of the major things that it was clearly missing was the ability to add some kind of add-on or plugin. I'm sure future versions will carry the feature. Another thing I'd like to see resolved is the ability to login to my bank. Right now only Internet Explorer and FireFox are supported.
More Blogging MLA... Introduction to RDA/FRBR
No, we're not talking about Recommended Dietary Allowances, nor are we talking about a particular child rearing method, although one says FRBR like "Ferber." We're talking serious insider cataloging baseball talk. And nothing says "cataloging" like a bunch o' acronyms.
RDA, or Resource Description and Access, is the "new" AACR2r (that's Anglo-American Cataloging Rules, 2nd Edition, Revised), bringing library cataloging standards right into the 1990s. Uh, I mean the 21st century. FRBR, or Functional Requirements for Bibliographic Records, builds on an entity relationship model for cataloging resources. Until I went to this session, I confess, I did not really "get" FRBR. I've read quite a bit, I generally think I'm pretty quick to figure things out. But for whatever reason, I did not have a good understanding of what FRBR did. After 45 minutes with Chew Chiat Naun, Principal Cataloger at the University of Minnesota Libraries, I had a true "ah-ha!" moment, when it finally all clicked together. Here's my attempt to explain:
Basically, a catalog, or metadata, record for an item has some information that is unique to that particular item and some information that may be shared by other records. FRBR is an attempt to notice those differences in the information, and make distinctions between them by introducing different language to describe them. Let's consider the first book in the Harry Potter series, Harry Potter and the Philosophers's Stone. The basic intellectual concept of the story is the work. Once that information is put into a tangible form, it becomes an expression of the work, with potentially different manifestations of the work: The book with the U.S. title, Harry Potter and the Sorcerer's Stone, the audio book (which might be on CD or as a digital download), the large print edition, and so on. Eventually, we get to the item, the specific manifestation that Library A gives the call number, Juv Fic Row and barcodes with 3030222169788.
Then we look at what information is shared between all manifestations. Name of the creator, title, date of copyright, and basic topical controlled vocabulary terms would be shared. What is unique to the manifestation? The carrier (print book or audio CD), descriptive information that goes along with the carrier (the book's dimensions and number of pages, for example), publisher. What is unique to the item? Call number, barcode, local notes. RDA uses the framework provided by FRBR to restructure the elements of describing the various manifestations of an expression of a work. All that perfectly clear? That's what I thought.
Anyway, back to the session. I had my ah-ha moment about midway through the session. In a perfect world, we would have library catalog systems that would allow us to take full advantage of this entity relationship model and we could link all this information together. For example, J. K. Rowling writes other books too and is involved with other works (the movies, etc.); rather than copy her name into every metadata record for something she's been involved with, there should be a name authority record for her (actually, there is), and we should just plug in the identification number for that authority record into the information for the manifestation we're cataloging (that part, we can't do yet). Same thing with publisher. Have the version published by Scholastic? Look up the publisher authority record and put the number for Scholastic into the record (nope, can't do that yet either).
So, I had the epiphany that we should work toward an "HDTV" moment for library cataloging, where we move from the flat-file model we have now with metadata records that literally contain all of this information over and over again, to a "virtual" bibliographic/metadata record that fully makes use of the relationships between these information pieces and uses linking data to bring the user a uniform display that looks like what we're used to seeing. No reason we can't do that. Just need the will and some reinvestment in time and energy.
Anyway, the session went over some more nitty-gritty details of RDA changes, like moving from "main entry," to "preferred access point," no longer using GMD (General Material Designation) to media/carrier/content, and no more "rule of three" regarding access points. And, at some point, there's gonna be a whole lotta trainin' goin' on.
RDA, or Resource Description and Access, is the "new" AACR2r (that's Anglo-American Cataloging Rules, 2nd Edition, Revised), bringing library cataloging standards right into the 1990s. Uh, I mean the 21st century. FRBR, or Functional Requirements for Bibliographic Records, builds on an entity relationship model for cataloging resources. Until I went to this session, I confess, I did not really "get" FRBR. I've read quite a bit, I generally think I'm pretty quick to figure things out. But for whatever reason, I did not have a good understanding of what FRBR did. After 45 minutes with Chew Chiat Naun, Principal Cataloger at the University of Minnesota Libraries, I had a true "ah-ha!" moment, when it finally all clicked together. Here's my attempt to explain:
Basically, a catalog, or metadata, record for an item has some information that is unique to that particular item and some information that may be shared by other records. FRBR is an attempt to notice those differences in the information, and make distinctions between them by introducing different language to describe them. Let's consider the first book in the Harry Potter series, Harry Potter and the Philosophers's Stone. The basic intellectual concept of the story is the work. Once that information is put into a tangible form, it becomes an expression of the work, with potentially different manifestations of the work: The book with the U.S. title, Harry Potter and the Sorcerer's Stone, the audio book (which might be on CD or as a digital download), the large print edition, and so on. Eventually, we get to the item, the specific manifestation that Library A gives the call number, Juv Fic Row and barcodes with 3030222169788.
Then we look at what information is shared between all manifestations. Name of the creator, title, date of copyright, and basic topical controlled vocabulary terms would be shared. What is unique to the manifestation? The carrier (print book or audio CD), descriptive information that goes along with the carrier (the book's dimensions and number of pages, for example), publisher. What is unique to the item? Call number, barcode, local notes. RDA uses the framework provided by FRBR to restructure the elements of describing the various manifestations of an expression of a work. All that perfectly clear? That's what I thought.
Anyway, back to the session. I had my ah-ha moment about midway through the session. In a perfect world, we would have library catalog systems that would allow us to take full advantage of this entity relationship model and we could link all this information together. For example, J. K. Rowling writes other books too and is involved with other works (the movies, etc.); rather than copy her name into every metadata record for something she's been involved with, there should be a name authority record for her (actually, there is), and we should just plug in the identification number for that authority record into the information for the manifestation we're cataloging (that part, we can't do yet). Same thing with publisher. Have the version published by Scholastic? Look up the publisher authority record and put the number for Scholastic into the record (nope, can't do that yet either).
So, I had the epiphany that we should work toward an "HDTV" moment for library cataloging, where we move from the flat-file model we have now with metadata records that literally contain all of this information over and over again, to a "virtual" bibliographic/metadata record that fully makes use of the relationships between these information pieces and uses linking data to bring the user a uniform display that looks like what we're used to seeing. No reason we can't do that. Just need the will and some reinvestment in time and energy.
Anyway, the session went over some more nitty-gritty details of RDA changes, like moving from "main entry," to "preferred access point," no longer using GMD (General Material Designation) to media/carrier/content, and no more "rule of three" regarding access points. And, at some point, there's gonna be a whole lotta trainin' goin' on.
Subscribe to:
Posts (Atom)