Skip to main content

Home/ IMT122 OUA Group/ Group items tagged librarians

Rss Feed Group items tagged

Joanne S

blyberg.net » Blog Archive » The Darien Statements on the Library and Librarians - 0 views

  •  
    Blyberg, J., Greenhill, K., & Trainor, C. (2009, April 3). The Darien Statements on the Library and Librarians. blyberg.net. Retrieved October 21, 2010, from http://www.blyberg.net/2009/04/03/the-darien-statements-on-the-library-and-librarians/
Joanne S

What is a Database, really? Data Storage for Librarians « The Other Librarian - 0 views

  • A Text File Good old text is still not a bad way to store data. 
  • If you want to retrieve that information, you can use a script to tell the computer to organize the information in a particular way.   This is called parsing
  • Structured Text As you climb the data food chain, complex systems get developed to organize information. 
  • ...17 more annotations...
  • Mark-up:   Marked information is data that has marks or signals to let a computer distinguish one type of data from the other.  
  • A variable:   A variable happens when you give some data a name. 
  • A string:   A string is a kind of variable that has text.
  • An array:   An array is a type of variable that includes a list used by computer programs for later manipulation.    
  • An object:   Explaining objects in full requires that someone read up on object-oriented programming.  
  • Tree-based  Structures Tree-based structures, or cluster models are a subset of “structured text” data storage models.  
  • XML is probably the best example.
  • data is organized in “parents”, “siblings” and “children”.
  • The Relational Model The relational model is better than a tree-model when your dataset is large and complicated.    The way it works is, instead of thinking in terms of “parents, siblings and children,” you think in term of relationships.
  • the “Primary Key.”   This means that every data object (such as a library) has a way of identifying itself in a unique way
  • a “Foreign Key.”    The Foreign key is a way to associate one dataset (eg. libraries) with another dataset (eg. library branches, hospitals or businesses).
  • This association is called a relationship.
  • In more complicated relationships (called the Many-to-Many relationship), you might have to create a third table to associate two entities.      
  • TEXT/XML Based Text files can be organized in such a way as to accommodate some of the benefits of the relational model.
  • Two examples of XML-based databases include Xindice and Sedna.
  • SQL/Binary-based Databases The more common relational database type is a piece of software running on a server, rather than a set of text files.   They are generally accessed using a standard language called SQL (Structure Query Language), or more specifically SQL as supported by a popular scripting language like PHP, Python or Java.
  • Almost any major web application will have a combination of all these types of data storage methods!  
  •  
    How databases are used in libraries
Joanne S

Librarians rewrite the book on disaster recovery - Storage - Technology - News - iTnews... - 0 views

  •  
    Cochrane, N. (2011, January 18). Librarians rewrite the book on disaster recovery. itnews for Australian Business. Retrieved from http://www.itnews.com.au/News/245107,librarians-rewrite-the-book-on-disaster-recovery.aspx
Joanne S

