<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
    <channel>
        <title>Binky&apos;s Blog</title>
        <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/</link>
        <description></description>
        <language>en-us</language>
        <copyright>Copyright 2008</copyright>
        <lastBuildDate>Tue, 17 Jun 2008 09:05:09 -0500</lastBuildDate>
        <generator>http://www.sixapart.com/movabletype/</generator>
        <docs>http://www.rssboard.org/rss-specification</docs>
        
        <item>
            <title>SNRG 2009 Cool and creative ways for small libraries to promote their OPACs</title>
            <description><![CDATA[<p>Tracey Amey</p>
<p><strong>How do we bring the users to&nbsp;our catalog?</strong></p>
<p><strong>Custom Search URLs<br /></strong>Custom search url is a url that you construct to make a link into an on the fly search for a specific item type, category, keyword. These are all live urls, so thy are automatically updated. This becomes a seamless link into the OPAC. You don't need to update them again. &nbsp;One example is for the titles they have on cd at summer break time. Another example is for their popular collection or leisure reading&nbsp; - they use the list and bring in book covers for a more visual list. </p>
<p>Highlighting a display on the home page with a link to the item catgory display within the catalog. Students don't even know they are being sent into the catalog. </p>
<p>Bibliography<br />Custom search string includes the following: &amp;item_2cat=GAMES_IND.&nbsp;&nbsp;The advantage is that it's aways live and always current and the url can be sent to faculty, students, etc at a momen't notice.</p>
<p>Periodicals by curriculum. <br />This was created by using the fund&nbsp;code in the local notes field 594.&nbsp; <br />Base url plus ?searchdata1=LS{T594} </p>
<p>custom search string includes the following: &amp;item_2cat=GAMES_IND</p>
<p>Lots of information for creating these comes from the Sirsi Customer wiki</p>
<p>There is a check box to have people search ebooks only. When they implemented this, their stats for e-books went&nbsp;up 33% after this was turned on.&nbsp; sys.env file under the electronic book configuration area.</p>
<p>&nbsp;</p>
<p><strong>How do we bring the catalog to them?</strong></p>
<p>iGoogle, Amazon, IMDb, CMS, Blogs<br />widgets for iGoogle that also work in Angel</p>
<p>Amazon.com library look up - works in firefox only right now.&nbsp; The script was modified from the LION Library Lookup Script at userscripts.org.</p>
<p>IMDb - there is a script that lets people know that the library has this dvd.Adapted from an existing script.</p>
<p>Trixie - same as greasemonkey for Firefox. Helps with migratin scripts to work on IE as well as Firefox.&nbsp; </p>
<p>Yahoo Pipes - </p>
<p>Dapper lets you take a url&nbsp;and make an RSS.&nbsp; Choose the content you want to feed. (Tracy chose Title call# and availability). Use the dapper-created rss feed as your source in yahoo pipes. Use pipe as is. Peoplpe can add to their iGoogle or feedreader. Creates badge to embed in website or blog, etc. You can clone a feed that works and change it to use your own url.&nbsp; For promoting these tools, Madigan has a page called cool tools. This is where all gadgets and instructions for downloading. </p>
<p>&nbsp;</p>
<p>Promotional posting on portal, emails with gadgets and custom urls.&nbsp; Talking about them in sessions, classes, users has really promoted them.&nbsp; </p>
<p><strong>Tools used:</strong></p>
<p>Flickr - to embed images into email<br />iGoogle gadget<br />Greasemonkey - to use scripts in Firefox<br />Userscripts.org<br />Yahoo pipes - interactive feed aggregator<br />Dapper - the data mapper<br />Trixie for IE7<br /></p>
<p>Try it - you can't break anything. Experiment and see what you can do!</p>
<p>Great presentation!</p>
<p><a href="mailto:tamey@pct.edu">tamey@pct.edu</a></p>
<p>&nbsp;</p>
<p>eres?<br /></p>
<p><br />&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>]]></description>
            <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/06/snrg-2009-cool-and-creative-wa.html</link>
            <guid>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/06/snrg-2009-cool-and-creative-wa.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">snrg08</category>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">libraries</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">sirsi</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">snrg2008</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">web2.0</category>
            
            <pubDate>Tue, 17 Jun 2008 09:05:09 -0500</pubDate>
			
			



        </item>
        
        <item>
            <title>SNRG 2009  - Sirsi Dynix User Experience Roadmap</title>
            <description><![CDATA[<p><strong>Enterprise 1.0</strong></p>
<ul>
<li>enhancement to OPAC (not a reivention of OPAC)</li>
<li>immediate and intuitive faceted search experience</li>
<li>built in fuzzy search logic</li>
<li>easy to manage and configure</li>
<li>responsive and reliable</li>
<li>cost advantage over faceted search competitors</li>
<li>light integration with existing environments</li>
<li>search index updates based on changes rather than complete nightly dump</li>
<li>enhanced enriched content support</li>
<li>consortia support<br />&nbsp;- library or library group search limits<br />&nbsp;- ip address ranges<br />&nbsp;- did you mean concept</li>
<li>enetrprise 1.0 Q3/Q4 2008</li></ul>
<p>&nbsp;</p>
<p><strong>E- Library</strong> </p>
<ul>
<li>replacement for iBistro and iLink</li>
<li>NO COST</li>
<li>patch upgrade after you get to 3.2.1</li>
<li>no training required</li>
<li>enterprise can sit on e-library 3.2.1</li>
<li>look and feel to match enterprise</li>
<li>enhance enriched content support (cannot get this w/iLink)</li>
<li>online bill payment</li>
<li>ezproxy integration</li>
<li>3.2 highlights<br />&nbsp;- renewals from review my account</li></ul>
<p>Enterprise is a subscription plus product delivery cost and project managment fees. There will be optional Enterprise training.</p>
<p><strong><u>iLink Customers:</u></strong></p>
<p><strong>Option 1:</strong></p>
<p>ibistro/ilink running 3.1 or higher, you can run enterprise on top </p>
<p><strong>Option 2</strong>:</p>
<p>move to e-library with 3.2.1 and then enterprise on top</p>
<p>&nbsp;</p>
<p><strong>New Enriched Content Support</strong></p>
<p>Reviews, fiction profiles, find similar titles, additional subscription - expensive. If you buy it by Aug 15, 25% discount - but you must be moved into e-library already</p>
<p><strong>Goals for Enterprise 3.0</strong></p>
<ul>
<li>integration of additional data sources - federated search, library favorites</li>
<li>guided discovery</li>
<li>rss, tagging, user reviews, ratings</li>
<li>third party interfaces (fed search and resolver support)</li>
<li>visual search - may partner with another vendor</li>
<li>when asked about pricing - the response was that it's less than aquabrowser&nbsp;</li>
<li>partnership with brainware</li></ul>
<p><strong>Demo</strong></p>
<p>Kate demoed enterprise starting with "bud not buddy". The initial search screen is just like google - one search box. Enterprise brought up the correct record as the first hit with facets on the right for narrowing your search. Second search was Tchaikowsky spelled incorrectly - but found the results automatically. The facets are designed to me intuitive and easy.&nbsp; You can go to your account directly from home search page - single log in.&nbsp;Stop words and boolean logic do not exist. This is not a replacement for the OPAC - it is designed for your typical patron who wants what they want quickly. For advanced searching,&nbsp;patrons will still be using the regular catalog (which will be e-library).</p>
<p>Sirsi Dynix is planning to have demos available from client care area so customers will have the chnce to play with this new interface.</p>
<p><strong>Admin Interface<br /></strong>Simple admin interface. There is ability to set up search groups for multiple libraries. Customize page elements and themes for groups, banner info, library logo. Ability to manage library content. &nbsp;</p>
<p>Single sign on with EZ Proxy: ez proxy can send back the user id and password (encrypted) which will support the login to the opac. So it really doesn't matter where&nbsp;user starts,&nbsp;they are only challenged to authenticate once.&nbsp;&nbsp;&nbsp;</p>
<p>&nbsp;</p>
<p>Ann Snowman asked a great question - how do you display the OPAC AND Enterprise to the users? Which is the default? Do you have one default from Library machines and one for remote access?&nbsp; You can put an Enterprise search box anywhere...</p>
<p>&nbsp;</p>]]></description>
            <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/06/snrg-2009-sirsi-dynix-user-exp.html</link>
            <guid>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/06/snrg-2009-sirsi-dynix-user-exp.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">snrg08</category>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">libraries</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">sirsi</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">snrg2008</category>
            
            <pubDate>Mon, 16 Jun 2008 16:02:10 -0500</pubDate>
			
			



        </item>
        
        <item>
            <title>SNRG 2009 - Sugar Coated Serials - Vermont State Colleges</title>
            <description><![CDATA[<p><strong>Serials Display:</strong></p>
<p>We need to ask ourselves:</p>
<p>What information do patrons want to see?<br />What info do reference librarians want to see?<br />What info do circ and ill staff need to see?</p>
<p>No one liked serial holdings displays - they were confusing and difficult to interpret, and not arranged in an easily interpreted sequence.&nbsp; Because the group is&nbsp;a consortium of 4 colleges, they needed to speak a common language and use a common style. Numbering system and notes were standardized. They checked with reference librarians and confirmed that this would work. The group showed examples of their collaborative decisions.</p>
<p>I won the door prize - pancake mix and Vermont maple syrup!</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>]]></description>
            <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/06/snrg-2009-sugar-coated-serials.html</link>
            <guid>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/06/snrg-2009-sugar-coated-serials.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">snrg08</category>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">libraries</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">sirsi</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">snrg2008</category>
            
            <pubDate>Mon, 16 Jun 2008 13:17:51 -0500</pubDate>
			
			



        </item>
        
        <item>
            <title>SNRG 2009 - Tina Hertel, Lehigh University</title>
            <description><![CDATA[<p>Technology is becoming more portable and&nbsp;smaller. Jump drives with files AND portable applications.&nbsp; Ms Hertel showed iGoogle, pageflakes and netvibes. Pageflakes and netvibes pages can be shared, which iGoogle does not allow. Netvibes allows you to create groups whic makes it most useful.&nbsp; In netvibes, you have the option of making things public or private, so you can hide certain tabs if you are sharing your page. </p>
<p>Diigo is like "delicious on steroids". You can make lists and&nbsp;highlight parts of page and bookmark them, as well as&nbsp;comment on the bookmark. Anything&nbsp;you add to diigo automatically gets added to delicious and magnolia -&nbsp;this is something you set in your preferences or settings.&nbsp; Diigo creates&nbsp;webslides as well. I'll have to give it a try!&nbsp;&nbsp;</p>]]></description>
            <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/06/snrg-2009-tina-hertel-lehigh-u.html</link>
            <guid>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/06/snrg-2009-tina-hertel-lehigh-u.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">snrg08</category>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">libraries</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">sirsi</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">snrg2008</category>
            
            <pubDate>Mon, 16 Jun 2008 11:06:47 -0500</pubDate>
			
			



        </item>
        
        <item>
            <title>Day Summit - Support 5/29/08</title>
            <description><![CDATA[Bob Kelton, Executive Sponsor<br />Day Support<br /><br /><br />Support Tiers<br />1. basic issues - trained key users will provide support<br />2. disfficult issues - support team - daycare<br />3. product issues - R&amp;D <br /><br />Support Improvements<br /><ul><li>executive sponsor</li><li>improvement iniative for daycare</li></ul><br />Eren Aydin<br />North American Support Lead<br />eren.aydin@day.com<br /><br />dev.day.com/kb<br /><br /><br /><ul><li>tripled support agents</li><li>top quality resources</li><li>dedicated support lead</li></ul><br /> ]]></description>
            <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/day-summit-support-52908.html</link>
            <guid>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/day-summit-support-52908.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Day Communique</category>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">cms</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">day</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">daysummit508</category>
            
            <pubDate>Thu, 29 May 2008 12:09:00 -0500</pubDate>
			
			



        </item>
        
        <item>
            <title>Day Summit - Social Networking 5/29/08</title>
            <description><![CDATA[Lars Treiloff<br /><br />Social Networking Features<br />activity feed - allows you to track what happens on social network (friend feed)<br /><br />Collaborative Features<br />Blogging<br />Calendaring<br />forums and discussions (digg)<br />chat rooms -&nbsp; meebo<br />image uploads<br />video uploads<br />private messages<br />favorites and appreciation<br />tagging<br /><br />Day collab will add above features to add value to content<br /><br />upcoming features<br />application platform - facebook, bebo<br />internetwork connections - connect social netowrks<br /><br /><br />widgets - <br /><br />Social networks -<br />intensify and enhance user generated content<br />visitor loyalty<br />new visitors though 3rd oarty network integration<br />increase page views<br />40% of mobile traffic is to social networks<br />reduce spam and abuse thru online reputation magmt<br /><br />behind firewall...<br />collab techniques can help:<br />
<ul>
<li>across org chart</li>
<li>org chart does not reflect social reality</li>
<li>ad-hoc networking</li>
<li>across&nbsp; depts</li>
<li>younger generation joining the workforce</li></ul>Dont: build standalone socialnetwork - do: leverage existing<br />Dont: create viral only apps&nbsp;&nbsp; do: make apps social<br />Dont: require extensie data from users - do: leverage existing content<br />Dont: lock in users and content - do: encourage mashups and apis<br /><br />bad social apps have no api<br />mediocre social apps add api later<br />good social apps have complete api<br />superb social apps are buil on top of their own api<br /><br />apps using twitter for customer data<br /><br />DAM<br />image and video upload file sharing and conversion<br />Advanced collab<br />blogs, wikis calendaring<br />CQ5 WCM<br />widgets, open social apps (internetwork connectivity), sling<br />photo, slideshow,<br />CQ5 Social Collab<br />Advanced collab and social networking capabilities<br />]]></description>
            <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/day-summit-social-networking-5.html</link>
            <guid>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/day-summit-social-networking-5.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Day Communique</category>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">cms</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">day</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">daysummit508</category>
            
            <pubDate>Thu, 29 May 2008 11:24:16 -0500</pubDate>
			
			



        </item>
        
        <item>
            <title>Day Summit - Enterprise 2.0 - the New ECM  5/29/08</title>
            <description><![CDATA[Web 2.0<br /><ul><li>user centered</li><li>open agile based on standards</li><li>simple and lightweight</li><li>decentralized, distributed and participatory</li></ul>web 1.0 created by scientists - <br />web 2.0 created by society<br /><br />Rich User Experience<br />Web as a platform<br />Content is the Intel Inside<br /><ul><li>edmunds - content is king, info becomes the key, not the infrastructure</li><li>syndicate don't dictate</li><li>standardize - software apis are no longer a lock-in point</li></ul>Architecture of Participation<br /><ul><li>emusic</li><li>force of many - harnessing the power of users, info gets better and grows the more people that use it...</li></ul>Software above a single device<br /><ul><li>pushing to devices<br /></li></ul>Lightweight Business Models<br /><ul><li>web 2.0 wcm is almost recession proof - good economic times, expanding business, in bad times, use web to reach different markets</li></ul>End of Software Upgrade Cycle<br /><ul><li>continual innovation - always updating (launch and iterate) - with cq - release of discrete sets of functionality (OU flash component)<br /></li><li>Operations must become core competency - availablility, load balancing, caching</li></ul><br />Day's Enterprise 2.0 Products<br /><ul><li>CRX JCR Repository - basis of everything they do (JSR 170/283 API)<br /></li><ul><li>jackrabbit/jcr connectors</li></ul><li>CQ WCM - CQ DAM - CQ Social Collab</li></ul>Freedom within a Framework<br /><ul><li>wcm, dam, social collab on a global scale</li><li>global brand management</li><li>productivity</li></ul>Content where it lives<br /><ul><li>flexible content integration</li><li>jcr standard and secure</li></ul>Integrated and agile<br /><ul><li>industry leading products and platforms</li><li>Day will not force being locked in</li></ul>CQ DAM<br />Innovative AJAX interface<br /><ul><li>starts with simple search box</li></ul>CQ Social Collab<br /><ul><li>blog</li><li>wiki - versioning search<br /></li><li>CQ Social Collab Calendar</li><li><br /></li></ul><br /><br /> ]]></description>
            <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/day-summit-enterprise-20-the-n.html</link>
            <guid>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/day-summit-enterprise-20-the-n.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Day Communique</category>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">cms</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">day</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">daysummit508</category>
            
            <pubDate>Thu, 29 May 2008 10:10:38 -0500</pubDate>
			
			



        </item>
        
        <item>
            <title>Day Tech Summit - Kodak Gallery 5/28/08</title>
            <description><![CDATA[An atypical&nbsp; but effective implementation of cq<br />Damon Brennen<br /><br />Challenges<br />
<ul>
<li>CQ installed, but not fully implemented</li>
<li>Project Team Turnover</li>
<li>Mgmt on to the next new thing</li></ul>
<p>How we overcame those challenges</p>
<ul>
<li>babysteps</li></ul>
<p>Timeline</p>
<ul>
<li>pilot</li>
<li>procrastinator campaign</li>
<li>full campaign with cms</li>
<li>90% of bc slots managed by Day (small changes, few new pages)</li>
<li>extended biz users</li>
<li>business as usual end of rollout</li></ul>
<p>Published over 900 slots</p>
<ul>
<li>all us</li>
<li>target</li>
<li>canada</li>
<li>eu</li>
<li>easyshare software</li>
<li>all avail meta slots</li>
<li>all advertising/headers and meta slots</li></ul>
<p>&nbsp;</p>
<p>Marketing</p>
<ul>
<li>workflow removed bottleneck</li>
<li>reduced publishing promo speed</li>
<li>test, update, site content landing pages - ability to "play around"</li>
<li>eu stays in sync with us</li></ul>
<p>Choose a template based on slot size</p>
<p>create a page with slot id</p>
<p>&nbsp;</p>
<p>Strengths</p>
<ul>
<li>easy to use</li>
<li>easy to maintain</li>
<li>small project team</li></ul>
<p>&nbsp;</p>]]></description>
            <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/day-tech-summit-kodak-gallery.html</link>
            <guid>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/day-tech-summit-kodak-gallery.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Day Communique</category>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">cms</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">day</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">daysummit508</category>
            
            <pubDate>Wed, 28 May 2008 16:36:39 -0500</pubDate>
			
			



        </item>
        
        <item>
            <title>Day Tech Summit - Supercharging Search 5/28/08</title>
            <description><![CDATA[Patrick Kent - F5 Knowledge Base<br /><br />Requiremenst<br /><ul><li>-stemming</li><li>ranking</li><li>synonyms</li><li>restrict by document type</li><li>preserve product databse mappings</li><li>search documents by release date</li></ul><br />Driven by Lucene<br /><br />Day had to write a custom interpretor between jcr and xpath that talks to lucene<br /><br />Lucene's "Tricks"<br />Stemming -finds derivatives of the wors. Lucene on the fly finds the root text of the word and searches<br />Fuzzy Search -<br />Synonyms -&nbsp; searches synonymns via word net - but cannot map multi-word synonymns.&nbsp; F5 implemented google style suggestion<br /><br /><br />Tweaking crx search config<br />workspace.xml<br /><br /><br /><br />&nbsp;<br /><br /> ]]></description>
            <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/day-tech-summit-supercharging.html</link>
            <guid>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/day-tech-summit-supercharging.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Day Communique</category>
            
            
            <pubDate>Wed, 28 May 2008 15:29:50 -0500</pubDate>
			
			



        </item>
        
        <item>
            <title>Global Web Deployment - Infiniti</title>
            <description><![CDATA[The Designory - Judy Tantana<br /><br />launched infinit brand worldwide<br /><br />usability for authors<br />-use cases <br />-test tasks<br />- survey<br /><br />cq launch<br />organization<br />
<ul>
<li>structure and operating guidelines for each region</li>
<li>clear distinction between global and regional control</li></ul>Benefits<br />
<ul>
<li>regions will provide their knowedge back into the system for use by other regions for system improvement</li>
<li>centralized development of infrastructure</li>
<ul>
<li>allows all regions to have same baseline and capabilities</li>
<li>leverages global efforts across regiomms</li>
<li>less disparity between regions</li></ul></ul><br />First countries launched - China and Russia<br />
<ul>
<li>2 most difficult countries - character sets and content regulations</li>
<li>started small and grew, knowing&nbsp; they'd have to go back and work infrastructure and development</li></ul>Design -<br />
<ul>
<li>based on us version</li>
<li>business-user friendly</li>
<li>recent us design and creative</li>
<li>provide as much as possible for users/authors</li></ul>Business<br />
<ul>
<li>per country cost reduced (support, maintenance and infrastructure)</li>
<li>enhancements benefit all countries</li>
<li>brand consistency</li>
<li>standardized reporting</li></ul>Technical<br />
<ul>
<li>flash based editing</li></ul>
<p><br /></p>]]></description>
            <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/global-web-deployment-infiniti.html</link>
            <guid>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/global-web-deployment-infiniti.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Day Communique</category>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">cms</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">day</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">daysummit508</category>
            
            <pubDate>Wed, 28 May 2008 14:43:40 -0500</pubDate>
			
			



        </item>
        
        <item>
            <title>Day Tech Summit - Global Web Deployment - Infiniti 5/28/08</title>
            <description><![CDATA[The Designory - Judy Tantana<br /><br />launched infinit brand worldwide<br /><br />usability for authors<br />-use cases <br />-test tasks<br />- survey<br /><br />cq launch<br />organization<br /><ul><li>structure and operating guidelines for each region</li><li>clear distinction between global and regional control</li></ul>Benefits<br /><ul><li>regions will provide their knowedge back into the system for use by other regions for system improvement</li><li>centralized development of infrastructure</li><ul><li>allows all regions to have same baseline and capabilities</li><li>leverages global efforts across regiomms</li><li>less disparity between regions</li></ul></ul><br />First countries launched - China and Russia<br /><ul><li>2 most difficult countries - character sets and content regulations</li><li>started small and grew, knowing&nbsp; they'd have to go back and work infrastructure and development</li></ul>Design -<br /><ul><li>based on us version</li><li>business-user friendly</li><li>recent us design and creative</li><li>provide as much as possible for users/authors</li></ul>Business<br /><ul><li>per country cost reduced (support, maintenance and infrastructure)</li><li>enhancements benefit all countries</li><li>brand consistency</li><li>standardized reporting</li></ul>Technical<br /><ul><li>flash based editing</li><li><br /></li></ul><ul><li><br /></li></ul>]]></description>
            <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/global-web-deployment-infiniti-1.html</link>
            <guid>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/global-web-deployment-infiniti-1.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Day Communique</category>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">cms</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">day</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">daysummit508</category>
            
            <pubDate>Wed, 28 May 2008 14:43:40 -0500</pubDate>
			
			



        </item>
        
        <item>
            <title>OU Day Implementation</title>
            <description><![CDATA[Had been using same site since 1995.- lots of out of date content and design, every site out doing their own thing - no unifying navigation, users had to reorient themselves every time they would hit different section of the site.<br /><br />used a consultant team to review current site - have a new team reporting directly to president - web communication department was born<br />Redesign and rearchitect the site<br />challenges - buy-in and keeping project interest<br /><br />campus partnerships<br />new components<br />good design<br />keep campus (esp stakeholders) in the know<br /><br />Migration -<br /><ul><li>prioritized sites</li><li>migration should improve current sites</li><li>info arcitecture</li><li>analytics</li><li>usability</li></ul>Wireframes<br /><ul><li>10 templates with minor variations between each</li></ul>Offer:<br /><ul><li>new design or modify and fit within wireframe</li><li>department or Partner agency can do it themselves</li><li>predesigned templates</li></ul>Components<br /><ul><li>text image</li><li>dynamic flash -create movement/interest in site without having to do it themselves</li><li>tab block</li></ul>Working on this<br /><ul><li>polling</li><li>comment</li><li>rss output</li><li>photo gallery - create thumbnails and set up gallery from media library</li><li>profile gallery (alumni) <br />&nbsp;This would be great for subject specialists/public services <br /></li><li>calendar - doing some great stuff with calendaring with different levels - can push up events to different department levels all the way up to campus-wide</li><li>forced alt text in media library</li></ul>Accessibility<br />campus education<br />screen reader available in web comm office<br />google analytics - use for content and design decisions (screen res, etc)<br /><br />note: look at museum of art<br /><br />lessons learned<br /><ul><li>identifying requirements</li><li>design vs development</li><li>going live w/out redundancy ( any probs give bad pr to all users)</li><li>lacking define web requirements</li></ul>Proud of<br /><ul><li>buy in, interest</li><li>creating and maintaining achievable schedule</li><li>documentation - before migrating - understanding responsibilities - bad design and bad content ae not allowed to migrate</li><li>usability testing - new issues, confirm decisions</li><li>system free to campus - building functionality with all departments</li><li>relationship with Day</li></ul>similarity of language across departments<br /><br />can we do "fake" rss with reference paragraph?<br /><br /><ul><li><br /></li><li><br /></li></ul><br /><br /><br /><br />]]></description>
            <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/ou-day-implementation-1.html</link>
            <guid>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/ou-day-implementation-1.html</guid>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">cms</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">day</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">daysummit508</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">ou</category>
            
            <pubDate>Wed, 28 May 2008 12:52:01 -0500</pubDate>
			
			



        </item>
        
        <item>
            <title>OU Day Implementation</title>
            <description><![CDATA[Had been using same site since 1995.- lots of out of date content and design, every site out doing their own thing - no unifying navigation, users had to reorient themselves every time they would hit different section of the site.<br /><br />used a consultant team to review current site - have a new team reporting directly to president - web communication department was born<br />Redesign and rearchitect the site<br />challenges - buy-in and keeping project interest<br /><br />campus partnerships<br />new components<br />good design<br />keep campus (esp stakeholders) in the know<br /><br />Migration -<br /><ul><li>prioritized sites</li><li>migration should improve current sites</li><li>info arcitecture</li><li>analytics</li><li>usability</li></ul>Wireframes<br /><ul><li>10 templates with minor variations between each</li></ul>Offer:<br /><ul><li>new design or modify and fit within wireframe</li><li>department or Partner agency can do it themselves</li><li>predesigned templates</li></ul>Components<br /><ul><li>text image</li><li>dynamic flash -create movement/interest in site without having to do it themselves</li><li>tab block</li></ul>Working on this<br /><ul><li>polling</li><li>comment</li><li>rss output</li><li>photo gallery - create thumbnails and set up gallery from media library</li><li>profile gallery (alumni) <br />&nbsp;This would be great for subject specialists/public services <br /></li><li>calendar - doing some great stuff with calendaring with different levels - can push up events to different department levels all the way up to campus-wide</li><li>forced alt text in media library</li></ul>Accessibility<br />campus education<br />screen reader available in web comm office<br />google analytics - use for content and design decisions (screen res, etc)<br /><br />note: look at museum of art<br /><br />lessons learned<br /><ul><li>identifying requirements</li><li>design vs development</li><li>going live w/out redundancy ( any probs give bad pr to all users)</li><li>lacking define web requirements</li></ul>Proud of<br /><ul><li>buy in, interest</li><li>creating and maintaining achievable schedule</li><li>documentation - before migrating - understanding responsibilities - bad design and bad content ae not allowed to migrate</li><li>usability testing - new issues, confirm decisions</li><li>system free to campus - building functionality with all departments</li><li>relationship with Day</li></ul>similarity of language across departments<br /><br />can we do "fake" rss with reference paragraph?<br /><br /><ul><li><br /></li><li><br /></li></ul><br /><br /><br /><br />]]></description>
            <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/ou-day-implementation.html</link>
            <guid>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/ou-day-implementation.html</guid>
            
                <category domain="http://www.sixapart.com/ns/types#category">Day Communique</category>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">cms</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">day</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">daysummit508</category>
            
                <category domain="http://www.sixapart.com/ns/types#tag">ou</category>
            
            <pubDate>Wed, 28 May 2008 12:52:01 -0500</pubDate>
			
			



        </item>
        
        <item>
            <title>Non-CMS Web Application Development</title>
            <description><![CDATA[(Using JCR, REST &amp; AJAX)<br />David Nueschelar<br /><br />JCR- An API that allows you to access content bidirectionally from a content repository.<br />Content repository - best of database and file system combined - superset of all functions of relational database and file system.<br /><br />
<ul>
<li>Hierarchy</li>
<li>Sort order</li>
<li>Multi-value</li>
<li>Full-text search</li>
<li>Versioning <br /></li>
<li>Access control</li>
<li>Unstructured content&nbsp;</li></ul>REST<br />Roy Fielding<br />REST over JCR<br />JCR - heavyweight, longterm stable, durable<br />Developer - wants a way to work with jcr in a quick, agile way<br />Apache Sling - rest webkit backed by jcr, sling.js &amp; .jst<br /><br />jsp, groovy, esp, ruby, scala <br /><br />crx quickstart (download) - available at dev.day.com<br /><br /><br /><br />]]></description>
            <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/noncms-web-application-develop.html</link>
            <guid>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/05/noncms-web-application-develop.html</guid>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">daysummit508 cms day</category>
            
            <pubDate>Wed, 28 May 2008 12:05:12 -0500</pubDate>
			
			



        </item>
        
        <item>
            <title>Computers in Libraries 2008 - we survived!</title>
            <description><![CDATA[<p><p></p><p></p>Emily and I survived our presentation, Library Web Presence, Engaging the Audience.&nbsp; There were just a few more people there than we anticipated! <br /><br /><a href="http://www.flickr.com/photos/binkylush/favorites/show/">Slideshow from our presentation at Computers in Libraries, 2008.</a><br /><br /><span class="mt-enclosure mt-enclosure-image"><a href="http://www.personal.psu.edu/ful105/blogs/binkys_blog/cil8-thumb-500x333.html" onclick="window.open('http://www.personal.psu.edu/ful105/blogs/binkys_blog/cil8-thumb-500x333.html','popup','width=500,height=333,scrollbars=no,resizable=no,toolbar=no,directories=no,location=no,menubar=no,status=no,left=0,top=0'); return false"><img src="http://www.personal.psu.edu/ful105/blogs/binkys_blog/assets_c/2008/04/cil8-thumb-500x333-thumb-500x333.jpg" alt="Thumbnail image for cil8.jpg" class="mt-image-left" style="margin: 0pt 0pt 20px 20px; float: right;" height="333" width="500" /></a></span><br /><div><br /></div><div><br /></div></p>

<div><br /></div>

<div><br /></div>
]]></description>
            <link>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/04/post.html</link>
            <guid>http://www.personal.psu.edu/ful105/blogs/binkys_blog/2008/04/post.html</guid>
            
            
                <category domain="http://www.sixapart.com/ns/types#tag">cil2008</category>
            
            <pubDate>Wed, 09 Apr 2008 14:58:17 -0500</pubDate>
			
			



        </item>
        
    </channel>
</rss>
