This was my first experience with downloading ebooks admittedly, so this is a new experience for me. I definitely appreciate the convenience of being a able to check out a book via downloading without needing to check out a physical copy, and this definitely comes in handy for wanting to listen to audiobooks on tablets and such. I suppose the biggest obstacle to ebooks being used more frequently in K-12 libraries likely has to do with licensing and digital rights management, where you are limited regarding the choice of books to choose and what the library can or cannot stock without first going through DRM regulations. I noticed when checking out my book that there is a limited selection compared to the physical copies in the main library.
However, I feel that there is a paradigm shift occurring in that libraries will be transitioning more and more to distributing digital content, we've already seen how Kindle and other apps have essentially made the bookstore industry obsolete, so I believe that as time goes on, the availability of ebooks in K-12 libraries will gradually increase.
Of course, there were and I do believe should remain a place for physical copies of books, but the digital distribution method is yet another route that has barely been explored in the practice of library media.
Saturday, July 20, 2013
Thursday, July 18, 2013
Library Automation Review
For this assignment, I chose to take a look at the Koha Library Software system.
Unlike other library automation systems like Sirsi or Voyager which are proprietary systems that require a fee to install, Koha is entirely open source and free to use. This I believe would be a big plus for libraries operating with limited budget and resources.
Among the features included with Koha are full text searching using RDBMS (Relational database management system), a MARC compatible interface, inter-library loan, SQL reports from the latest acquisitions by the library to items in stock, along with fully customizable search functions, including a separate one for authority records (Corporate name, topical term, etc), and more.
Many of these features are relatively common ones you can find in any library automation system. Though one of the advantages with Koha being open source is that librarians have a greater degree more freedom in regards to designing and modifying the site as opposed to closed source software that places restrictions on what librarians can or cannot do. From what I've read, the customization features are fairly simple to do in Koha if one is familiar with HTML and templates. According to the Automation Marketplace article, more and more libraries are opting to use open source software like Koha and Evergreen as opposed to proprietary products.
If I can recommend Koha to both current and future librarians, it would be on the basis that it is free to use, completely customizable, has the standard set of features that proprietary software already has, and from what I've gleamed from the demo, the interface used by Koha appears to be relatively simple and consistent, provided the librarian doesn't go overboard on the complexity when it comes to designing.
And speaking of demo, Koha features demo interfaces that may give people a glimpse at what the software looks like when implemented.
For more information: http://koha-community.org/
Unlike other library automation systems like Sirsi or Voyager which are proprietary systems that require a fee to install, Koha is entirely open source and free to use. This I believe would be a big plus for libraries operating with limited budget and resources.
Among the features included with Koha are full text searching using RDBMS (Relational database management system), a MARC compatible interface, inter-library loan, SQL reports from the latest acquisitions by the library to items in stock, along with fully customizable search functions, including a separate one for authority records (Corporate name, topical term, etc), and more.
Many of these features are relatively common ones you can find in any library automation system. Though one of the advantages with Koha being open source is that librarians have a greater degree more freedom in regards to designing and modifying the site as opposed to closed source software that places restrictions on what librarians can or cannot do. From what I've read, the customization features are fairly simple to do in Koha if one is familiar with HTML and templates. According to the Automation Marketplace article, more and more libraries are opting to use open source software like Koha and Evergreen as opposed to proprietary products.
If I can recommend Koha to both current and future librarians, it would be on the basis that it is free to use, completely customizable, has the standard set of features that proprietary software already has, and from what I've gleamed from the demo, the interface used by Koha appears to be relatively simple and consistent, provided the librarian doesn't go overboard on the complexity when it comes to designing.
And speaking of demo, Koha features demo interfaces that may give people a glimpse at what the software looks like when implemented.
For more information: http://koha-community.org/
Wednesday, July 10, 2013
Website Assignment 1
Having taken a look at the articles related to designing library websites, I shall now provide my five methods on how I would design such a website.
1. Keep it simple
I would most certainly agree to the principle of keeping the website's layout as simple and organized as possible. Without making it overly complex for patrons to access. Fonts, background colors and formats should be easy to read without being distracting to the patron (Though avoid comic sans), information on the library, including reference and contact information, would be best shown in text rather then using graphics. And information to contact library staff and other miscellaneous details like the library's mission statement should be presented in a clear and prominent format. In short, the layout of the website should emphasize information instead of visuals.
2. Accurate accessibility
I would ensure all links to the various web resources on the site lead the patron to where they want to go without unexpectedly opening a window to another site or unrelated page. Links that lead to files such as PDF should include a warning that the patron will require a plug-in. I would recommend links to sites and resources be formatted by bold or underlined text rather then color to avoid confusion with patrons who may be colorblind, in adherence to the first method above. Finally, it is important to keep in mind that websites are a visual interface, for blind or visually impaired students and patrons, including apps like audio browsers would be essential.
3. Keep the userbase demographic in mind
When designing a school-related website, it is important to know what type of audience this site is meant. If say one is designing the site for high school-level students, then using formats such as images would probably not need to rely on images to convey information when simple text will do, whereas middle and elementary-level students would be more likely to respond to visual clues. Depending on which school library I am working for, I would bear this in mind while maintaining the principle of keeping the information simple and consistent.
4. Blog
I maintain that blogs are a very useful tool for use in the educational process that has yet to be fully explored. Using a blog, I would use it for posting information related to events such as Banned Book Week or Black History Month, information on library policy, special collections, inquiries as to the state of the library and other miscellaneous information. A blog would be very simple to use, and it would be open for both teachers and students to provide feedback or insights. Such information would be collated for future use such as purchasing new books and items to add to the curriculum.
5. Content, Content, and more Content.
Ultimately, there is not much to a school library website if there isn't a suitable amount of content. I would strive to include as much content as possible: Reference links, librarian contact info, schedule, item search engine, links to databases, etc. All the while presenting it in an accessible format suited to the grade level of the student.
If anyone has thoughts to share, feel free!
1. Keep it simple
I would most certainly agree to the principle of keeping the website's layout as simple and organized as possible. Without making it overly complex for patrons to access. Fonts, background colors and formats should be easy to read without being distracting to the patron (Though avoid comic sans), information on the library, including reference and contact information, would be best shown in text rather then using graphics. And information to contact library staff and other miscellaneous details like the library's mission statement should be presented in a clear and prominent format. In short, the layout of the website should emphasize information instead of visuals.
2. Accurate accessibility
I would ensure all links to the various web resources on the site lead the patron to where they want to go without unexpectedly opening a window to another site or unrelated page. Links that lead to files such as PDF should include a warning that the patron will require a plug-in. I would recommend links to sites and resources be formatted by bold or underlined text rather then color to avoid confusion with patrons who may be colorblind, in adherence to the first method above. Finally, it is important to keep in mind that websites are a visual interface, for blind or visually impaired students and patrons, including apps like audio browsers would be essential.
3. Keep the userbase demographic in mind
When designing a school-related website, it is important to know what type of audience this site is meant. If say one is designing the site for high school-level students, then using formats such as images would probably not need to rely on images to convey information when simple text will do, whereas middle and elementary-level students would be more likely to respond to visual clues. Depending on which school library I am working for, I would bear this in mind while maintaining the principle of keeping the information simple and consistent.
4. Blog
I maintain that blogs are a very useful tool for use in the educational process that has yet to be fully explored. Using a blog, I would use it for posting information related to events such as Banned Book Week or Black History Month, information on library policy, special collections, inquiries as to the state of the library and other miscellaneous information. A blog would be very simple to use, and it would be open for both teachers and students to provide feedback or insights. Such information would be collated for future use such as purchasing new books and items to add to the curriculum.
5. Content, Content, and more Content.
Ultimately, there is not much to a school library website if there isn't a suitable amount of content. I would strive to include as much content as possible: Reference links, librarian contact info, schedule, item search engine, links to databases, etc. All the while presenting it in an accessible format suited to the grade level of the student.
If anyone has thoughts to share, feel free!
Tuesday, July 9, 2013
Wednesday, July 3, 2013
RSS Review: Feedly and Box.net
Like a lot of people here in this class, I don't use RSS that much. That said, I have taken a look at Feedly, and it does appear to be a viable alternative now that GoogleReader is going defunct. The interface appears very similar to GR allowing users to be more accustomed to its features. And its availability on both desktop and mobile platforms is a huge plus for students. The ability to customize feed options for content management is also a benefit. And with GR now going defunct, Feedly has its own cloud sync technology to improve the app's efficiency when it comes to inputting and organizing data. This review may help explain how much it builds on GR's foundation and improves it: http://www.nytimes.com/2013/05/09/technology/personaltech/three-ways-feedly-outdoes-the-vanishing-google-reader.html?pagewanted=all&_r=0
Another site I use for content management, while it may not exactly count as an RSS feed, its still handy for storing and sharing information, is Box.net. I used this in my technology class last year, and its a good means of storing content and sharing it online, for it too comes with its own cloud sync. You can even customize the HTML on Blogger to share content with it. https://www.box.com/signup/o/sendlargefiles
Another site I use for content management, while it may not exactly count as an RSS feed, its still handy for storing and sharing information, is Box.net. I used this in my technology class last year, and its a good means of storing content and sharing it online, for it too comes with its own cloud sync. You can even customize the HTML on Blogger to share content with it. https://www.box.com/signup/o/sendlargefiles
Blogging History
As I am not a teacher, I have no experience with using blogs as an educational tool, though I can definitely see the potential. Normally, my blogs here were either to turn in assignments, one of which was a technology-related class, and a couple others for me to post random thoughts regarding politics, movies or such. I am familiar with how to customize a blog, including modifying the HTML script to add new features, videos, pictures, documents etc. Hence why I think blogs have potential to be a very resourceful tool in the educational process. Though I'd keep the changes simple as too much complexity can make it confusing to look at.
A shared class blog would definitely help, as would each student having their own personalized blogs with which to gauge and review other people's work. Though of course, the trick would be instructing them on how to manage the different customization available on Blogger and to use their time blogging wisely, as with all social media.
A shared class blog would definitely help, as would each student having their own personalized blogs with which to gauge and review other people's work. Though of course, the trick would be instructing them on how to manage the different customization available on Blogger and to use their time blogging wisely, as with all social media.
Subscribe to:
Comments (Atom)