Skip to main content

Home/ IMT122 OUA Group/ Group items tagged Topic 07

Rss Feed Group items tagged

Joanne S

Towards a Typology for Portals | Ariadne: Web Magazine for Information Professionals - 0 views

  •  
    PORTALS Miller, P. (2003) "Towards a typology for portals" Ariadne Issue 37. Retrieved from http://www.ariadne.ac.uk/issue37/miller
Joanne S

An Alternative to Existing Library Websites : Evaluation of Nine Start Pages using Crit... - 0 views

  •  
    WEB START PAGES AS LIBRARY HOME PAGES This is long, so just browse it to get the gist of the tools examined and the criteria used. Pigott, C. (2009). An Alternative to Existing Library Websites: Evaluation of Nine Start Pages Using Criteria Extracted from Library Literature. School of Information Management, Victoria University of Wellington. Retrieved from http://researcharchive.vuw.ac.nz//handle/10063/1276
Joanne S

Tag Team Tech April 2011 | VOYA - 0 views

  •  
    SELECTING THE RIGHT TOOL FOR A PORTAL-BASED SUBJECT GUIDE Valenza, J. (2011). My Perpetual Pursuit of the Perfect Pathfinder Platform. VOYA: Voice of Youth Advocates. Retrieved from http://www.voya.com/2011/03/18/tag-team-tech-april-2011/
Joanne S

VALA2012 Session 12 Warren - VALA - 0 views

  •  
    NATIONAL AND STATE LIBRARIES OF AUSTRALASIA'S LIBRARY HACK PROJECT Warren, M., & Hayward, R. (2012). Hacking the nation: Libraryhack and community-created aps. VALA 2012: eM-powering eFutures. Presented at the VALA 2012: eM-powering eFutures, Melbourne Australia: VALA: Libraries, technology and the future. Retrieved from http://www.vala.org.au/vala2012-proceedings/vala2012-session-12-warren
Joanne S

Library Mashups and APIs - 0 views

  •  
    This "L Plate" presentation was presented at the VALA: Libraries, Technologies and the Future Conference in February 2010. The notes underneath each slide explain them very nicely. It gives you an idea of what is considered "L Plate" material at a professional conference. Hagon, P. (2010, February). Library Mashups and APIs. Presented at the VALA 2010 Conference. L Plate Session, Melbourne Australia. Retrieved from http://www.slideshare.net/paulhagon/library-mashups-and-apis
Joanne S

The Machine is Us/ing Us (Final Version) - YouTube - 0 views

  •  
    The Machine is Us/ing Us (Final Version). (2007). . Retrieved from http://www.youtube.com/watch?v=NLlGopyXT_g&feature=youtube_gdata_player
Joanne S

Reprogramming The Museum | museumsandtheweb.com - 0 views

  • 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
  •  
    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
Joanne S

Is the Sky Falling on the Content Industries? by Mark Lemley :: SSRN - 0 views

  •  
    Lemley, M. A. (2011). Is the sky falling on the content industries? Journal of Telecommunications and High Technology Law, 9, 125-313. Retrieved from http://papers.ssrn.com/sol3/papers.cfm?abstract_id=1656485##
1 - 10 of 10
Showing 20 items per page