Skip to main content

Home/ IMT122 OUA Group/ Group items tagged Archives 2.0

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Joanne S

What Is Web 2.0 - O'Reilly Media - 0 views

oreilly.com/...what-is-web-20.html

IMT122 Reading List IMT122 Week 09 Topic 08

shared by Joanne S on 22 Oct 12 - Cached
  • Joanne S on 22 Oct 12
     
    O'Reilly, T. (2005, September 30). What Is Web 2.0 - O'Reilly Media. Retrieved September 10, 2010, from http://oreilly.com/web2/archive/what-is-web-20.html To discover how Tim O'Reilly originally conceptualised Web 2.0, please read the following explanation. Do not worry too much about understanding every web tool mentioned or all the technical processes. Do pay particular attention to the discussion of RSS on page 3 and the different ways that users relate to the web in this vision.
Joanne S

Archives 2.0? | ArchivesNext - 0 views

www.archivesnext.com/?p=203

IMT122 IMT122 Reading List Week 09 Topic 08 Archives 2.0 Archives

shared by Joanne S on 22 Oct 12 - No Cached
  • Do we need Archives 2.0? Clearly, yes, I think we do.
Joanne S

Library 2.0 and User-Generated Content What can the users do for us? - 0 views

archive.ifla.org/...113-Danowski-en.pdf

IMT122 Reading List IMT122 Week 10 Topic 09 Essential Reading library2.0

shared by Joanne S on 22 Oct 12 - No Cached
  • Joanne S on 22 Oct 12
     
    Danowski, P. (2007). Library 2.0 and User-Generated Content What can the users do for us? In World Library and Information Congress: 73rd IFLA General Conference and Council. Durban, South Africa: IFLA. Retrieved from http://archive.ifla.org/IV/ifla73/papers/113-Danowski-en.pdf
Joanne S

blyberg.net » Blog Archive » 11 reasons why Library 2.0 exists and matters - 0 views

www.blyberg.net/...-library-20-exists-and-matters

IMT122 Reading List IMT122 Week 09 Topic 08 Supplementary Reading library2.0

shared by Joanne S on 22 Oct 12 - Cached
  • Joanne S on 22 Oct 12
     
    Blyberg, J. (2006, September 1). 11 reasons why Library 2.0 exists and matters. blyberg.net. Retrieved September 14, 2010, from http://www.blyberg.net/2006/01/09/11-reasons-why-library-20-exists-and-matters/
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
1 - 5 of 5
Showing 20▼ items per page