Biomedical Engineering Reference
In-Depth Information
Creating a single 'top' category for all categories associated with forms
makes it possible to separate semantic content from other pages such
as portals or index pages. This is useful when trying to get an accurate
count of wiki pages.
Identifying a core set of semantic properties common to all categories is
useful to simplify reporting and navigation between pages.
Description: a short summary of what a page is about.
Topics: tags to defi ne a fl exible classifi cation of content inside pages
(examples of topics are 'chemistry', 'biology', 'sequencing').
Scope: tags to indicate for whom a page is relevant (examples of scopes
are individuals, teams, functions, companies).
In addition to the core set, a few standard properties can help overcome
some limitations of Semantic MediaWiki.
Page title (text): pattern matching in semantic queries is allowed only
for properties of type text. Creating a text version of the page title as
a property allows queries such as 'all pages starting with the letter A',
which can be useful for creating a table of contents or alphabetical
indices.
Class name (text): creating a redundant property for the category
of pages allows running of queries on a single category, without
inheritance.
Related to: it is useful to defi ne a 'catch all' property on certain pages
to capture relationships that have not yet been formally defi ned.
Regular reviews of values provided by users for this property are useful
to identify properties that should be made more explicit inside forms.
￿ ￿ ￿ ￿ ￿
16.3.7 Simplify the user experience
Choosing the right mix of extensions is not enough to ensure participation.
In order to be successful, an Enterprise Encyclopaedia has to fi nd a place
in the fl ow of a casual user, which means it has to fi t within the ecosystem
of tools they use daily to fi nd and share information. Customisation of
the visual theme of the wiki (its skin) is necessary to allow content to be
embedded in remote sites, viewed from mobile devices or printed if
necessary. For example, the interface needs to provide options to share
content using email, forums and whatever micro-blogging platform is
used internally. By providing options to share content from the wiki to
 
Search WWH ::




Custom Search