CIP A 2003 XIX th International Symposium, 30 September- 04 October, 2003, Antalya, Turkey 
the mainly used browsers by the community and the visitors. To 
get individual information’s on this the log file and the web 
statistic is good point to start. 
1.4 General usability aspects 
As discussed before there might be some limitations. Most of 
them are easy to eliminate, just by switching to another provider 
or another browser. Keep in mind that most users of the internet 
uses more than one browser. More important in this context is 
the usability of the CMS. This means, the system should be easy 
to handle for the user and the administrator. Only if the user 
feels good by using the system the website and the community 
will grow and expand. Thus the CMS should offer an user 
interface that is easy to understand and to handle. 
Because of the opportunity to manage different user rights it 
must also be possible to offer the user different interfaces with 
options concerning to their user rights. All this must be easily 
set up by the administrator of the system. Furthermore the 
administration of the CMS must be flexible enough to adapt 
changes in the structure or different requirements of the user 
groups. This leads to the question of organisational aspects of a 
CMS. 
2. ORGANISATIONAL ASPECTS 
2.1 Basics 
CIPAWEB 
Tipafriend 
f □ N «“* 8- Evnts 
0 The Framework 
| ' 0 Latest news 
□ -0 Organisation 
i 0 The Framework 
ì 0 The Structure 
ßj-0 CIPA Boards 
0-Q Working Groups 
0 Working Group 1 
; Q| Working Group 2 
0 Working Group 3 
•; 0 Working Group 4 
i 0 Working Group 5 
0 Working Group 6 
0-0 Working Group 7 
0 Hl Image management 
: Ï-Q Image acquisation 
0-0 Metric caméras 
i—R) Next level 
; Hi '•*' 
i 0 Working Group 8 
-0 Search 
Fig.2 
In figure 2 you can see a screenshot of the structure from the 
CIPA website in the CMS. Especially in the section “Working 
groups” you see how the organizational structure is 
implemented 1:1 to the CMS. In the browser this looks as 
shown in figure 3. 
Wot-klng Groups 
► Working Group 1 
► Working Group 2 
*• Working Group 3 
► Working Group 4 
► Working Group 5 
► Working Group 6 
► Working Group 7 
► Working Group 8 
Search 
In the context of the usability of a CMS it is important to check 
out the structure of the organization which plans to use a CMS. 
While in commercial organizations often a specialized group of 
employees or a team with good skills in HTML or other 
programming languages is responsible for the CMS, scientific 
communities are often not specialized on this. Sure there is a 
coordinator or an administrator for the web pages, but he has to 
put all the stuff together and adapt and edit it, so it will fit to the 
web design. This is one reason why you often find sides with so 
called “island solutions” where every user group has it’s own 
layout which seldom fits to the layout of the whole community. 
Thus the website appears to the visitor as “mixed pickles”. The 
click into the bookmark list is far away. 
So, what is to do to give the community a professional closed 
look or the so called “community identity” as described above? 
First of all we have to check the organization structure of the 
community and try to adapt this into the CMS. By doing this the 
organization, the responsibilities, the user groups and the 
sections will correspond with the layout of the website. Thus 
the user realizes the community structure just by a look on the 
navigation bar. So, it is possible for him to easy figure out 
which part of the organization is of special interest for him. 
To achieve this goal sometimes the community has to rebuild 
her structure in some sections to bring up that closed look to the 
visitor. 
Fig. 3 
The great advantage of the corresponding structures takes place 
when there is for example a change in the organizational 
structure. Because what you see in figure 3 and 4 is 
automatically generated by the CMS, it is easy to adapt changes 
in the under laying organizational structure to the website. Just 
reorganize the page tree in the CMS so it fit’s to the 
organizational structure! 
; OrOu» 9 
) Task Oroup* 
Project* I« (xamphf 
} link» * Raportr 
\ 8th« CIPAWfB 
1 
Y The Framework 
► Latest news 
y Events 8t Meetings 
► Symposia 
I 
I 
► The Framework 
► The Structure 
► CIPA Boards 
V/oH<lr»g Groups 
► Working Group 1 
y Working Group 2 
► Working Group 7 
Projects & Examples 
Links & Reports 
Search the CIPAV/EB