<?xml version="1.0"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:dc="http://purl.org/dc/elements/1.1/"
         xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
         xmlns="http://purl.org/rss/1.0/">
<channel rdf:about="http://rhaptos.org/devblog/kef">

    <title>Rhaptos Software Development - Kathi's Blog</title>
  <link>http://rhaptos.org</link>
  <description></description>
  <image rdf:resource="logo.jpg"/>
  <sy:updatePeriod>daily</sy:updatePeriod>
  <sy:updateFrequency>1</sy:updateFrequency>
  <sy:updateBase>2006-08-14T23:33:43Z</sy:updateBase>
  <items>
    <rdf:Seq>
        
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/search_results"/>
          
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/upa-rhyne"/>
          
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/upa-breadcrumbs"/>
          
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/js-research"/>
          
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/js-web20"/>
          
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/js-organizations"/>
          
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/js-training"/>
          
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/js-designsmall"/>
          
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/collectiontypes"/>
          
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/citeuliketoc"/>
          
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/roundtable"/>
          
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/lensblog"/>
          
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/kef%20mockup%20test"/>
          
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/fullnamebehavior"/>
          
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/subject_categories"/>
          
          
              <rdf:li resource="http://rhaptos.org/devblog/kef/EducationPress"/>
          
        
   </rdf:Seq>
  </items>
</channel>


<item rdf:about="http://rhaptos.org/devblog/kef/search_results">
<title>Search results tips from Jarod Spool -- (more scent, most relevant first, no pogosticking, no wacko results, more result per page)</title>
<link>http://rhaptos.org/devblog/kef/search_results</link>
<description>&lt;p&gt;Jared Spool's article, &lt;a href="http://www.uie.com/articles/search_results_part2"&gt;http://www.uie.com/articles/search_results_part2/&lt;/a&gt;, has some interesting results from researching various companies' search results pages. &lt;/p&gt;


&lt;ol&gt;&lt;li&gt;
&lt;strong&gt;Provide a lot of info&lt;/strong&gt; in the results to support user tasks. He gives the example of price, distance, and room amenities for hotel searches, to support various types of customers. For us, I think that means providing axes of information about the content in the initial results page, which we do fairly well. At some point, including lens information, ratings and reviews will probably be important. 
&lt;/li&gt;
&lt;li&gt;

&lt;strong&gt;No one ever complains that the page has too many results&lt;/strong&gt; -- 10 per page can be limiting, but I think right now performance issues force us to limit the UI. 
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Most relevant results should be first.&lt;/strong&gt; Well that is obvious. But the interesting result is that people stop searching down if irrelevant results appear (relevancy threshhold). As we get textbook searchers, we really need to reconsider how often modules are obscuring collection results that may be more relevant to the searcher.
&lt;/li&gt;
&lt;li&gt;

&lt;strong&gt;Eliminate wacko results. &lt;/strong&gt;Just thought the psychology here was interesting. Programmers see wacko results as a weird corner case of an algorithm, but searchers see them like Tourette's syndrom (Spool's term) -- random results inserted into an otherwise sane response -- and it makes them not trust the other results. 
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Prevent pogosticking &lt;/strong&gt;-- The more times someone goes to look at content and comes back to the search results (which Spool calls pogosticking), the less likely they are to ultimately find what they want. (I think that this would be a good stats problem for our new book -- probability of success given Y pogos) Preventing this is related to the "Provide a good scent in the initial display). 
&lt;/li&gt;
&lt;/ol&gt;</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2008-07-15T13:09+00:00</dc:date>
</item>


<item rdf:about="http://rhaptos.org/devblog/kef/upa-rhyne">
<title>Consistency without becoming a hobgoblin</title>
<link>http://rhaptos.org/devblog/kef/upa-rhyne</link>
<description>&lt;p&gt;Rob Rhyne (UPA-DC 2007)&lt;/p&gt;
&lt;p&gt;Rhyne&amp;rsquo;s talk was about using common design patterns and  everyday metaphors to achieve consistent and usable interfaces without  demanding strict uniformity. He says uniformity is problematic if it is being  invoked to justify a design that is one of the following:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;easier to build but is actually  less useful, &lt;/li&gt;
  &lt;li&gt;a substitute for a more useful creative solution, or &lt;/li&gt;
  &lt;li&gt;when it simply results  in something that is boring and undistinguished. &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;He showed Google search  results, Yahoo search results, and Microsoft Live search results and without  the header these look nearly identical, but the two catch up searches really  need &amp;nbsp;to distinguish themselves visually without  breaking the understandability. Conventions can be broken when they are  immediately obvious. He cited successful examples that broke away from conventions:  the iPhone interface and a CD burner called disco that uses drifting smoke on  the desktop to indicate that it is still working while allowing the user to do  other stuff. &lt;/p&gt;
