MediaWiki Open Source. MediaWiki. Outreach. as Infrastructure for. Software as. Electronic Resource Outreach. Millie Jackson Jonathan Blackburn

Transcription

1 MediaWiki Open Source MediaWiki Software as as Infrastructure for Outreach Electronic Resource Outreach Millie Jackson Jonathan Blackburn Florida State University Libraries Tallahassee, FL

2 If I had a hammer...

3 Overview Who? Why? What? How? Where? When? (organization & culture) (background, need, etc.) (a wiki if that helps) (very carefully) (are we now) (do we move on... NOW)

4 <who> </who> Who? <who> </who>

5 <who> </who> Organization Library divided into 3 divisions: Public Services, Collection Services, and Technology & Research Outreach librarians assigned department(s) Collection Development Department

6 <who> </who> Stakeholders Patrons ( users ) Faculty Students Broader campus community Librarians ( pushers )

7 <why> </why> Why? <why> </why>

8 <why> </why> Background / Initial impetus Recent move to Open Source CMS from static HTML Use of wikis by subject specialists and librarians for outreach

9 <why> </why> Why a wiki? Easy to update and un-do Minimal learning curve Connect with targeted user groups

10 <why> </why> Why MediaWiki? Robust support community Proven security Widgets, extensions, etc. Fit with current infrastructure Ease of install PHP/MySQL

11 <why> </why> Purposes / Goals Targeted content Personal empowerment (for librarians and end-users)

12 <what> </what> What? <what> </what>

13 <what> </what> A Wiki (but not) Open editing for librarians End-users only have view access Content Management without all the formality

14 <what> </what> Organized by Subject Website Wiki

15 <what> </what> A Personal Touch Added photos of outreach librarians

16 <how> </how> How? <how> </how>

17 <how> </how> Implementation Fast rollout (one month from initial impetus to implementation/training) Minimal planning Soft launch

18 <how> </how> Training Dual strategy Beginners: Hands-on instruction, paper cheat sheets Advanced: Basic introduction, online help tools links to documentation Need for best practices

19 <where> </where> Where are we now?

20 <where> </where> E-Resource by Subject Prominent link with embedded photo

21 <where> </where> URL Aliases Current link schema for MediaWiki install: /subject/index.php/clas sics If move to different software, can t be maintained Alternate URL Alias: /subject/classics Easy to remember Durable and consistent

22 <where> </where> Customization of interface Better meets FSU identity guidelines Remove authenticated user features No login link or edit tabs Removed toolbox

23 <where> </where> Basic Customization Previous Page: Clean /simple Nice layout No FSU ID

24 <where> </where> FSU look and feel New Look: FSU header Matching background and fonts

25 <where> </where> Removed Wiki-ness

26 <where> </where> Functionality Extensions Embedded chat Meebome enabled Plugoo, Chantango, etc. Google CSE

27 <where> </where> Embedded Chat Allows flash-based chat widgets MeeboMe Plugoo Chatango

28 <where> </where> Google CSE Custom Search Engine Search across subject-based selection of websites

29 <where> </where> The English Super Page Collaboration between technology and outreach Serve as point of inspiration for other outreach librarians Encourage further content creation and use of MediaWiki functionality

30 <where> </where> Challenges & Opportunities Discovery of Wiki pages What goes here? How to make content more than a PDF of the paper version Updates fitting the Wiki into workflow/workpatterns

31 <where> </where> Coming soon... Best Practices documentation Marketing New Features Turn on talk page WYSIWYG editing

32 <when> </when> When do we move on? <when> </when>

33 <when> </when> Taking Stock Pros: Quick and easy changes Openness and collaboration Positive user feedback Cons: Clarification of purpose and best practices Lack of structure & uniformity

34 <when> </when> Alternatives and possibilities Blogging platform (Wordpress MU?) RSS Feeds Facebook and MySpace Flickr and Youtube Return of the CMS Book module Library staff profiles Discussion forums, et

35 <when> </when> Things to remember Services breed expectations ( Services not software ) Communication not committees Change happens Evolve/adapt Take stock consider stakeholders

36 Thanks Robert H. McDonald Chronopolis Project Manager/SDSC /AIM - mcdonald@sdsc.edu For sharing slides, background information, ideas, suggestions, as well as the original impetus for this project.

37 Contact Info. Millie Jackson Collection Development Librarian/FSU /AIM Jonathan Blackburn Web Development Librarian/FSU /AIM