CRGH Medical Library Wiki: Improving staff communication and interaction Julia Philips and Kaye Lee Concord Repatriation G...
Background – CRGH Medical Library <ul><li>Library clientelle </li></ul><ul><ul><li>Hospital staff (a principal teaching ho...
Catalyst for action <ul><li>Two new staff members late 2006 / early 2007 </li></ul><ul><li>Need to develop strong communic...
What is a Wiki? <ul><li>“ A wiki is a freely expandable collection of interlinked Web “pages”, a hypertext system for stor...
 
Our Objective <ul><li>To enhance staff communication and interaction within the Library through development and use of a l...
Methodology <ul><li>Develop criteria for wiki selection </li></ul><ul><li>Identify suitable wiki applications </li></ul><u...
1. Develop criteria <ul><li>Freely available </li></ul><ul><li>Authentication to prevent unauthorised access </li></ul><ul...
2. Identify potential wiki applications <ul><li>Two categories of wikis were identified: </li></ul><ul><li>Externally host...
3. Select best option and implement <ul><li>a.  Selection – </li></ul><ul><ul><li>Do we download and host a wiki applicati...
3. Select best option and implement <ul><ul><li>b.  Implementation - Carried out at  http:// pbwiki.com / </li></ul></ul><...
4. Introduce to Staff <ul><li>Formally introduced at staff meeting of 6th March 2007 </li></ul><ul><li>Overview of wikis p...
5. Survey Staff <ul><li>After some six months of use a questionnaire was developed  </li></ul><ul><li>Distributed to Libra...
Survey Results Q.1 Have you accessed the Concord Medical Library wiki? <ul><li>All library staff have accessed the wiki. <...
Survey Results  Q.2  Which page/s do you visit?   <ul><li>All pages have been viewed by at least 50% of library staff. </l...
Survey Results  Q.3 Have you used the wiki Help function? <ul><li>Is the use of the Help function reflective of what diffe...
Survey Results  Q.4 How do you keep aware of changes to the wiki?   <ul><li>All staff use the automatic email alerts to ke...
Survey Results  Q.5 Which page/s have you edited/changed?   <ul><li>No page has been edited/changed by all staff members. ...
Survey Results  Q.6  Which page/s have you created/added ?  <ul><li>Pages have been created/added by two staff members onl...
they had not   All <ul><li>All staff answered in the negative </li></ul>Have you deleted any pages?   Survey Results
Survey results Q.7 Has the wiki been of benefit to you in terms of communication regarding Library activities? <ul><li>“ C...
Survey results Q.8 Any changes that could be made to make the wiki more useful and/or usable? <ul><ul><li>New project page...
Survey Results Q.9  Have you needed to make any changes to the way you work to integrate the wiki? <ul><li>Again, mapping ...
<ul><li>Q.10 Is there something else you  </li></ul><ul><li>  would prefer to use to stay  </li></ul><ul><li>  informed in...
Survey results Q.11 Are you comfortable using the wiki? <ul><li>All staff indicated comfort in using the wiki and don’t ha...
If you have any further wiki-related comments to make please add them here <ul><li>Is there a limit to the kinds of things...
6. Analysis of results <ul><li>Analysis filters : </li></ul><ul><li>Is the wiki being used? </li></ul><ul><li>How is it be...
Is the wiki being used? <ul><li>All pages have been viewed  (echoes Leuf and Cunningham  comment re  “ dropping by ” ) </l...
How is it being used ? <ul><li>Most users appear happy to  view   pages </li></ul><ul><ul><ul><li>‘ Interesting Articles’ ...
Is the wiki proving useful for staff communication? <ul><li>Yes – All 4 staff answered affirmatively to Question 8 re usef...
<ul><li>In terms of  editing ,  the Calendar was a hit with 75% of staff changing and adding information. </li></ul><ul><l...
Possible Improvements <ul><li>50% of staff did not have any suggestions for improvement </li></ul><ul><li>Balance of staff...
Comfort levels and changes needed to integrate wiki into work practices <ul><li>100% of staff indicated they were comforta...
7. Corporate policy requirements <ul><li>Policy governing use of wikis sought from IM&T, and existing policy consulted to ...
Conclusions <ul><li>Have we been successful in enhancing communications and interaction in the Library at Concord through ...
Conclusions <ul><li>Additional requirements identified for use - </li></ul><ul><ul><li>High level encryption or internal h...
Other library uses for wikis <ul><li>“ Can become true community resources that position the library as an online hub” (Fa...
More Uses <ul><li>Multi-user, collaborative wiki applications can include  (Leuf & Cunningham, 2001): </li></ul><ul><ul><l...
Finally <ul><li>The wiki has indeed proved useful in improving communications within the library at Concord, although it h...
Upcoming SlideShare
Loading in...5
×

CRGH Medical Library Wiki: Improving staff communication and interaction to enhance user services (Julia Philips & Kaye Lee)

5,036

Published on

CRGH Medical Library Wiki: Improving staff communication and interaction to enhance user services

JR Philips and KR Lee
Concord Repatriation General Hospital Medical Library

Background:
The Medical Library at Concord Repatriation General Hospital has four full-time staff members - Library Manager, Reference Librarian, Document Delivery Officer and Library Officer, and a volunteer who assists ½ day a week. This team is involved in the development and implementation of a variety of projects to aid library clients, who comprise staff of both the hospital (a principal teaching hospital of the University of Sydney) and the wider Sydney South West Area Health Service, as well as students from a variety of other tertiary institutions.

Whilst staff meetings once every other month provide a framework to drive these projects and a time to discuss required topics such as occupational health & safety, security and quality, the introduction of a wiki to improve Library staff communications and interaction across all these areas seemed both timely and beneficial. With this in mind, the following research was undertaken.

Objective:
Development and use of a library-oriented wiki to enhance communication and interaction within the Library.

Methodology
1. Identify potential wiki applications, based on the following criteria:
 Freely available
 Authentication to prevent unauthorised access
 Easy to use (WYSIWYG editing)
 RSS and email updates for changes made
 No extra software required to run the application
 Runs on Windows
 Stable and upgradeable
 File based storage
 Page Preview
 Comments
 Complex tables
 HTML tag support
 File attachments

2. Seek advice from SSWAHS Information Management & Technology (IM&T) in relation to any policy relating to use of wikis in the Area.

3. Implement preferred wiki on a trial basis.

4. Provide training in wiki use.

5. Survey users to measure usefulness of wiki in improving communication and interaction.

Results:
 Potential wiki applications were identified using http://www.wikimatrix.org/ in conjunction with the previously identified criteria.

 Two categories of wikis were identified; those externally hosted and available via the Internet and those internally hosted and available over LAN/WAN:

 Externally hosted wiki applications:
o BrainKeeper http://www.brainkeeper.com/
o CentralDesktop http://www.centraldesktop.com/
o Metadot Wiki http://www.metadot.net
o PBwiki http://pbwiki.com/
o SamePage http://www.etouch.net/
o Socialtext http://www.socialtext.com/
o Wikispaces http://www.wikispaces.com/
o
Internally hosted wiki applications:
o MoniWiki http://kldp.net/projects/moniwiki/
o Oddmuse http://www.oddmuse.org/
o PhpWiki http://phpwiki.sourceforge.net/
o PmWiki http://www.pmwiki.org/
o PukiWiki http://pukiwiki.sourceforge.jp/
o TWiki http://twiki.org/

 An externally hosted wiki (PBwiki) was chosen as a pilot for the concept as it enabled a wiki to be set up very quickly and required minimal training time. This application was chosen from the short-list as the wiki implementor (JR Philips) had experience using this wiki elsewhere

 Library staff have been trained in the use of PBwiki.

 A survey to measure the usefulness of the wiki in enhancing communication and teamwork is currently being developed.

 Advice has been sought from the CIO, SSWAHS to ensure that the externally hosted wiki is compliant with Area policies and IT requirements.

 Depending upon IM&T requirements, it is recommended that PhpWiki, PmWiki and Twiki be trialled first in the event that an internally hosted wiki is required as they have the largest range of other features available out of the six listed.

Conclusions:
The project has yet to be completed, but at this point the different sections of the pilot Internet-based wiki appear to be worki

Published in: Business, Technology
2 Comments
1 Like
Statistics
Notes
  • Try http://vpshsoting.blogspot.com for a good hosting
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • too much words...
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
5,036
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
38
Comments
2
Likes
1
Embeds 0
No embeds

No notes for slide
  • CRGH Medical Library Wiki: Improving staff communication and interaction to enhance user services (Julia Philips & Kaye Lee)

    1. 1. CRGH Medical Library Wiki: Improving staff communication and interaction Julia Philips and Kaye Lee Concord Repatriation General Hospital Medical Library November 2007
    2. 2. Background – CRGH Medical Library <ul><li>Library clientelle </li></ul><ul><ul><li>Hospital staff (a principal teaching hospital of the University of Sydney) </li></ul></ul><ul><ul><li>Sydney South West Area Health Service staff </li></ul></ul><ul><ul><li>Students from a variety of other tertiary institutions. </li></ul></ul><ul><li>Four full-time staff members: </li></ul><ul><ul><li>Library Manager </li></ul></ul><ul><ul><li>Reference Librarian </li></ul></ul><ul><ul><li>Document Delivery Officer </li></ul></ul><ul><ul><li>Library Officer </li></ul></ul><ul><li>Staff meetings held every two months </li></ul>
    3. 3. Catalyst for action <ul><li>Two new staff members late 2006 / early 2007 </li></ul><ul><li>Need to develop strong communication lines in new team to support customer services </li></ul><ul><li>Interest in utilising Web 2.0 / Library 2.0 tools, in particular, the wiki, and its collaborative characteristics – defined as “a collaborative website which can be directly edited by anyone with access to it” (Wiktionary) – just the thing to enhance communication. </li></ul><ul><li>http:// en.wiktionary.org/wiki/wiki accessed 29 October 2007 </li></ul>
    4. 4. What is a Wiki? <ul><li>“ A wiki is a freely expandable collection of interlinked Web “pages”, a hypertext system for storing and modifying information – a database, where each page is easily editable by any user with a forms-capable Web browser client” (Leuf & Cunningham, 2001) </li></ul><ul><li>“ A wiki is a server-based collaborative tool that allows any authorised user to edit Web pages and create newer ones using nothing more than a Web browser and a text entry form on a Web page… Wikis make it possible for people to collaborate in a Web environment by creating, organising, and maintaining a Web site of automatically linked pages (Chawner & Lewis, 2006) </li></ul>Leuf B, Cunningham W. (2001) The Wiki way: quick collaboration on the web . Boston: Addison-Wesley, 14 Chawner B, Lewis PH. (2006) WikiWikiWebs: New ways to communicate in a web environment. Information Technology and Libraries, 25, 33-43.
    5. 6. Our Objective <ul><li>To enhance staff communication and interaction within the Library through development and use of a library-oriented wiki </li></ul>
    6. 7. Methodology <ul><li>Develop criteria for wiki selection </li></ul><ul><li>Identify suitable wiki applications </li></ul><ul><li>Select best option and implement </li></ul><ul><li>Introduce to staff </li></ul><ul><li>Survey staff </li></ul><ul><li>Gather and analyse survey results </li></ul><ul><li>Review corporate policy affecting wiki use </li></ul><ul><li>Draw conclusions as to usefulness of wiki as an aid to communication and interaction in the Library at Concord, and its usefulness in other settings </li></ul>
    7. 8. 1. Develop criteria <ul><li>Freely available </li></ul><ul><li>Authentication to prevent unauthorised access </li></ul><ul><li>Easy to use (WYSIWYG editing) </li></ul><ul><li>RSS and email updates for changes made </li></ul><ul><li>No extra software required to run the application </li></ul><ul><li>Runs on Windows </li></ul><ul><li>Stable and upgradeable </li></ul><ul><li>File based storage </li></ul><ul><li>Page Preview </li></ul><ul><li>Comments </li></ul><ul><li>Complex tables </li></ul><ul><li>HTML tag support </li></ul><ul><li>File attachments </li></ul><ul><li>Potential wiki applications were identified using http://www.wikimatrix.org/ </li></ul>
    8. 9. 2. Identify potential wiki applications <ul><li>Two categories of wikis were identified: </li></ul><ul><li>Externally hosted applications </li></ul><ul><ul><li>BrainKeeper </li></ul></ul><ul><ul><li>CentralDesktop </li></ul></ul><ul><ul><li>Metadot Wiki </li></ul></ul><ul><ul><li>PBwiki </li></ul></ul><ul><ul><li>SamePage </li></ul></ul><ul><ul><li>Socialtext </li></ul></ul><ul><ul><li>Wikispaces </li></ul></ul><ul><li>Internally hosted applications </li></ul><ul><ul><li>MoniWiki </li></ul></ul><ul><ul><li>Oddmuse </li></ul></ul><ul><ul><li>PhpWiki </li></ul></ul><ul><ul><li>PmWiki </li></ul></ul><ul><ul><li>PukiWiki </li></ul></ul><ul><ul><li>Twiki </li></ul></ul>
    9. 10. 3. Select best option and implement <ul><li>a. Selection – </li></ul><ul><ul><li>Do we download and host a wiki application onsite? </li></ul></ul><ul><ul><ul><li>OR </li></ul></ul></ul><ul><ul><li>Do we choose an externally hosted wiki? </li></ul></ul><ul><ul><ul><ul><li>Externally hosted solution chosen – </li></ul></ul></ul></ul><ul><ul><ul><ul><li>PBwiki - one of four likely candidates </li></ul></ul></ul></ul>
    10. 11. 3. Select best option and implement <ul><ul><li>b. Implementation - Carried out at http:// pbwiki.com / </li></ul></ul><ul><li>Name chosen & free account set up </li></ul><ul><li>Basic settings adjusted (eg public/private access) </li></ul><ul><li>Welcome message added to front page </li></ul><ul><li>Preset ‘How it works’ and tutorial links left in place </li></ul><ul><li>Calendar added & new pages created – </li></ul><ul><ul><li>Website Changes </li></ul></ul><ul><ul><li>Newsletter Ideas </li></ul></ul><ul><ul><li>Potential Resources to add to the Website </li></ul></ul><ul><ul><li>Interesting articles and other resources </li></ul></ul><ul><ul><li>Library Objectives (added a little later) </li></ul></ul><ul><li>Links to pages added to SideBar (wiki’s navigation bar) </li></ul><ul><li> </li></ul><ul><li>and the wiki looked like this  </li></ul>
    11. 12.
    12. 13.
    13. 14.
    14. 15.
    15. 16. 4. Introduce to Staff <ul><li>Formally introduced at staff meeting of 6th March 2007 </li></ul><ul><li>Overview of wikis provided </li></ul><ul><li>Existing pages were shown </li></ul><ul><ul><li>Calendar </li></ul></ul><ul><ul><li>Website Updates </li></ul></ul><ul><ul><li>Potential resources to add to the website </li></ul></ul><ul><ul><li>Newsletter Ideas </li></ul></ul><ul><ul><li>Library Objectives </li></ul></ul><ul><ul><li>Interesting articles and other Resources </li></ul></ul><ul><li>URL and password provided </li></ul><ul><li>Noted that the wiki could be edited and accessed by all Library staff </li></ul><ul><li>Help was provided on an ‘as needed’ basis </li></ul>
    16. 17. 5. Survey Staff <ul><li>After some six months of use a questionnaire was developed </li></ul><ul><li>Distributed to Library staff on 26 September 2007 with all completed forms returned by 3 October 2007 </li></ul><ul><ul><li>100% response rate </li></ul></ul><ul><li>Thirteen questions were posed to try to ascertain: </li></ul><ul><ul><li>If and how the wiki was being used </li></ul></ul><ul><ul><li>Whether or not the wiki was proving useful for staff communication </li></ul></ul><ul><ul><li>Possible improvements </li></ul></ul><ul><ul><li>Comfort levels and difficulties in integrating wiki into practice </li></ul></ul>
    17. 18. Survey Results Q.1 Have you accessed the Concord Medical Library wiki? <ul><li>All library staff have accessed the wiki. </li></ul><ul><li>Access was not enforced but was encouraged through the formal introduction of the wiki at a staff meeting and the use of the wiki as an information repository. </li></ul><ul><li>First impressions were generally positive: </li></ul><ul><ul><li>“ Useful” </li></ul></ul><ul><ul><li>“ Informative” </li></ul></ul><ul><li>There was one reservation about the external location of the wiki. </li></ul>
    18. 19. Survey Results Q.2 Which page/s do you visit? <ul><li>All pages have been viewed by at least 50% of library staff. </li></ul><ul><li>Although there have been no known discussions relating to posted interesting articles, it is hoped that some articles will have been accessed and read. </li></ul>100% 75% 50% Interesting articles Front page Calendar Website updates Newsletter Sidebar Library objectives URLs to add to proxy Potential resources to add to the website NSWHLF wiki paper
    19. 20. Survey Results Q.3 Have you used the wiki Help function? <ul><li>Is the use of the Help function reflective of what different staff members are trying to do with the wiki? </li></ul><ul><ul><li>Help may not be required if pages are being read but not added or edited. </li></ul></ul><ul><ul><li>Staff may be more likely to look at the Help if they want to understand how the wiki works in more detail. </li></ul></ul><ul><li>It could also be suggested that the lack of use of the Help function supports the ease of use and intuitiveness of the wiki for the less experienced users. </li></ul>
    20. 21. Survey Results Q.4 How do you keep aware of changes to the wiki? <ul><li>All staff use the automatic email alerts to keep aware of changes to the wiki, but other methods are also used. </li></ul><ul><li>RSS is problematic as RSS readers like Bloglines are blocked by the proxy at this stage. </li></ul>
    21. 22. Survey Results Q.5 Which page/s have you edited/changed? <ul><li>No page has been edited/changed by all staff members. </li></ul><ul><li>Most pages have been read but not interacted with in any other way. </li></ul><ul><li>Most pages have been edited/changed by one person only. </li></ul>75% 50% 25% Calendar Newsletter ideas Library objectives URLs to add to the proxy Front page Website updates Potential resources to add to the website Sidebar Interesting articles NSWHLF wiki page
    22. 23. Survey Results Q.6 Which page/s have you created/added ? <ul><li>Pages have been created/added by two staff members only. </li></ul><ul><ul><li>This reflects the read/edit pattern found in the previous responses. </li></ul></ul><ul><li>Other staff members appear to be happy to use the wiki and interact with the calendar. May not be adding content because: </li></ul><ul><ul><li>They may not want to add anything </li></ul></ul><ul><ul><li>They may not be used to providing input in this collaborative way </li></ul></ul><ul><ul><li>They may need more encouragement and training to use the interactive options </li></ul></ul>
    23. 24. they had not All <ul><li>All staff answered in the negative </li></ul>Have you deleted any pages? Survey Results
    24. 25. Survey results Q.7 Has the wiki been of benefit to you in terms of communication regarding Library activities? <ul><li>“ Calendar is handy for proposed events” </li></ul><ul><li>“ Without Wiki, I would be less aware of projects that I am not involved in” </li></ul><ul><li>“ Finding out new newsletter ideas” </li></ul><ul><li>“ Provides a quick easy way to share ideas” </li></ul><ul><li>“… publicise and promote library objectives + strategic planning” </li></ul>
    25. 26. Survey results Q.8 Any changes that could be made to make the wiki more useful and/or usable? <ul><ul><li>New project pages </li></ul></ul><ul><ul><li>More control over editing/access </li></ul></ul><ul><ul><li>Improved design and layout of email alerts </li></ul></ul>
    26. 27. Survey Results Q.9 Have you needed to make any changes to the way you work to integrate the wiki? <ul><li>Again, mapping the results for this question against the results of the question dealing with editing/changing suggests that those who have been making changes to the content have had to change the way they work to integrate the wiki. </li></ul><ul><ul><li>Remembering to check the wiki for relevant information </li></ul></ul><ul><ul><li>Sharing more information </li></ul></ul>
    27. 28. <ul><li>Q.10 Is there something else you </li></ul><ul><li> would prefer to use to stay </li></ul><ul><li> informed instead of the wiki? </li></ul><ul><ul><ul><ul><li>All staff indicated in the negative </li></ul></ul></ul></ul>Survey Results
    28. 29. Survey results Q.11 Are you comfortable using the wiki? <ul><li>All staff indicated comfort in using the wiki and don’t have anything they would prefer to use instead. </li></ul><ul><li>This suggests possibilities for on-going extended use. </li></ul><ul><ul><li>Project management </li></ul></ul><ul><ul><li>- Patron resource hub </li></ul></ul><ul><li>This also supports the ease of use of the wiki (reflected in the Help function usage pattern). </li></ul>
    29. 30. If you have any further wiki-related comments to make please add them here <ul><li>Is there a limit to the kinds of things we can do with the wiki? ie do we hit security concerns or comfort constraints… </li></ul><ul><li>The wiki concept seems to be a great project management tool, as interested parties can interact + share easily + with immediacy. Useful not just for libraries, but any planning group. </li></ul><ul><li>Having the software sitting on an internally located wiki server would ensure security + privacy issues … </li></ul>Survey Results
    30. 31. 6. Analysis of results <ul><li>Analysis filters : </li></ul><ul><li>Is the wiki being used? </li></ul><ul><li>How is it being used? </li></ul><ul><li>Is the wiki proving useful for staff communication? </li></ul><ul><li>Possible improvements </li></ul><ul><li>Comfort levels and changes needed in integrating the wiki into practice </li></ul>
    31. 32. Is the wiki being used? <ul><li>All pages have been viewed (echoes Leuf and Cunningham comment re “ dropping by ” ) </li></ul><ul><li>Most pages have been viewed by most staff (although not all) </li></ul><ul><li>First impressions reveal staff feel it is useful and easy to use </li></ul>Yes!
    32. 33. How is it being used ? <ul><li>Most users appear happy to view pages </li></ul><ul><ul><ul><li>‘ Interesting Articles’ the most popular with all staff viewing it </li></ul></ul></ul><ul><ul><ul><li>The Calendar (viewed by 75%) and receiving comments such as handy and useful </li></ul></ul></ul><ul><ul><ul><li>‘ Front Page’, ‘Website Updates’, ‘Newsletter’, ‘SideBar’, ‘Library Objectives’, and ‘Urls to add to proxy’ all viewed by 75% of staff, </li></ul></ul></ul><ul><li>Potential resources to add to the website and NSWHLF wiki page was viewed by only 50% </li></ul><ul><li>All 4 staff continued to receive the automatic email alerts (cancellable) </li></ul><ul><li>All staff appear to be happy to use the wiki, with different staff accessing different pages – possibly because of their different interests, approaches, and workplace roles. </li></ul>
    33. 34. Is the wiki proving useful for staff communication? <ul><li>Yes – All 4 staff answered affirmatively to Question 8 re usefulness </li></ul><ul><li>Supporting comments reflected this outlook, including – </li></ul><ul><ul><ul><li>Being kept informed </li></ul></ul></ul><ul><ul><ul><li>Awareness </li></ul></ul></ul><ul><ul><ul><li>New ideas </li></ul></ul></ul><ul><ul><ul><li>Sharing ideas </li></ul></ul></ul><ul><ul><ul><li>Active role in planning </li></ul></ul></ul><ul><ul><ul><li>Developing ideas </li></ul></ul></ul><ul><ul><ul><li>Empowering </li></ul></ul></ul><ul><li>Interest shown by staff in visiting and editing also supports usefulness of the tool </li></ul>
    34. 35. <ul><li>In terms of editing , the Calendar was a hit with 75% of staff changing and adding information. </li></ul><ul><li>Only 50% had edited the ‘Newsletter’, ‘Library Objectives’ and ‘Urls to add to the proxy’ pages, with just just one person (25%), the developer, editing all 10 pages. </li></ul><ul><li>In terms of creating new pages, 50% of staff indicated that had not created any pages, one respondent had created one page, and one respondent or 25%, had created 9 pages (in developing the site). </li></ul><ul><li>In terms of deleting pages, all indicated they had not done so. </li></ul><ul><ul><li>Most staff are using the wiki to view information, rather than interactively edit or create pages (with the exception of the Calendar. Perhaps staff don’t yet have an understanding of the potential of the wiki, feel they have nothing to add, may be hesitant in providing input in this collaborative way, or simply need more training and encouragement. </li></ul></ul>
    35. 36. Possible Improvements <ul><li>50% of staff did not have any suggestions for improvement </li></ul><ul><li>Balance of staff offered the following: </li></ul><ul><ul><li>More pages for new projects </li></ul></ul><ul><ul><li>Increased control over editing/deletion </li></ul></ul><ul><ul><li>Improvements in email alert layout </li></ul></ul>
    36. 37. Comfort levels and changes needed to integrate wiki into work practices <ul><li>100% of staff indicated they were comfortable in using the wiki, with accompanying comments highlight ease of using the wiki </li></ul><ul><li>50% of staff indicated they did not make any changes to their work practices </li></ul><ul><li>The balance mentioned the following: </li></ul><ul><ul><li>Handling email alerts/RSS feeds through filtering </li></ul></ul><ul><ul><li>Despite alerts, need still exists to consult actual pages </li></ul></ul><ul><ul><li>Changing paper-based habits to a wiki orientation </li></ul></ul><ul><ul><li>Need to be comfortable about sharing ideas and working collaboratively </li></ul></ul>
    37. 38. 7. Corporate policy requirements <ul><li>Policy governing use of wikis sought from IM&T, and existing policy consulted to identify requirements </li></ul><ul><li>Official IM&T policy under review, and no definitive information yet available </li></ul><ul><li>Statutory requirements to maintain records for scrutiny questioned – given wiki open-edit characteristics </li></ul><ul><ul><li>Wiki documents seen as temporary, of a planning nature </li></ul></ul><ul><ul><li>Any document that needs to be retained, should be held elsewhere also, for scrutiny and legal discovery purposes </li></ul></ul><ul><li>Confidentiality requirement may have a bearing – </li></ul><ul><ul><li>We chose externally hosted wiki, accessible by user name and password, with 128-bit SSL encryption, but better solution may be needed to reduce risk </li></ul></ul><ul><ul><li>Alternatives lie in stronger encryption (eg PBwiki enterprise-grade encryption) or downloading software to a local server. </li></ul></ul>
    38. 39. Conclusions <ul><li>Have we been successful in enhancing communications and interaction in the Library at Concord through our wiki intervention? </li></ul><ul><li>All staff have viewed a majority of available pages, so the wiki provides a good bulletin board for information. This certainly enhances one-way communication so we have achieved out object in part, but the collaborative effect that a wiki can provide when used to full potential has yet to be fully achieved. </li></ul><ul><li>Use of the calendar is more tangible evidence of interaction, with most staff adding their ADOs, appointments, etc. so that others will be more aware, but again it’s one way communication - someone adds something, someone else reads it </li></ul><ul><li>With 50% of staff yet to create or edit a page, there is a perceived need for additional training and encouragement to stimulate staff to contribute to, comment on and edit (where permitted) to enhance interaction and collaboration, and to get the best out of the wiki. </li></ul>
    39. 40. Conclusions <ul><li>Additional requirements identified for use - </li></ul><ul><ul><li>High level encryption or internal hosting </li></ul></ul><ul><ul><li>Access control that allows authority over editing and deleting of pages </li></ul></ul><ul><ul><li>Greater design capacity for layout of pages and alerts </li></ul></ul><ul><ul><li>Means of capturing statistics on page usage – for papers like this </li></ul></ul><ul><li>Be mindful of corporate requirements </li></ul>
    40. 41. Other library uses for wikis <ul><li>“ Can become true community resources that position the library as an online hub” (Farkas, 2005) </li></ul><ul><li>Possible library uses according to Stephens include </li></ul><ul><ul><li>Subject guides </li></ul></ul><ul><ul><li>policy manuals </li></ul></ul><ul><ul><li>Resource listings </li></ul></ul><ul><ul><li>Project planning </li></ul></ul><ul><li>Library supported hospital use </li></ul><ul><li>– departmental journal clubs </li></ul><ul><ul><li>collaborative research projects </li></ul></ul><ul><ul><li>Inservices </li></ul></ul><ul><ul><li>Grand rounds </li></ul></ul><ul><li>Cross-Area Health Service Library use </li></ul>Farkas, M. (2005) Using Wikis to Create Online Communities 2005 http:// webjunction.org /do accessed on 17 September 2007 Stephens, M. (2006) Wikis Part 1:Wikis & Libraries in Library Technology Reports Chapter 5 : Academic Research Library, 52
    41. 42. More Uses <ul><li>Multi-user, collaborative wiki applications can include (Leuf & Cunningham, 2001): </li></ul><ul><ul><li>Resource collections (content and links) </li></ul></ul><ul><ul><li>Collaborative FAQs </li></ul></ul><ul><ul><li>Project management </li></ul></ul><ul><ul><li>Web site management </li></ul></ul><ul><ul><li>Discussion and review </li></ul></ul><ul><ul><li>Shared bulletin board postings </li></ul></ul><ul><ul><li>Online guestbook </li></ul></ul><ul><ul><li>Free-form database </li></ul></ul>Leuf B, Cunningham W. (2001) The Wiki way: quick collaboration on the web. Boston: Addison-Wesley, 34-35
    42. 43. Finally <ul><li>The wiki has indeed proved useful in improving communications within the library at Concord, although it has not yet achieved its full collaborative potential. </li></ul><ul><li>With the various additional criteria addressed, it should continue to be a valuable communications tool – be that as a simple bulletin board, or a collaborative and dynamic information resource. </li></ul><ul><li>There is great potential for the wiki to be used in a host of different ways in the hospital system - what’s more, it’s fun and easy to use! </li></ul><ul><li>Wiki wiki! </li></ul>
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×