Skip to main content

Home/ IMT122 OUA Group/ Group items tagged likes

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Joanne S

Eli Pariser: Beware online "filter bubbles" | Video on TED.com - 0 views

www.ted.com/...are_online_filter_bubbles.html

IMT122 Reading List Week 04 Essential Reading video Topic 04 IMT122

shared by Joanne S on 11 Sep 12 - No Cached
    • Joanne S
      Joanne S on 04 Oct 12
       
      Mark Zuckerberg, a journalist was asking him a question about the news feed. And the journalist was asking him, "Why is this so important?" And Zuckerberg said, "A squirrel dying in your front yard may be more relevant to your interests right now than people dying in Africa." And I want to talk about what a Web based on that idea of relevance might look like. So when I was growing up in a really rural area in Maine, the Internet meant something very different to me. It meant a connection to the world. It meant something that would connect us all together. And I was sure that it was going to be great for democracy and for our society. But there's this shift in how information is flowing online, and it's invisible. And if we don't pay attention to it, it could be a real problem. So I first noticed this in a place I spend a lot of time -- my Facebook page. I'm progressive, politically -- big surprise -- but I've always gone out of my way to meet conservatives. I like hearing what they're thinking about; I like seeing what they link to; I like learning a thing or two. And so I was surprised when I noticed one day that the conservatives had disappeared from my Facebook feed. And what it turned out was going on was that Facebook was looking at which links I clicked on, and it was noticing that, actually, I was clicking more on my liberal friends' links than on my conservative friends' links. And without consulting me about it, it had edited them out. They disappeared. So Facebook isn't the only place that's doing this kind of invisible, algorithmic editing of the Web. Google's doing it too. If I search for something, and you search for something, even right now at the very same time, we may get very different search results. Even if you're logged out, one engineer told me, there are 57 signals that Google looks at -- everything from what kind of computer you're on to what kind of browser you're using to where you're located -- that it uses to personally tailor you
Joanne S

"Likes" are lovely, but do they lead to more logins? - 0 views

crln.acrl.org/...18.long

Week 11 Week 10 IMT122 IMT122 Reading List Social Media & the Information Professional Supplementary Reading likes

shared by Joanne S on 09 Nov 12 - No Cached
  • Joanne S on 09 Nov 12
     
    Evaluating library use of social media Glazer, H. (2012). "Likes" are lovely, but do they lead to more logins? College & Research Libraries News, 73(1), 18-21. Retrieved from http://crln.acrl.org/content/73/1/18.long
Joanne S

The Strongest Link: Libraries and Linked Data - 0 views

www.dlib.org/...11byrne.html

IMT122 Reading List Supplementary Reading Week 03 Linked Data Topic 03 IMT122

shared by Joanne S on 10 Sep 12 - Cached
  • 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?
  • Joanne S on 10 Sep 12
     
    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

Best content in BA (LCIM) | Diigo - Groups - 2 views

groups.diigo.com/ba-lcim

shared by Joanne S on 22 Nov 12 - No Cached
  • Joanne S on 22 Nov 12
     
    Open to everyone studying for the BA (Librarianship and Corporate Information Management) through OUA. A social bookmarking group to save and collect sites, interesting links for our degree, units, profession. Consider installing toolbar hwww.diigo.com/tools Change Alert settings to Daily/Weekly as you like
Joanne S

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

journal.code4lib.org/...1638

IMT122 Essential Reading Week 06 Task 06 Koha

shared by Joanne S on 02 Oct 12 - Cached
  • 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.
  • Joanne S on 02 Oct 12
     
    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

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

librariansmatter.com/...or-a-one-branch-public-library

Week 11 Topic 10 IMT122 IMT122 Reading List Essential Reading Social Media & the Information Professional Policy Social Media

shared by Joanne S on 09 Nov 12 - No Cached
  • “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.
  • Joanne S on 09 Nov 12
     
    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

Reprogramming The Museum | museumsandtheweb.com - 0 views

www.museumsandtheweb.com/...reprogramming_the_museum

