Socializing the catalogue
=========================
:author: Dan Scott
:copyright: 2011 Laurentian University
:backend: slidy
:data-uri:
:max-width: 45em
:icons:
:duration: 15

This talk is licensed under a http://creativecommons.org/licenses/by-sa/2.5/ca/[Creative Commons, Attribution, Share Alike license].

image::images/cc_by_sa_360.png[]

Slides available from http://bzr.coffeecode.net/opac_talk_2011/

Word association game
---------------------
  * When I say "Catalog", the first thing that comes to mind...
    ** sterile
    ** antiseptic
    ** utilitarian
    ** anti-social
  * Text-heavy, serious interfaces
  * Solitary human interacting with Information

"Added Content" generally utilitarian
-------------------------------------
  * Oriented towards aiding selection and recall tasks
    ** Cover art
    ** Reviews
    ** Excerpts, author bios, tables of content
    ** Tags
  * ... and all read only

Current social features in Evergreen
------------------------------------
  * *+* Lists (aka public bookbags)
    ** *-* List URLs have to be shared manually
    ** *-* Default views are RSS or very plain HTML
    ** *-* Curated only by individuals, no collaborative efforts possible
  * Not much more
  * You have no presence as an Evergreen user

Fall 2010 experiment
--------------------
  * Give users the ability to rate, add reviews, tag records
  * Expose one public page per user (basic opt-in when you act socially)
    ** Nickname
    ** Name (opt-in)
    ** Contact information (all opt-in)
      *** Email address
      *** Other net identities (web site, blog, identi.ca, Twitter, Facebook)
    ** Public lists
    ** Ratings, reviews
    ** Items circulated (opt-in obviously)
  * Exposed via TT-based HTML pages
  * Exposed via Activity Stream Atom extension

User "about" page
-----------------
image::images/Evergreen-about-user.png[]

Activity Stream Atom extension?
-------------------------------
  * Yes - a standard for sharing actions such as:
    ** Posts (tweets, Facebook status, IM status)
    ** Ratings
    ** Reviews
    ** Comments
    ** List actions (creating, adding to, deleting from)
  * Atom extension has been sidelined, JSON version about to hit 1.0
    ** Easy to offer JSON as well as Atom and HTML
  * Standard means it is easy to aggregate into Google Buzz, FriendFeed, RSS feeds, etc
    ** And "easy" to aggregate across Evergreen instances - and any other catalog that uses Activity Streams
    ** "Easy" because we need a truly standard identifier for works; ISBN, OCLCnum, etc don't cut it
    ** OpenLibrary ID to the rescue (for books, anyway)?

Mmm, Activity Streams XML...
----------------------------

