Tutor Note : This module includes Virtual Session 5 on Tuesday 10 March which Kathryn Seale, the Communities Support expert will present
SSI Transition Leads will also schedule a call with you talk through these points in relation to the SSI's wiki (or multiple wikis)
Wiki ownership and governance is an important consideration. Someone in the business must be designated as the Administrator for the space. There may be more than one Administrator, but they need to understand the decisions to be made in order to set Space Permissions appropriately, and what additional rights / responsibilities being the Administrator gives them. You may need to give a mini-training session!
Attachments : there are exceptions to the "no attachments in wikis" principle (it's not a rule because Wiki Central does allow attachments, but it is not built to be a repository). Graphics are allowed, and small files which are very frequently updated may be considered for attachment to a wiki page. In general, GBS content should always be stored in an a formal repository which has the appropriate level of access control and which is globally-accessible. Wiki owners should use Cattail, teamrooms, W3 Media Library, Practitioner Portal etc for storing attachments. Then provide access to the content via links from the wiki.
Generally, distribute information and files without flooding inbaskets with data files, and publish links to content scattered over the IBM intranet
Replace a plethora of teamrooms, KnowledgeCafés, spreadsheets, documents, websites, eMails and other repositories or channels
Tiny Links are a short URL that does not change even if the name or location of a wiki page is changed. This allows links created with Tiny URLs to be very robust.
always use the Tiny URL for creating links between pages and in any "long-lasting" mails such as E-Cards.
You can find the Tiny Link for a wiki page by going to the bottom of that page, clicking the "Info" link and looking in the box to the top left of the Info page.
As you probably know, a template is a page you can copy to create the same structure on different pages. This is very useful in wiki’s because it helps to ensure consistency throughout.
There are also templates set up in some SSI wikis for example the CRM wiki has a standard page template, so do some of the ISV wikis. The SCM wiki has templates for Engagement Storyboards and for Learning Event E-Cards.
Only people with Admin rights in a wiki space can create new page templates.
This is the standard template used in the GBS Packaging wiki. When you see a template in another wiki, you can copy into the wiki you want very easily. Depending on the what server the wiki is on, will determine how to copy. Both methods not only apply to templates but all pages you wish to copy from another wiki.
If you are on the same server you can copy a page simply by changing the space ID to where you want the page copied to. To identify the space name, look in the URL
To recover previous versions of wiki pages – view page history and look through or compare earlier versions to find the one you want to recover
Here are 2 different types of tab examples. In the 1st example each tab is its own page, but gives the appearance it is the same page. Since each page is its own, this is much easier to create. There are no limitation to what you can do on the page, you are still able to do tables, toc, banners, etc. In the 2nd example the content structure has to be much simpler. You cannot add much but text and images due to the complexity of the macro. Each has its own purpose. The 1st tab has more commonality with each page, where as the 2nd example is more of an eCard format and has completely different content. I provided the link to both examples so you can explore them more.
Recall also that in the presentation on Knowledge Packaging Liz included an example of a tabbed format used for the HCM Workforce & Talent Solution offering. This is also in GBSPAK in the Selected Business Solutions section : (http://w3.tap.ibm.com/w3ki2/x/STUH ) and is an example of the multiple pages tabbed format.
Recall also that in the presentation on Knowledge Packaging Liz included an example of a tabbed format used for the HCM Workforce & Talent Solution offering. This is also in GBSPAK in the Selected Business Solutions section : (http://w3.tap.ibm.com/w3ki2/x/STUH ) and is an example of the multiple pages tabbed format.
So as you can see there are many variations of the tab format, all very useful.
Give examples of how the business might want to use a poll in their wiki – why would they be interested to do this? what examples are there of polls being used?
I will like to high light a few thinks on this page, a very common practice among SSI wiki is to use the Table of Contents Feature. It allows you to multiple things are one page without having to scroll down to know what is there. As you can Training & Career is highlighted in orange, this is call a TOC rollover method. As your curser moves over the selection, it will be highlighted.
The great thing about this page, is the way HCM highlight Hot News. This is the home page of the HCM wiki, as soon you open this page you can see what is hot and not,
The last thing on this page I would like to point out is the tagging section, a widgit has been used to create this section. It provides up to date information on what is being tagged by hcm in Dogear. You can customize the widgit for the are
As you can see here under the Oracle wiki, they have a great page on Oracle wiki Help and Guidelines. It is important to include a page with wiki guidelines in every wiki since there will be multiple contributors per wiki.
Sandboxes provided contributors a place they can learn and practice without the worry of messing up. It is nice to provide examples like the one here in the HCM wiki for them to start with.
