30.05.2013 Views

2012 Best Practices for Government Libraries

2012 Best Practices for Government Libraries

2012 Best Practices for Government Libraries

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

200<br />

BEST PRACTICES <strong>2012</strong><br />

Using the SharePoint Intranet Portal to Reach, and Reach Out to,<br />

Clients at OPIC<br />

By Christopher Lee Cochran, Business and Industry Librarian, Overseas Private<br />

Investment Corporation<br />

When the In<strong>for</strong>mation Center (IC) staff at the Overseas Private Investment<br />

Corporation (OPIC), a U.S. government corporation, was asked to be the beta test<br />

site <strong>for</strong> the agency’s new SharePoint intranet portal in 2009, we eagerly accepted<br />

the challenge. Under the new SharePoint in<strong>for</strong>mation architecture, each department<br />

at OPIC would assume ownership responsibilities of its intranet page, not only <strong>for</strong><br />

the obvious content creation responsibilities, but also <strong>for</strong> managing the content:<br />

uploading new content, editing existing content, and deleting outdated content.<br />

While general intranet design features had already been worked out by the Chief<br />

In<strong>for</strong>mation Officer’s (CIO) office, with input from OPIC staff, the content<br />

development and maintenance of each individual page would be transferred to the<br />

relevant department. The CIO reached out to the In<strong>for</strong>mation Center and asked us<br />

to be the test site <strong>for</strong> this new process, since we were, by definition, an<br />

in<strong>for</strong>mation-rich office that was already focused on creating, sharing, and<br />

maintaining digital content <strong>for</strong> our clients. As with so many things in the<br />

government, the rollout of the new OPIC intranet was timed to coincide with the<br />

start of a new fiscal year, and we were given a short timeframe to complete the<br />

transfer to SharePoint. Our existing web page had become outdated and was sorely<br />

in need of updating, so the challenge of a deadline was just the impetus we needed<br />

to update and create web versions of our print guidelines, check <strong>for</strong> dead links on<br />

our reference resources page, and create new in<strong>for</strong>mation products that would<br />

highlight our expertise and contributions to OPIC’s work.<br />

Certain elements of each intranet page at OPIC were designed to be as uni<strong>for</strong>m<br />

across all departments as possible. The basic design was a three-paned page with a<br />

banner across the top. The banner was to be fairly static, except each department<br />

could put in images that reflected the general focus of their department (IC staff<br />

took photos within the IC and worked with the IT department to create a<br />

representative photo collage) (Figure 1). The left side navigation pane would<br />

feature static sections such as “Who We Are” and “What We Do.” The In<strong>for</strong>mation<br />

Center also included sections in the left side navigation pane featuring policy<br />

guidelines <strong>for</strong> some of our services.<br />

The right side navigation pane was reserved <strong>for</strong> each department to populate with<br />

document collections, <strong>for</strong>ms, links, and resource guides specific to that department.<br />

IC staff felt it was important to have search access to our catalog available right<br />

from our home page, so an online catalog search box was added to the top of the<br />

right pane as well. Links to our digital collections, subscription databases,<br />

recommended links, and resource guides round out the right side pane. (Figure 1)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!