[source,xml]
------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<feed gd:kind="buzz#activityFeed" xmlns="http://www.w3.org/2005/Atom" xmlns:activity="http://activitystrea.ms/spec/1.0/" xmlns:buzz="http://schemas.google.com/buzz/2010" xmlns:crosspost="http://purl.org/syndication/cross-posting" xmlns:gd="http://schemas.google.com/g/2005" xmlns:georss="http://www.georss.org/georss" xmlns:media="http://search.yahoo.com/mrss/" xmlns:poco="http://portablecontacts.net/ns/1.0" xmlns:thr="http://purl.org/syndication/thread/1.0">
<link rel="self" type="application/atom+xml" href="https://www.googleapis.com/buzz/v1/activities/116747292129029460979/@public?alt=atom"/>
<link rel="next" href="https://www.googleapis.com/buzz/v1/activities/116747292129029460979/@public?alt=atom&amp;max-results=20&amp;c=CN3ljbD536ECSLPltv3wpaQC"/>
<link rel="hub" href="http://pubsubhubbub.appspot.com/"/>
<title>Google Buzz Public Feed for Dan Scott</title>
<updated>2010-09-20T05:00:01.997Z</updated>
<id>tag:google.com,2010:buzz-feed:public:posted:116747292129029460979</id>
<generator uri="http://www.google.com/buzz">Google Buzz</generator>
<entry gd:kind="buzz#activity">
    <title>Responding to the Evergreen &quot;research&quot; article in Information Technology and Libraries</title>
    <published>2010-09-20T02:25:01.000Z</published>
    <updated>2010-09-20T05:00:01.997Z</updated>
    <id>tag:google.com,2010:buzz:z12nupcwztz3jnva104ccpp5pkvvchnxbkc0k</id>
    <link rel="alternate" type="text/html" href="http://www.google.com/buzz/116747292129029460979/ZRbkbZcXiC6"/>
    <link rel="self" type="application/atom+xml" href="https://www.googleapis.com/buzz/v1/activities/116747292129029460979/@self/B:z12nupcwztz3jnva104ccpp5pkvvchnxbkc0k?alt=atom"/>
    <link rel="replies" type="application/atom+xml" href="https://www.googleapis.com/buzz/v1/activities/116747292129029460979/@self/B:z12nupcwztz3jnva104ccpp5pkvvchnxbkc0k/@comments?alt=atom" thr:count="0" thr:updated="2010-09-20T05:00:01.997Z"/>
    <author>
        <poco:id>116747292129029460979</poco:id>
        <poco:photoUrl>http://www.google.com/s2/photos/public/AIbEiAIAAABECPOn_OPdrpW16AEiC3ZjYXJkX3Bob3RvKig4OGNlNzQ1NGVhMmUwYWU3NWUxMzMxZjNhNmQ4NDVlODYyZDkyY2Y0MAHO16cg1OnXsJEyXV2Zs7368dua0g</poco:photoUrl>
        <name>Dan Scott</name>
        <uri>http://www.google.com/profiles/denials</uri>
        <link rel="photo" type="image/jpeg" href="http://www.google.com/s2/photos/public/AIbEiAIAAABECPOn_OPdrpW16AEiC3ZjYXJkX3Bob3RvKig4OGNlNzQ1NGVhMmUwYWU3NWUxMzMxZjNhNmQ4NDVlODYyZDkyY2Y0MAHO16cg1OnXsJEyXV2Zs7368dua0g"/>
        <activity:object-type>http://activitystrea.ms/schema/1.0/person</activity:object-type>
    </author>
    <content type="html">Responding to the Evergreen &amp;quot;research&amp;quot; article in Information Technology and Libraries</content>
    <activity:verb>http://activitystrea.ms/schema/1.0/post</activity:verb>
    <activity:object>
        <activity:object-type>http://activitystrea.ms/schema/1.0/note</activity:object-type>
        <content type="html">Responding to the Evergreen &amp;quot;research&amp;quot; article in Information Technology and Libraries</content>
        <buzz:original-content type="text"/>
        <link rel="alternate" type="text/html" href="http://www.google.com/buzz/116747292129029460979/ZRbkbZcXiC6"/>
    </activity:object>
    <crosspost:source>
        <id>http://coffeecode.net/archives/234-guid.html</id>
    </crosspost:source>
    <source>
        <activity:service>
        <title>Coffee|Code : Dan Scott</title>
        </activity:service>
    </source>
    <buzz:visibility>
        <buzz:aclentry type="group">
            <poco:id>G:@me:@public</poco:id>
            <uri>https://www.googleapis.com/buzz/v1/people/@me/@groups/G:@me:@public?alt=atom</uri>
            <poco:name>Public</poco:name>
        </buzz:aclentry>
    </buzz:visibility>
    <link rel="http://schemas.google.com/buzz/2010#liked" type="application/poco+xml" href="https://www.googleapis.com/buzz/v1/activities/116747292129029460979/@self/B:z12nupcwztz3jnva104ccpp5pkvvchnxbkc0k/@liked?alt=atom" buzz:count="0"/>
</entry>
</feed>
------------------------------------------------------------------------------


To go forward with socializing Evergreen
----------------------------------------
  * Privacy protection:
    ** Separate user name / user ID from nickname (user ID is exposed publicly for checked-out items, etc, so we need to prevent linking users to borrowing history, even obliquely, without their consent)
    ** Set up regular reminders about any of the opted-in data publishing
  * More interaction:
    ** Build automatic lists of items that have been rated / reviewed / commented
    ** Enable users to follow other users (Atom / JSON outside of a single Evergreen instance)
    ** Enable users to publish their activities on other services (easy for Google Buzz / FriendFeed types - just drop in their link; more programming required for custom APIs like Twitter / Facebook)
    ** Link to recent activities on the catalog home page
  * Development time!

Added content vs. Adding content back
-------------------------------------
  * As of Evergreen 2.0, the default added content provider is OpenLibrary "One page per book"
    ** Currently only pulling cover art and table of contents
    ** Could pull links to ebooks, description, excerpts, first line
      *** *Late-breaking news!*
  * In early discussions with OpenLibrary about their "Write" API:
    ** Manage cover art (some people abuse the system, sigh)
    ** Add / edit description, table of contents, excerpts, first line
    ** Short-term: Simple AJAX calls to invoke the native OpenLibrary interface
    ** Longer-term: Integrate directly into the Evergreen interface (with a fall-back to storing info natively in Evergreen if working with a less-sophisticated added content provider)