In this issue, learn about upcoming library events, tips for requesting materials through I-Share, and, of course, Literary Madness!
The following database trials end later this month:
Proquest Historical Newspaper: Black Newspaper
If you have used any of these databases and would like to have a discussion about possibly subscribing to it, please contact your liaison librarian.
Our next book display is "Women in STEM!" We have a great collection of books about this topic, so make sure to stop by and see what's available. Can't come to the library? Look at our virtual book display guide. We're including ebooks on the guide, which you can check out without physically coming into the library.
Curious about the next book display for April? Our next display is called "We're Still Here: Indigenous Experiences." This display will feature Native voices, topics, and experiences, and highlight how Native communities are a vibrant and active part of society.
COVID can't stop us from our tradition of Literary Madness! Starting Monday, 3/8, keep an eye on email and social media for your first chance to enter your votes for our bracket. This year's categories are the following: Horror, Wanderlust, Celebrity Authors, and Entitled! After week 1, voting forms will only be available via social media, so make sure to follow us on the Instagram, Facebook, and Twitter accounts!
It's that time again! FYI/FYH instructors, please encourage any students you have who you believe is writing, (or has written) an outstanding researching paper to submit to the library by May 28th. First year students, learn more about the research prize and application process here. You have a chance of winning $400 and have your paper uploaded in Digital Commons!
Last summer, the library switched to new behind-the-scenes library software. We have seen some fantastic benefits to that, including single-serve log on and the ability to save searches and favorites. However, consortially, we have had problems with some requests for I-Share materials not processing correctly.
As the software manufacturer works to resolve this issue, here's the easiest work around:
0 Comments.