1 / 13

Issues and Considerations in Building an Intranet

Issues and Considerations in Building an Intranet. Intranets and Internal Library Communications Triangle Research Libraries Network May 3, 2006. Overview. UNC Health Sciences Library Context Content Access Infrastructure Information Architecture Adoption. HSL Data Structure.

rianne
Download Presentation

Issues and Considerations in Building an Intranet

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Issues and Considerations in Building an Intranet Intranets and Internal Library Communications Triangle Research Libraries Network May 3, 2006

  2. Overview • UNC Health Sciences Library Context • Content • Access • Infrastructure • Information Architecture • Adoption

  3. HSL Data Structure • File server • Files organized by department and groups • Standard and department- specific subdirectories • Multiple PC file formats

  4. Identified Information Access Issues • Staff often cannot find documents or find them easily • Multiple document versions; most current document is not always clear • Staff sometimes cannot access documents (permissions)

  5. HSL Baseline Intranet pages

  6. HSL’s Process • Intranet Planning Task Force • Initial Purpose: To enable (HSL) staff to find the most current and most frequently needed forms, documents, policies, procedures, reports and other documents in an easy and timely manner. • Needs Assessment (SILS project)

  7. Content • Scope – • Decision: start with most used admin and statistical data • File formats • Decision: leverage native formats • Creation and maintenance • Staff roles • Procedures and workflows • Communication, collaboration and other tools e.g. Blogs, Wikis, RSS, chat • Decision: yes, details to be determined

  8. Access • Eligibility • Authorization/authentication • Levels of access/restriction • Access protocols • e.g. http(s), (s)ftp, vpn • Security

  9. Infrastructure • Servers • File/print, Web, database, CMS • Content management and constituent applications • Plone/Zope/Python • ColdFusion/Contribute • Wiki • HTML templates

  10. Information Architecture • Organizational facets • e.g. departments, tasks, other • Linking between independently developed content

  11. Adoption • How / Does Intranet become first stop for internal information? • Involve staff in planning & development • Make it irresistable • Incorporate into staff/library workflows • Keep it current and relevant

  12. Next … Intranet Examples • Duke – David Chandek-Stark • NCSU – May Chang, Angie Ballard • UNC-Chapel Hill Academic Affairs Library – Debra Hanken-Kurtz

  13. Questions? Contact information Barrie E. Hayes Head, Application Development Services Health Sciences Library UNC-Chapel Hill barrie_hayes@unc.edu

More Related