IMT122 Essential Reading Week 08 Topic 07 IMT122 Reading List Portals Widgets and Remix

shared by Joanne S on 05 Oct 12 - No Cached
  • Powerhouse experie
  • her APIs
  • Flickr AP
  • ...23 more annotations...
  • Thomson Reuters OpenCalais
  • OCLC's WorldCat
  • Before we began our work on the Commons on Flickr, some museum colleagues were concerned that engaging with the Flickr community would increase workloads greatly. While the monitoring of the site does take some work, the value gained via the users has far outweighed any extra effort. In some cases, users have dated images for us.
  • In subsequent use of the Flickr API, we appropriated tags users had added to our images, and now include them in our own collection database website (OPAC). We also retrieved geo-location data added to our images for use in third party apps like Sepiatown and Layar.
  • In our case the purpose of creating an API was to allow others to use our content.
  • So consider the questions above not in the context of should we or shouldn't we put our data online (via an API or otherwise) but rather in the context of managing expectations of the data's uptake.
  • Steps to an API
  • several important things which had to happen before we could provide a public web API. The first was the need to determine the licence status of our content.
  • The drive to open up the licensing of our content came when, on a tour we conducted of the Museum's collection storage facilities for some Wikipedian
  • This prompted Seb Chan to make the changes required to make our online collection documentation available under a mix of Creative Commons licences. (Chan, April 2009)
  • Opening up the licensing had another benefit: it meant that we had already cleared one hurdle in the path to creating an API.
  • The Government 2.0 Taskforce (http://gov2.net.au/about/) was the driver leading us to take the next step.
  • "increasing the openness of government through making public sector information more widely available to promote transparency, innovation and value adding to government information"
  • the first cultural institution in Australia to provided a bulk data dump of any sort.
  • The great thing about this use is that it exposes the Museum and its collection to the academic sector, enlightening them regarding potential career options in the cultural sector.
  • I will briefly mention some of the technical aspects of the API now for those interested. In line with industry best practice the Powerhouse Museum is moving more and more to open-source based hosting and so we chose a Linux platform for serving the API
  • Images are served from the cloud as we had already moved them there for our OPAC, to reduce outgoing bandwidth from the Museum's network.
  • Once we had the API up and running, we realised it would not be too much work to make a WordPress plug-in which allowed bloggers to add objects from our collection to their blogs or blog posts. Once built, this was tested internally on our own blogs. Then in early 2011 we added it to the WordPress plugin directory: http://wordpress.org/extend/plugins/powerhouse-museum-collection-image-grid/
  • One of the main advantages the API has over the data dump is the ability to track use.
  • It is also worth noting that since the API requests usually do not generate pages that are rendered in a browser it is not possible to embed Google Analytics tracking scripts in the API's output.
  • y requiring people to sign up using a valid email address before requesting an API key we are able to track API use back to individuals or organisations.
  • Concerns that people would use the API inappropriately were dealt with by adding a limit to the number of requests per hour each key can generate
  • An Application Programming Interface (API) is a particular set of rules and specifications that a software program can follow to access and make use of the services and resources provided by another particular software program
  • Joanne S on 05 Oct 12
     
    Dearnley, L. (2011). Repreogramming the museum. In Museums and the Web 2011 : Proceedings. Presented at the Museums and the Web 2011, Toronto: Archives & Museum Informatics. Retrieved from http://conference.archimuse.com/mw2011/papers/reprogramming_the_museum
Felipp Crawly

Amazing Customer Service - 1 views

I would like to thank Onward Process Solutions for greatly helping me with my need for assistance in a Customer service outsourcing project. They provided me with 24/7 phone/ email answering serv...

started by Felipp Crawly on 31 Oct 12 no follow-up yet
Joanne S

Archives & Museum Informatics: Museums and the Web 2009: Paper: Gow, V. et al., Making ... - 0 views

www.museumsandtheweb.com/...gow.html

IMT122 Reading List IMT122 Week 10 Topic 09 Essential Reading

shared by Joanne S on 22 Oct 12 - No Cached
  • New Zealand content difficult to discover, share and use
  • DigitalNZ is testing ways to create digital content, collect and share existing digital content, and build smart, freely available search and discovery tools.
  • Memory Maker blurs the line between consuming and producing content. What’s sometimes called ‘remix culture’ […]. Digital technologies have opened up new possibilities for young people to access and represent the stories of their culture by taking sound and images and recombining them to say something new, something relevant to them. (Sarah Jones, Lunch Box: Software & digital media for learning, November 2008) http://lunchbox.org.nz/2008/11/get-coming-home-on-your-schools-website-wiki-or-blog/)
  • ...7 more annotations...
  • The Memory Maker provides a taste of what is possible when collecting institutions modernise their practices for keeping and managing copyright information, using Creative Commons licenses or ‘no known copyright’ statements.
  • Learning about ‘hyperlinks’ today, these young New Zealanders will be the developers and creators of tomorrow.
  • The full set of contributions is accessible through a Coming Home search tool, occasionally on a google-like hosted search page (Figure 5), but more often through a search widget embedded on many New Zealand Web sites (Figure 6).
  • Digital New Zealand is developing and testing solutions that showcase what’s possible when we really focus on improving access to and discovery of New Zealand content.
  • Technically, the Digital New Zealand system is in three parts: a backend, a metadata store, and a front end.
  • The coolest thing to be done with your data will be thought of by someone else
  • “an API is basically a way to give developers permission to hack into your database”.
  • Joanne S on 22 Oct 12
     
    Gow, V., Brown, L., Johnston, C., Neale, A., Paynter, G., & Rigby, F. (2009). Making New Zealand Content Easier to Find, Share and Use. In Museums and the Web 2009. Presented at the Museums and the Web 2009, Toronto: Archives & Museum Informatics, Retrieved from http://www.archimuse.com/mw2009/papers/gow/gow.html
Joanne S

What is Cloud Computing and How will it Affect Libraries? | TechSoup for Libraries - 0 views

www.techsoupforlibraries.org/...d-how-will-it-affect-libraries

IMT122 Reading List Supplementary Reading Technology for Information Managment_Hardware Cloud Computing Topic 01 IMT122

shared by Joanne S on 03 Sep 12 - Cached
  • If you’ve used any of the popular Web 2.0 services over the past few years (e.g. Gmail, Wikipedia, Flickr or Twitter), you already have some experience with cloud computing
  • Like water and electricity, a computing cloud is a communally-shared resource that you lease on a metered basis, paying for as little or as much as you need, when you need it
    • Joanne S
      Joanne S on 13 Sep 12
       
      Benefits-  Cost Savings, Flexibility and Innovation.
  • ...4 more annotations...
  • As individuals and members of organizations, we’re already choosing between desktop applications and cloud applications when it comes to e-mail, RSS, file storage, word processing and other simple applications. Sooner or later we’ll have to make this choice for mission-critical enterprise applications too
  • Libraries may soon be building and managing their own data centers.
  • For more practical, technical explanations of cloud computing, check out the Wikipedia article the Anatomy of Cloud Computing the MIT Technology Review Briefing on Cloud Computing.
  • For a discussion of problems and concerns about the digital cloud, read: How Secure is Cloud Computing? Security in the Ether Industry Challenges: The Standards Question
Joanne S

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

www.asis.org/...DecJan09_Schneider.html

IMT122 Reading List Week 02 Essential Reading Topic 02 IMT122 Open Source Software

shared by Joanne S on 03 Sep 12 - No Cached
  • 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

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

otherlibrarian.wordpress.com/...ly-data-storage-for-librarians

IMT122 IMT122 Reading List Week 06 Topic 06 Supplementary Reading Databases Libraries

shared by Joanne S on 18 Sep 12 - Cached
  • 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!  
  • Joanne S on 18 Sep 12
     
    How databases are used in libraries
1 - 12 of 12
Showing 20▼ items per page