&lt;p&gt;An audience member working for a medical site told a story  about trying to develop websites of information for diabetics and for breast  cancer survivors. The pointy haired bosses (ooh that&amp;rsquo;s me) wanted uniformity,  but these two communities are actually very different in how they approach  finding information (no details given unfortunately). I retell that story,  because I think it has some parallels with our communities of authors and  readers. The Connexions stylesheets were the first design for allowing  communities to relate to content as communities. The stylesheets controlled the  entire look and feel of the navigation, content, CNX and branding which turned  out to be very hard to understand for readers, and difficult to maintain for  development. We are now moving toward supporting styling in the content area,  but preserving CNX navigation. We plan to provide style parameters that can be  applied by module authors, collection authors, lens makers, and readers (in  that order). Will that be enough? And will it really be easier to maintain? &lt;/p&gt;
&lt;strong&gt;Rhyne gave a couple of suggested references:&lt;/strong&gt;
&lt;ul&gt;&lt;li&gt;Yahoo! Pattern Library&lt;br /&gt;
    &lt;a href="http://developer.yahoo.com/ypatterns"&gt;http://developer.yahoo.com/ypatterns&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;&amp;ldquo;Web Patterns&amp;rdquo;, John Allsopp&lt;br /&gt;
    &lt;a href="http://westciv.typepad.com/dog_or_higher/2005/11/webpattenrs_and.html"&gt;http://westciv.typepad.com/dog_or_higher/2005/11/webpattenrs_and.html&lt;/a&gt;&lt;/li&gt;
  &lt;li&gt;Flickr Design Pattern Photo pool&lt;/li&gt;
&lt;/ul&gt;
</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-11-06T22:40+00:00</dc:date>
</item>


<item rdf:about="http://rhaptos.org/devblog/kef/upa-breadcrumbs">
<title>Breadcrumbs : Finding related information</title>
<link>http://rhaptos.org/devblog/kef/upa-breadcrumbs</link>
<description>&lt;p&gt;I heard a brief talk by Angela Colter (UPA-DC 2007) on a  study of breadcrumb usage. The researchers wanted to know how people think of  them, and how they use them. &lt;/p&gt;
&lt;p&gt;Three types of breadcrumbs: &lt;/p&gt;
&lt;ol&gt;
  &lt;li&gt;&lt;strong&gt;Location model&lt;/strong&gt; &amp;ndash; single breadcrumb path to any resource&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Path model&lt;/strong&gt; &amp;ndash; shows exactly how this user got to the page&lt;/li&gt;
  &lt;li&gt;&lt;strong&gt;Attribute model&lt;/strong&gt; --&amp;nbsp;  gives metadata information (categories, subcategories) &amp;ndash; this model is  used by Amazon and results in multiple breadcrumbs paths showing on a single  page.&lt;/li&gt;
  
&lt;/ol&gt;
&lt;p&gt;Results: &lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt; Users describe breadcrumbs as paths, but think of them as  locations. &lt;/li&gt;
  &lt;li&gt;Novice users are very likely to use them, and understand they are  links. &lt;/li&gt;
  &lt;li&gt;Most commonly used to find something related. While heading  back to the search box the user trips over the breadcrumbs and see that something in the breadcrumb trail might be  useful. &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Breadcrumb problems:&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;If the breadcrumb link label is named something  different than the page you get to that is a problem and users never use the  crumbs again if that happens to them. (In this study)&lt;/li&gt;
&lt;/ul&gt;
</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-11-05T10:36+00:00</dc:date>
</item>


<item rdf:about="http://rhaptos.org/devblog/kef/js-research">
<title>Web 2.0 usability issues and open questions</title>
<link>http://rhaptos.org/devblog/kef/js-research</link>
<description>
&lt;p&gt;From Jared Spool at UPA-DC-2007 again: These are the things that his  company is actively researching &amp;ndash; the unsolved problems of Web 2.0 usability.&lt;/p&gt;
&lt;ul&gt;
  &lt;li&gt;What does it mean to produce a usable API?&lt;/li&gt;
  &lt;li&gt;RSS &amp;ndash; When chronologically isn&amp;rsquo;t the right organization,  what then?&lt;/li&gt;
  &lt;li&gt;Tagging &amp;ndash; How do you unify things that are intended to be the same,  but aren&amp;rsquo;t such as misspellings and alternates (NY, NYC, New York etc.)? &amp;nbsp;The big search engines have made headway in  this area somewhat. &lt;/li&gt;
  &lt;li&gt;Quality: What is the role for the editorial with regard to  user-generated content and how to support that role?&lt;br /&gt;
    &lt;br /&gt;
  This quality question is exactly the same  question that Connexions is asking and trying to answer with lenses. The  corresponding business question is how do we support an economy of editors  while preserving open content? Related to the quality of content is the quality  of tagging. Audience members brought up the need for expert generated ontologies  and subject vocabularies in addition to  completely user generated tags.&lt;/li&gt;
  &lt;li&gt;Social networking -- How to avoid mobs?&lt;/li&gt;
&lt;/ul&gt;
</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-10-24T20:49+00:00</dc:date>
</item>