Kroski, E. (2008). Web 2.0. In Web 2.0 for librarians and information professionals - 0 views

  •  
    Kroski, E. (2008). Web 2.0. In Web 2.0 for librarians and information professionals. New York: Neal-Schuman.  (Available from: https://auth.lis.curtin.edu.au/cgi-bin/auth-ng/authredirect.cgi?redirurl=http://edocs.lis.curtin.edu.au/eres.cgi&url=dc60266981 )
Joanne S

Emerald | Diffusion of innovation theories and their relevance to understanding the rol... - 0 views

  •  
    Holland, M. (1997). Diffusion of innovation theories and their relevance to understanding the role of librarians when introducing users to networked information. The Electronic Library, 15(5), 389-394. doi:10.1108/eb045587 Start at part 2. Background and History p.390 
Joanne S

A social media policy for a one branch public library » Librarians Matter - 1 views

  • “Social Media.” includes community created content sites like Blogs, Forums, Flickr, YouTube, Wikis, Social Networks, Twitter and other content sharing sites.
  • When you use social media your behaviour  and content is not only a reflection of you but also of (our) Library.
  • Social Media Do’s Be Professional – Talk the way you would talk to real people in professional situations. Be Courteous – Be sure to listen & ask questions. Be Accurate – Check your facts before you post and provide supporting sources if necessary. Be Useful – Add content because you have something interesting to say, not for the sake of regular posting. Be Intelligent – Provide some value. Don’t talk down. Offer insight. Be Conversational –  Avoid overly pedantic or “composed” language. Don’t be afraid to bring in your own personality. Be Non-confrontational – If you disagree, do so respectfully Be Prompt – If you need to moderate or respond to a comment do so as quickly as possible Be Identifiable – Use your real name and do not post anonymously. Be Transparent – Disclose that you work for the library if this is relevant and be honest & truthful. Social Media Don’ts Don’t Share Secrets –If you aren’t sure you can disclose something, just don’t do it. Think about privacy, confidentiality and permission to use other people’s content. Don’t Bad Mouth – Keep the language clean & avoid slamming people or companies. Don’t Complain – If you don’t have anything nice to say, don’t say anything at all. Don’t do Stupid Things – If it doesn’t help the Library or our community, don’t do it. Don’t Defame – Show everyone respect. Don’t Forget your day job –Social Media can consume you so don’t forget your other duties. Moderate, balanced use is essential.
  •  
    Greenhill, K., & Fay, J. (2010, September 10). A social media policy for a one branch public library. Librarians Matter. Retrieved October 1, 2010, from http://librariansmatter.com/blog/2010/09/10/a-social-media-policy-for-a-one-branch-public-library/
Joanne S

Keeping up: strategic use of online social networks for librarian current awareness. - 0 views

  •  
    Online social networks for current awareness Cook, S., & Wiebrands, C. (2010). Keeping up: strategic use of online social networks for librarian current awareness. In VALA 2010: Connections. Content. Conversations. Melbourne, Victoria. Retrieved from http://www.vala.org.au/vala2010/papers2010/VALA2010_78_Cook_Final.pdf
Joanne S

Library 2.0 Discussion: Michael Squared | Librarian in Black Blog - Sarah Houghton - 0 views

  •  
    Houghton-Jan, S. (2005, December 19). Library 2.0 Discussion: Michael Squared. The Librarian in Black. Retrieved April 16, 2011, fromhttp://librarianinblack.net/librarianinblack/2005/12/library_20_disc.html
Joanne S

The Code4Lib Journal - How Hard Can It Be? : Developing in Open Source - 0 views

  • We experienced freedom to explore alternate avenues, to innovate, to take risks in ways that would have been difficult under the direct control of a district council.
  • patrons made it clear that while they appreciated that computers were a necessary part of a modern library, they did not consider them the most important part.
  • Our overall objective was to source a library system which: could be installed before Y2K complications immobilised us, was economical, in terms of both initial purchase and future license and maintenance support fees, ran effectively and fast by dial-up modem on an ordinary telephone line, used up-to-the minute technologies, looked good, and was easy for both staff and public to use, took advantage of new technology to permit members to access our catalogue and their own records from home, and let us link easily to other sources of information – other databases and the Internet. If we could achieve all of these objectives, we’d be well on the way to an excellent service.
  • ...14 more annotations...
  • "How hard can it be" Katipo staff wondered, "to write a library system that uses Internet technology?" Well, not very, as it turned out.
  • Koha would thus be available to anyone who wanted to try it and had the technical expertise to implement it.
  • fairly confident that we already had a high level of IT competence right through the staff, a high level of understanding of what our current system did and did not do.
  • ensure the software writers did not miss any key points in their fundamental understanding of the way libraries work.
  • The programming we commissioned cost us about 40% of the purchase price of an average turn-key solution.
  • no requirement to purchase a maintenance contract, and no annual licence fees.
  • An open source project is never finished.
  • Open source projects only survive if a community builds up around the product to ensure its continual improvement. Koha is stronger than ever now, supported by active developers (programmers) and users (librarians)
  • There are a range of support options available for Koha, both free and paid, and this has contributed to the overall strength of the Koha project.
  • Vendors like Anant, Biblibre, ByWater, Calyx, Catalyst, inLibro, IndServe, Katipo, KohaAloha, LibLime, LibSoul, NCHC, OSSLabs, PakLAG, PTFS, Sabinet, Strategic Data, Tamil and Turo Technology take the code and sell support around the product, develop add-ons and enhancements for their clients and then contribute these back to the project under the terms of the GPL license.
  • FRBR [5] arrangement, although of course it wasn’t called that 10 years ago, it was just a logical way for us to arrange the catalogue. A single bibliographic record essentially described the intellectual content, then a bunch of group records were attached, each one representing a specific imprint or publication.
  • The release of Koha 3.0 in late 2008 brought Koha completely into the web 2.0 age and all that entails. We are reconciled to taking a small step back for now, but the FRBR logic is around and RDA should see us back where want to be in a year or so – but with all the very exciting features and opportunities that Koha 3 has now.
  • In the early days, the Koha list appeared to have been dominated by programmers but I have noticed a lot more librarians participating now
  • "Adopt technology that keeps data open and free, abandon[ing] technology that does not." The time is right for OSS.
  •  
    For more information about Koha and how it was developed, see: Ransom, J., Cormack, C., & Blake, R. (2009). How Hard Can It Be? : Developing in Open Source. Code4Lib Journal, (7). Retrieved from http://journal.code4lib.org/articles/1638
Joanne S

The Strongest Link: Libraries and Linked Data - 0 views

  • For many years now we have been hearing that the semantic web is just around the corner
  • most libraries, however, is that we are still grappling with 2.0 technologies.
  • By marking up information in standardized, highly structured formats like Resource Description Framework (RDF), we can allow computers to better "understand" the meaning of content
  • ...17 more annotations...
  • For most librarians this concept is fairly easy to understand. We have been creating highly structured machine-readable metadata for many years
  • By linking our data to shared ontologies that describe the properties and relationships of objects, we begin to allow computers not just to "understand" content, but also to derive new knowledge by "reasoning" about that content.
  • the term "Semantic Web" to refer to a full suite of W3C standards including RDF, SPARQL query language, and OWL web ontology language.
  • This article will outline some of the benefits that linked data could have for libraries, will discuss some of the non-technical obstacles that we face in moving forward, and will finally offer suggestions for practical ways in which libraries can participate in the development of the semantic web.
  • What benefits will libraries derive from linked data?
  • Having a common format for all data would be a huge boon for interoperability and the integration of all kinds of systems.
  • The linking hub would expose a network of tightly linked information from publishers, aggregators, book and journal vendors, subject authorities, name authorities, and other libraries.
  • semantic search could take us far beyond the current string-matching capabilities of search engines like Google.
  • What are the major obstacles for libraries?
  • A fundamental challenge for the development of linked data in libraries is lack of awareness.
  • Linked Data becomes more powerful the more of it there is.
  • Until there is enough linking between collections and imaginative uses of data collections there is a danger librarians will see linked data as simply another metadata standard, rather than the powerful discovery tool it will underpin.
  • a more practical concern is that changing the foundation of library metadata is no trivial task.
  • Privacy is a huge concern for many interested in linked data.
  • Related to privacy is trust.
  • Rights management poses potential problems for linked data in libraries. Libraries no longer own much of the content they provide to users; rather it is subscribed to from a variety of vendors.
  • What needs to happen to move libraries to the next level?
  •  
    Byrne, G., & Goddard, L. (2010). The Strongest Link: Libraries and Linked Data. D-Lib Magazine, 16(11/12). doi:10.1045/november2010-byrne Retrieved from http://www.dlib.org/dlib/november10/byrne/11byrne.html
Joanne S

Taylor & Francis Online :: Optimal Results: What Libraries Need to Know About Google an... - 0 views

  •  
    Cahill, K., & Chalut, R. (2009). Optimal Results: What Libraries Need to Know About Google and Search Engine Optimization. The Reference Librarian, 50(3), 234-247. doi:10.1080/02763870902961969 ( You will need to be logged into Curtin Library to access this).
Joanne S

K. G Schneider, "The Thick of the Fray: Open Source Software in Libraries in the First ... - 0 views

  • the vast majority of libraries continue to rely on legacy proprietary systems
  • libraries using open source integrated library systems indicates that the vast majority of libraries continue to rely on legacy proprietary systems
  • there are at least a dozen active OSS projects based in or with their genesis in library organizations
  • ...10 more annotations...
  • xCatalog
  • LibraryFind
  • Blackligh
  • iVia,
  • What makes OSS different from proprietary software is that it is free in every sense of the word: free as in “no cost,” free as in “unencumbered” and free as in “not locked up.”
  • questioned whether OSS is overall less expensive than its proprietary counterparts and has called for libraries to look hard at cost factors
  • OSS projects are thriving communities with leaders, followers, contributors, audiences and reputation systems.
  • Like so many things librarians hold dear – information, books and library buildings themselves – OSS is open, available and visible for all to see
  • OSS presents important opportunities for libraries
  • This is the world we want to be in again. It will not always be easy, and there will be a few spectacular failures. But there will also be spectacular successes – and this time, they will happen in the open.
Joanne S

How the W3C Has Come To Love Library Linked Data - 0 views

  • The number of influential libraries publishing their metadata onto the web as linked open data, which is the heart of the Semantic Web, is growing
  • many librarians at major institutions have recognized that a key to the bibliographic future lies in migrating their data out of library silos and into an open, global pool of shared data.
  • the linked data cloud is seen as the most promising way to ensure that library data remains accessible and reusable
  • ...11 more annotations...
  • "If libraries are to retain their role as curators of the intellectual products of society, their assets must be part of that search stream."
  • web entities such as DBpedia, which offers a Semantic Web mirror of Wikipedia
  • libraries have begun to reconceptualize metadata and publish it on the web using linked data technologies, such as the Resource Description Framework (RDF) language and its extensions OWL, SKOS, and SPARQL.
  • library metadata is formatted and linked in RDF, then library content will surface more prominently in web search results
  • Recommendations from W3CThe report is still being finalized but the draft recommends that libraries:
  • — create web addresses using Uniform Resource Identifiers (URIs) as globally unique, web-compatible identifiers for the resources (any kind of object or concept) they manage and the metadata elements they use
  • — develop library data standards that are compatible with linked data
  • — use their expertise in metadata management to become full partners
  • — foster a discussion about open data and rights.
  • — explore using libraries' ethos of quality control in the curation and long-term preservation of linked data datasets and vocabularies.
  • "As the shared understanding expands, the benefits of publishing linked data are becoming clearer,"
  •  
    Kelley, M. (2011). How the W3C Has Come To Love Library Linked Data. Library Journal. Retrieved from http://www.libraryjournal.com/lj/home/891826-264/how_the_w3c_has_come.html.csp#.TmSTdJXQprl.twitter
1 - 17 of 17
Showing 20 items per page