<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:iweb="http://www.apple.com/iweb" version="2.0">
  <channel>
    <title>My Web Sites</title>
    <link>http://www.jimangus.com/JimAngus/Websites/Websites.html</link>
    <description>Is “website” one word or two?  I still don’t know, even after ten years!&lt;br/&gt;I’ve created this page as a way to organize my thoughts on some of the projects that I’ve worked on over the years.  They’re not in any particular order.&lt;br/&gt;&lt;br/&gt;Jim Angus</description>
    <generator>iWeb 2.0.3</generator>
    <image>
      <url>http://www.jimangus.com/JimAngus/Websites/Websites_files/cwby_jim2.jpg</url>
      <title>My Web Sites</title>
      <link>http://www.jimangus.com/JimAngus/Websites/Websites.html</link>
    </image>
    <item>
      <title>eRA Website</title>
      <link>http://www.jimangus.com/JimAngus/Websites/Entries/2007/6/17_eRA_Website.html</link>
      <guid isPermaLink="false">e0550cce-4fe9-4b0e-8776-fe56194ab7d4</guid>
      <pubDate>Sun, 17 Jun 2007 12:30:16 -0400</pubDate>
      <description>&lt;a href=&quot;http://www.jimangus.com/JimAngus/Websites/Entries/2007/6/17_eRA_Website_files/oris_era.jpg&quot;&gt;&lt;img src=&quot;http://www.jimangus.com/JimAngus/Websites/Media/oris_era_1.jpg&quot; style=&quot;float:left; padding-right:10px; padding-bottom:10px; width:250px; height:191px;&quot;/&gt;&lt;/a&gt;This is a redesign of a badly out-of-date site.  The challenge was more along the lines of decided what NOT to remove and to find a focus.  The original site was clearly “developed” by the technical group who did the programming for the NIH’s electronic grants management and administration software.  Little thought went into what the users of the site actually needed.&lt;br/&gt;&lt;br/&gt;We formed a number of small focus groups and decided to focus this site on the community of scientists and administrators that seek funding from the NIH.  We would include short fact sheets on all of the services offered by the eRA program and provide links to additional content that is scattered across NIH web space.  &lt;br/&gt;&lt;br/&gt;We recently presented the new design to a working group which enthusiastically supported our goals.  The site is slated to go live in July of 2007.  </description>
      <enclosure url="http://www.jimangus.com/JimAngus/Websites/Entries/2007/6/17_eRA_Website_files/oris_era.jpg" length="78114" type="image/jpeg"/>
    </item>
    <item>
      <title>ORISphere - A Blog</title>
      <link>http://www.jimangus.com/JimAngus/Websites/Entries/2007/6/14_ORISphere_-_A_Blog.html</link>
      <guid isPermaLink="false">41a7d971-03d6-4829-bcde-7f99e884afca</guid>
      <pubDate>Thu, 14 Jun 2007 12:24:08 -0400</pubDate>
      <description>&lt;a href=&quot;http://www.jimangus.com/JimAngus/Websites/Entries/2007/6/14_ORISphere_-_A_Blog_files/oris_blogs.jpg&quot;&gt;&lt;img src=&quot;http://www.jimangus.com/JimAngus/Websites/Media/oris_blogs_1.jpg&quot; style=&quot;float:left; padding-right:10px; padding-bottom:10px; width:250px; height:192px;&quot;/&gt;&lt;/a&gt;I started an NIH blog to much resistance, at least from some quarters.  My immediate management saw it as something “fun” but that I shouldn’t spend much time on it as it wasn’t a priority.&lt;br/&gt;&lt;br/&gt;The actual reason for the blog is to move the NIH in a new direction.  Research indicates that people don’t trust traditional sources of information.  They tend to trust more informal presentations where the writer seems more a person “more like themselves.”  So I created an ORIS blog, or the “ORISphere” to prototype a new way to reach our audience.  The manner is informal and the editing is minimal.  Since this particular blog is inward facing, I didn’t meet as much resistance and found cooperation among a group of senior managers.  The intent is to show another side of management to staff, one that each person can relate to on a more informal level while still receiving “the message” intended by management.</description>
      <enclosure url="http://www.jimangus.com/JimAngus/Websites/Entries/2007/6/14_ORISphere_-_A_Blog_files/oris_blogs.jpg" length="52519" type="image/jpeg"/>
    </item>
    <item>
      <title>Portals</title>
      <link>http://www.jimangus.com/JimAngus/Websites/Entries/2007/5/9_Portals.html</link>
      <guid isPermaLink="false">5561cdc6-e0cd-4bdd-b107-8de4393e4bae</guid>
      <pubDate>Wed, 9 May 2007 12:42:47 -0400</pubDate>
      <description>&lt;a href=&quot;http://www.jimangus.com/JimAngus/Websites/Entries/2007/5/9_Portals_files/oris_workplace_portal.jpg&quot;&gt;&lt;img src=&quot;http://www.jimangus.com/JimAngus/Websites/Media/oris_workplace_portal_1.jpg&quot; style=&quot;float:left; padding-right:10px; padding-bottom:10px; width:250px; height:191px;&quot;/&gt;&lt;/a&gt;I suspect that portals as we’ve known them over the last 5 years are on their way out, to be replaced with newer, more user-friendly Web 2.0 applications.  But they’re here now and they have their uses.&lt;br/&gt;&lt;br/&gt;We use them when we want to present information to one audience while excluding another.  This means “access control”.  You could do this with an intranet, but you would have to work with your technical developers to create security groups that would manage who had access to what.  With a portal, the portal software takes care of that.  You can essentially create an intranet for your staff that includes news, a document repository and collaboration tools... all mostly out-of-the-box.&lt;br/&gt;&lt;br/&gt;This is what we’ve done with the NIH portal.  We’ve created an ORIS Workplace as a staff intranet and collaboration environment.&lt;br/&gt;&lt;br/&gt;I suspect this effort will be short-lived as technology moves on, but it is easy to do and it meets our current needs at a low cost.</description>
      <enclosure url="http://www.jimangus.com/JimAngus/Websites/Entries/2007/5/9_Portals_files/oris_workplace_portal.jpg" length="84868" type="image/jpeg"/>
    </item>
    <item>
      <title>ORIS Update</title>
      <link>http://www.jimangus.com/JimAngus/Websites/Entries/2007/3/27_ORIS_Update.html</link>
      <guid isPermaLink="false">bbe07d42-48f1-4a1b-8e85-bb79273b7bb3</guid>
      <pubDate>Tue, 27 Mar 2007 12:11:44 -0400</pubDate>
      <description>&lt;a href=&quot;http://www.jimangus.com/JimAngus/Websites/Entries/2007/3/27_ORIS_Update_files/oris_update.jpg&quot;&gt;&lt;img src=&quot;http://www.jimangus.com/JimAngus/Websites/Media/oris_update_1.jpg&quot; style=&quot;float:left; padding-right:10px; padding-bottom:10px; width:280px; height:188px;&quot;/&gt;&lt;/a&gt;Part of my “mission” at the National Institutes of Health and in my new role as Associate Director of Communications is to improve internal communications.  That is much more easily said than done by NIH management.  NIH is extremely compartmentalized with many little pfifdoms.  The only lasting solution I could see was to bring about cultural change within the organization.  The ORIS Update, a web-based newsletter attempts to do this by introducing key personnel in a way that mixes humor, informality, the importance of their work and a bit about their lives.  The idea is to make it easier to work together in teams in the future.&lt;br/&gt;&lt;br/&gt;The notable thing about the ORIS Update, in terms of technology is that we devise a very successful pure CSS two column layout.  This allows us to easily meet Federal Section 508 requirements.</description>
      <enclosure url="http://www.jimangus.com/JimAngus/Websites/Entries/2007/3/27_ORIS_Update_files/oris_update.jpg" length="63625" type="image/jpeg"/>
    </item>
    <item>
      <title>ORIS Podcasts</title>
      <link>http://www.jimangus.com/JimAngus/Websites/Entries/2007/2/28_ORIS_Podcasts.html</link>
      <guid isPermaLink="false">ef5d0f0e-10fd-4aec-b2af-091e9cd1fd8d</guid>
      <pubDate>Wed, 28 Feb 2007 12:35:18 -0500</pubDate>
      <description>&lt;a href=&quot;http://www.jimangus.com/JimAngus/Websites/Entries/2007/2/28_ORIS_Podcasts_files/oris_podcasts.jpg&quot;&gt;&lt;img src=&quot;http://www.jimangus.com/JimAngus/Websites/Media/oris_podcasts_1.jpg&quot; style=&quot;float:left; padding-right:10px; padding-bottom:10px; width:250px; height:192px;&quot;/&gt;&lt;/a&gt;This is another example of pushing the envelop in a conservative organization.  As Associate Director of Communications within the Office of Extramural Research at the NIH, my goal is to use newer technologies to help improve the image of the programs managed by the office.  The primary users of eRA (the Electronic Research Administration) feel that the eRA program is not run particularly well and there isn’t much visibility into how decisions are made.  The goal of my office is to improve the perception and improving that perception is vital or the program may find that its funding has been cut.&lt;br/&gt;&lt;br/&gt;The idea eventually is to have a series where users of the system can directly interact with key eRA management in a “Talk Back Radio” format.  eRA staff will give a short presentation and callers (or participants) will be able to ask questions that are answered live.  The results will be formatted as a podcast and provided to interested parties via RSS. &lt;br/&gt;&lt;br/&gt;At this point, we’re experimenting with the technology and gaining expertise by recording the audio of one of our staff brown bag lunch seminar series and synching up the presentation slides with the audio.&lt;br/&gt;&lt;br/&gt;Although the primary purpose is to get familiar with the technology, I can not over emphasize how important it is to capture all your content.  Raw material is what is needed for the next stage!</description>
      <enclosure url="http://www.jimangus.com/JimAngus/Websites/Entries/2007/2/28_ORIS_Podcasts_files/oris_podcasts.jpg" length="47985" type="image/jpeg"/>
    </item>
  </channel>
</rss>
