The Electronic Resources selection pages are now finalized.
The official trial period is March 2 through March 31, but some of the trials are already up, and some are ending early. Anything like this has been noted in bold type under the name of the resource.
Please be aware that there are two different pages this year, one for resources with trials.
http://www.gpc.edu/library/technicalservices/db/databasetrials.htm
And one for resources we are considering without trials.
http://www.gpc.edu/library/technicalservices/db/nontrials.htm
There are also hyperlinks on each page, leading to the other one, and separate printer-friendly lists.
It was originally thought that the resources we weren't doing trials of were all ebooks, but some turned out to be databases, so I have noted in parenthesis what is what. (With Credo Reference, I had no idea what to call it.)
We've got a mix of pricing plans this year, subscription and perpetual access (purchase) models, so please pay careful attention to that column. With the addition of ebooks, there are a lot more caveats to consider, so be sure not to miss the "Special Considerations for Some E-Resources" document.
Please let me know if you have any questions, or encounter any problems, and happy evaluating!
Friday, February 27, 2009
Tuesday, February 17, 2009
GPC Libraries on Twitter and Facebook!
Just wanted to let you know that Clarkston's new Circulation Librarian, Ameet Doshi, has gotten us set up on Twitter and Facebook. If you'd like to check it out, I've put links on the Ask a Librarian page, under "Chat with a Librarian".
I don't know if Ameet needs any help managing these new web outposts of GPC Libraries, but I'm sure he wouldn't mind hearing from you.
I don't know if Ameet needs any help managing these new web outposts of GPC Libraries, but I'm sure he wouldn't mind hearing from you.
Labels:
Facebook,
library website,
public services,
Twitter,
Web 2.0
Tuesday, February 03, 2009
Clarkston Water Leak
As you may have already heard, Clarkston has been visited by its now annual water leak. This time it got the circulating stacks, call numbers N through P.
Books that were in that area and not water damaged have been temporarily relocated to trucks on the right side of the aisle. Books that have been too damaged to circulate have been given the location "Clarkston Water Damaged" in the OPAC, which should prevent patrons from requesting them. Eventually, these records will be removed from the OPAC, but we need to leave them in there for the time being to run reports on the damage.
Note: This location will prevent students from requesting these items in the OPAC, but I have no way of preventing librarians and staff from requesting them in the Circulation Module, so please double check the location of any Clarkston book before putting a request on it in the back-end. If the location is Clarkston Water Damaged, please inform the patron that these books have been permanently damaged by a water leak and removed from circulation.
And please let me know if you have any trouble with the OPAC or the back-end not behaving as expected with these items.
Thanks, everyone!
Books that were in that area and not water damaged have been temporarily relocated to trucks on the right side of the aisle. Books that have been too damaged to circulate have been given the location "Clarkston Water Damaged" in the OPAC, which should prevent patrons from requesting them. Eventually, these records will be removed from the OPAC, but we need to leave them in there for the time being to run reports on the damage.
Note: This location will prevent students from requesting these items in the OPAC, but I have no way of preventing librarians and staff from requesting them in the Circulation Module, so please double check the location of any Clarkston book before putting a request on it in the back-end. If the location is Clarkston Water Damaged, please inform the patron that these books have been permanently damaged by a water leak and removed from circulation.
And please let me know if you have any trouble with the OPAC or the back-end not behaving as expected with these items.
Thanks, everyone!
Subscribe to:
Comments (Atom)