<item rdf:about="http://rhaptos.org/devblog/kef/js-web20">
<title>Web 2.0 is ...</title>
<link>http://rhaptos.org/devblog/kef/js-web20</link>
<description>Jared Spool gave the following definition of Web 2.0:&lt;br /&gt;
  1. API's -- the ability to get the data without going through  the UI&lt;br /&gt;
  2. RSS &lt;br /&gt;
  3. Folksonomies and tagging&lt;br /&gt;
  4. Social networking&lt;br /&gt;
or is it just "marketing hype"?</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-10-17T21:05+00:00</dc:date>
</item>


<item rdf:about="http://rhaptos.org/devblog/kef/js-organizations">
<title>Jared Spool on Good Organizations</title>
<link>http://rhaptos.org/devblog/kef/js-organizations</link>
<description>Jared Spool gave a very quick rundown of things he thought  were required of good organizations. By implication such organizations are more likely to get the user experience done well also.</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-10-17T07:48+00:00</dc:date>
</item>


<item rdf:about="http://rhaptos.org/devblog/kef/js-training">
<title>Good user design is like chicken sexing and sushi making</title>
<link>http://rhaptos.org/devblog/kef/js-training</link>
<description>Jared Spool talks about design, the Wall Street Journal, chicken sexing, and sushi-making. </description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-10-15T19:36+00:00</dc:date>
</item>


<item rdf:about="http://rhaptos.org/devblog/kef/js-designsmall">
<title>Design well, design small, and keep the business needs in  mind.</title>
<link>http://rhaptos.org/devblog/kef/js-designsmall</link>
<description>Jared Spool on design at UPA-DC 2007</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-10-15T09:01+00:00</dc:date>
</item>


<item rdf:about="http://rhaptos.org/devblog/kef/collectiontypes">
<title>Collection Types to Support</title>
<link>http://rhaptos.org/devblog/kef/collectiontypes</link>
<description>We are now supporting course and report as collection types. Kyle is building an interface to enter them when creating collections and so we need to decide what collection types to support. The blog entry discusses bibtex types and others that have occurred in our practice. </description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-06-21T13:40+00:00</dc:date>
</item>


<item rdf:about="http://rhaptos.org/devblog/kef/citeuliketoc">
<title>Publishing Connexions Collections in CiteULike.</title>
<link>http://rhaptos.org/devblog/kef/citeuliketoc</link>
<description>CiteULike is publishing Journal TOC's and then letting people link to the articles. Should Connexions do that with collections?
</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-06-21T13:33+00:00</dc:date>
</item>


<item rdf:about="http://rhaptos.org/devblog/kef/roundtable">
<title>Author Roundtable June 07</title>
<link>http://rhaptos.org/devblog/kef/roundtable</link>
<description>I uploaded Sebastian's notes on the author round table from Tuesday, June 05. They are under User Interface/User Testing.
http://rhaptos.org/ui/ut/roundtablejune07</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-06-07T23:18+00:00</dc:date>
</item>


<item rdf:about="http://rhaptos.org/devblog/kef/lensblog">
<title>Lens Functional Design Draft</title>
<link>http://rhaptos.org/devblog/kef/lensblog</link>
<description>I have uploaded the lens functional design draft and a proposed version 1 implementation for July. Cameron Cooper will be producing an architectural design for the implmentation shortly. Comments are welcome.

All the documents are available in http://rhaptos.org/architecture/lenses/. 

</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-06-05T22:41+00:00</dc:date>
</item>


<item rdf:about="http://rhaptos.org/devblog/kef/kef%20mockup%20test">
<title>Testing the new home page mockups</title>
<link>http://rhaptos.org/devblog/kef/kef%20mockup%20test</link>
<description>Kathi had family test three mockups for the new homepage using questions that Manpreet devised. I transcribed what they said and did. When the first person is used, I am quoting them.</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2007-01-23T10:20+00:00</dc:date>
</item>


<item rdf:about="http://rhaptos.org/devblog/kef/fullnamebehavior">
<title>Full Name Behavior</title>
<link>http://rhaptos.org/devblog/kef/fullnamebehavior</link>
<description></description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2006-12-22T13:31+00:00</dc:date>
</item>


<item rdf:about="http://rhaptos.org/devblog/kef/subject_categories">
<title>Other Subject Categories</title>
<link>http://rhaptos.org/devblog/kef/subject_categories</link>
<description>We currently use the 6 subject categories from OER Commons. Here is one from CiteULike: Computer Science  | Biological Science  | Social Science  | Medicine  | Engineering  | Economics/Business  | Arts/Humanities  | Mathematics  | Physics  | Chemistry  | Philosophy  | Earth/Environmental Science

Dare we broach a deeper subject category?</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2005-04-06T21:34+00:00</dc:date>
</item>


<item rdf:about="http://rhaptos.org/devblog/kef/EducationPress">
<title>Education and CNX Related Press Articles</title>
<link>http://rhaptos.org/devblog/kef/EducationPress</link>
<description>Google scrapbooks for education press and Connexions press.</description>
<dc:publisher>No publisher</dc:publisher>
<dc:creator>kef</dc:creator>
<dc:rights></dc:rights>
<dc:date>2006-12-06T17:59+00:00</dc:date>
</item>


</rdf:RDF>



