Space Index
|
|||||||||||||||||||||||||||||||
0-9 |
APage: Accessing the dashboard use caseDescription
To perform any of the autoring and administration activiities, the user must reach his Dashboard first. There are two obvious ways of doing this.
If the site displays the Login portlet somewhere, users are able to authenticate themselves. If they are Site team members for the current site ...
Page:
Accessing the site use case
Description
This is a basic scenario for site browsing start.
User types in a Site address Domain name or clicks on a URL in the search results. The typed in address needs to be as simple as possible and must correspond to the site structure. Preferably this is the path to the page excluding the main ...
Page:
Active components
Page: Adding users to workgroup use case Description
Adding an user to a workgroup is an easy process, but choosing the right user is a trickier one, especially if the System has hundreds or thousands of them. The subject is discussed in more detail in Browsing users use case.
default categories of users ...
Page:
Anonymous user role
special identity that is assigned to all web surfers that have not logged in to a Cyklotron system.
View permission on a part or all of site's pages may be granted to Anonymous user thus letting non logged in people to browse them
Page:
Applications documentation
Here you can find documentation of the applications that are bundled in Cyklotron2 product
Page:
Assigning domain names to a site use case
Description
Assigining Domain names to Sites is restricted to the System administrator because it involves administrative tasks outside the scope of the System, like configuring virtual servers in Tomcat and Apache.
Any number of domain names may be assigned to a site, but only the primary ...
|
||||||||||||||||||||||||||||||
BPage: Bookmarking the page use caseDescription
The scenario for bookmarking the page.
User bookmarks the page - the properties needed to bookmark the page:
the title of the page, preferably the path to the page consisting of:
the name of the site and path to the page built of page titles and separator character,
example: Site name : 1st ...
Page:
Breadcrumbs
path marked with) breadcrumbs is a visual hint about user's current location in the System, by spelling out all the steps taken from an intial location, and provides a shortcut way of backing of to any of these previous steps.
Two distinct kinds of breadcrumbs ...
Page:
Browse mode
Browse mode is a site presentation mode for logged in users with administrative permissions. There are following browse modes defined:
Site browsing mode
Portlet administration mode
Emergency browsing mode
Time travel mode
Resource export mode
Resource import ...
Page:
Browse mode toolbar
Description
Every Browse mode will have a custom toolbar containing actions, filters, etc. This will be used to simplify new browse mode and Site browsing toolbar creation.
Mockups
Site browsing screen
Use cases this UI element is involved in
use ...
Page:
Browsing organizations use case
Description
The System administrator needs to be able to browse the list of all Organizations registered in the system.
The following information should be dispalyed for each organization
identifier
full name
date registered
number of owned sites
number or team members
The list should ...
Page:
Browsing sites by organization administrator
Description
The Organization administrator needs to be able to browse all the Sites owned by the Organization.
The following information should be displayed for each site:
site identifier
site's primary Domain name
site's creation date
Other information that we may or may ...
Page:
Browsing sites by system administrator use case
Description
The System administrator needs to be able to browse all the Sites present in the system.
The following information should be displayed for each site:
owner Organization identifier
site identifier
site's primary Domain name
site's creation date
Other information ...
Page:
Browsing users use case
Description
In many situations, it is necessary to pick a user of the system. Since there may be many of them (think thousands), it is critical that they can be filtered, sorted, grouped and searched effectively.
Here are a few example user filters:
All Registered users
All System ...
Page:
Browsing workgroup members use case
Description
A list of current workgroup members should be displayed. The following information about a worgroup member should be visible:
identifier
full name
For each user except users appointed to Workgroup administrator role a means for invoking Removing users from ...
Page:
Browsing workgroups use case
Description
Workgroup administrator should be able to browse all workgroups in his scope:
System administrator - all System workgroups
Organization administrator - all Organization workgroups in his appointed Organization
Site administrator - all Site workgroups in his appointed ...
|
CPage: Calendar technical documentationCalendar - Technical documentation
Application packaging
Calendar application is packaged in following java packages:
org.cyklotron.calendar
net.cyklotron.modules.actions.calendar
net.cyklotron.modules.components.calendar
net.cyklotron.modules.views.calendar
Configuration options
The calendar manager component need to be present in main container configuration.
<component class-key="org.cyklotron.calendar.CalendarManager"
class ...
Page:
Categorization concern
Description
Various Resources in the Site need to be categorized. Often resources of different types belong to one category.
Resource class that opts in for categorization will have apropriate links displayed in the Uniform resource navigation screen.
TODO is it a cross cutting concernt at all ...
Page:
Clipboard
Clipboard provides a commonly understood mechanism for moving resources around.
Different clipboard operations may be available on the selected resource, depending on the users's Privileges, and the current contents of the clipboard (each Resource Class has specific requirements with respect to the location where ...
Page:
Clipboard concern
Description
Clipboard with cut/copy/paste operations is a convinient and commonly understood mechanism for moving and copying resources.
A Resource class that opts in for clipboard operations must provide helper classes that are able to determine valid paste locations, and perform resource copying ...
Page:
Create your own application - Tutorial
Create your own application for Cyklotron 2
Here we will guide You through the process of creating new application in Cyklotron 2 environment. We choose simple forum application as an example.
Assumptions
one forum per High ...
Page:
Creating a site use case
Description
While crating a Site the following information needs to be entered by the System administrator
site identifier (unique across all sites created in the sytstem)
owner Organization picked from a list
site primary Domain name
user to be appointed to Site ...
Page:
Creating a workgroup use case
Description
The following information needs to be entered while creating a workgroup:
identifier (must be unique across all workgroups in the same scope)
description
zero or more users appointed to Workgroup administrator role, picked from apropriate list of:
users in System ...
Page:
Creating an organization use case
Description
When registering a new organization the System administrator needs to enter the following information:
organization identifier (unique across all registered organizations)
full name of the organization
contact details for the organization (postal address, telephone, fax)
user appointed ...
Page:
Crosscutting concerns
Security concern
Search concern
Categorization concern
Clipboard concern
Workflow concern
Page:
cyklotron2 i18n working sheet
temporary page for tracking progress in internationalization of C2 templates.
common/cms.vt
common/componentConfig.vt
components/ComponentWrapper.vt
R
components/commons/CmsNodeProperties.vt
R
components/commons/Empty.vt
components/commons/Result.vt
components/dashboard/BlankProperties.vt
R
components/dashboard ...
Page:
cyklotron2 mailman integration
Use cases
administration
a forum is created
a forum is deleted
a forum is renamed
moderation flag is changed on the forum
subscriptions through email policy on the forum is changed
moderation
administrator checks pending messages queue in a moderated forum
administrator accepts / rejects ...
|
||||||||||||||||||||||||||||||
DPage: DashboardDashboard is the starting point for Site auhtors, Site adminsitrators, Organization administrators, and the System administrator.
See Dashboard screen for UI design and Accessing the Dashboard use case
Page:
Dashboard screen
Description
Dashboard is the screen that the Site authors see after they log into their account.
The dashboard displays links to Uniform resource navigation screens for different High level resources, and Dashboard portlets.
Mockups
Dashboard screen OpenOffice draw mockup ()
Use cases ...
Page:
Deleting a site use case
Description
This operation completely and irrecoverably (except restoring database and sandbox directory from backups) deletes Site contents and associated information. Extreme caution should be exercised. To prevent data loss two level confirmation in the UI will be required.
In most situations ...
Page:
Deleting a workgroup use case
Description
This operation irrecoverably deletes a workgroup. To avoid data loss two level confirmation in the UI is required.
Features that introduce this use case
Workgroup administration feature
Roles involved in this use case
System administrator role
Organization administrator role ...
Page:
Deleting an organization use case
Description
In order to avoid massive data loss, it will be possible to delete only those organizations that have no existing sites. Additionaly a double confirmation in the UI layer will be required.
Features that introduce this use case
System administration feature
Roles involved in this use ...
Page:
Dependency checklist
page is used by the developers of Cyklotron to track the versions of different software packages in order to make sure we are using the latest stable versions.
The latest released versions were checked on June 10th 2004 by
groupId : artifactId
url
required
released ...
Page:
Developer Guide
Preparations
To build cyklotron, you need to install Apache Maven first. We strongly recommend using the most recent stable version (1.0-rc3, at the time of writing). Building with older version is possible but requires tweaking configuration files, and we will not provide ...
Page:
Document
Document is a piece of information that establishes the primary content of the page. Each document belongs to exactly one Document type defined in the Site. A document have 1-1 relationship with a Page, but it can be easily copied or moved between pages, possibly across site's ...
Page:
Document editing feature
Description
The screen for editing Document contents will be dynamically generated according to Document type definition. Moreover, the definition may contain fields that are optional or/and repetitive. This adds another level of "dynamics" to the editor. It has to either reload the page each time a field ...
Page:
Document field
Document filed is an an item of information confined in a Document.
The following field types are planned at this point:
plain text field
wiki formatted text field (possibly using Radeox)
HTML formatted text field (see WYSIWYG HTML ...
Page:
Document metadata
Metadata for the Document is contained in its respective Document fields.
Document fields may declare metadata mapping. If such mapping is present, the value of the field will be emmited in the <head> section of the Page in the apropriate <meta> tags.
Following http://dublincore.org recommendations is possible, by setting ...
Page:
Document type
Document type determines the structure of the information confined in a Document.
The definition of the document type is tree structure composed of Document field nodes.
Documents are subject to Skinning. A HTML template determines the markup that will be ultimately shown to the site visitor. Upon creation of the document ...
Page:
Domain name
Domain names are used to select a correct Site, when an browser makes an HTTP request to the server. A one-to-many relationship exists between sites and domain names
|
EPage: Editing organization properties use caseDescription
The following information about an organization may be changed:
full name of the organization
contact details for the organization (postal address, telephone, fax)
user appointed to the Organization administrator role, picked from the Registered users list.
Features that introduce ...
Page:
Editing site properties use case
Description
The following information may be changed for a Site by the administrators:
primary domain name, picked from the list of Domain names assigned to this site
user appointed to the Site administrator role, picked from the Organization team member list
Features that introduce ...
Page:
Editing workgroup properties use case
Description
The following information may be changed for a workgroup:
description
users appointed to Workgroup administrator role, picked from apropriate list
users in System administrator role for System workgroups
users in Organization team workgroup for Organization workgroups
users in Site ...
Page:
Email verification
Verification if the user controls an entered email address can be done as following:
random but unique cookie string is generated
the cookie is stored in the system, keyed by address
a probe message containing the cookie is sent
the user clicks on link contained in the message ...
|
||||||||||||||||||||||||||||||
FPage: FeaturesSystem administration feature
Organization administration feature
Site administration feature
Workgroup administration feature
User management feature
Site authoring feature
Site structure management feature
Site layout management feature
Site appearance management feature ...
|
GPage: Getting involvedUsefull informations for everybody who wants to join the development team.
How to contribute, repository access, mailing list
Page:
Granting application access rights for a site
Description
System administrator should be able to control which optional applications are available within a site. Details need to be worked out.
Features that introduce this use case
System administration feature
Roles involved in this use case
System administrator role ...
Page:
group membership management
Discussion of NUCYKLO-83
Current implementation
The security system of Cyklotron 2 addresses well the need to control what users that are the members of the organization, or specific site team/workgroup can and cannot do. It also addresses the need of controlling what anonymous, or registered ...
Page:
Group owner guide
Group owner guide.
The assumption is that your have already an account in Cyklotron2 system and you are owner at minimum one organization i.e. pablo.
So when you log in you should see dashboard looks like:
Clicking the pin ...
|
||||||||||||||||||||||||||||||
HPage: High level resourcethree kinds of high level resources in Cyklotron2 system.
System resource
Organization resources
Site resources
To perform autoring/administrative operations an user navigates form his Dashboard to one of high level resources, which determines the context ...
Home page:
Home
What is it all about?
Cyklotron2 is a content management system - an application for easy development and management of websites.
Cyklotron2 project is sponsored by major player in the Non Governmental Organizations domain, and thus it's primary focus is serving the needs of NGOs, but the developed software ...
Page:
Home page
Home page of a Site is the root Page in it's Public space
|
IPage: Included workgroupworkgroup may include other workgroups. An included workgroup recieves all the Privileges of the including workgroup.
A Workgroup administrator can include/exclude other groups from the group he manages
Page:
Installation Guide
Here are instructions for running Cyklotron2 starting with a plain Linux machine without development tools installed.
Note! you need root privileges to create directories under /usr/local directory.
1. Installing Java SDK
Go to http://java.sun.com ...
Page:
Issue tracking
strongly recommended to submit bugs and feature requests to Jira issue tracker:
http://objectledge.org/jira/browse/NUCYKLO
Remember to search the existing issues to avoid duplicated entries.
Top 20 open issues
|
||||||||||||||||||||||||||||||
J |
K |
||||||||||||||||||||||||||||||
LPage: Logging into the system use caseDescription
This is a scenario for logging into the system.
There are at least two ways of getting to the login form.
While browsing a public site, user may use embedded Login portlet.
By typing in administrative interface URL in the browser, user will be presented a login form.
User ...
Page:
Low level resource
low level resource is an ordinary Resource attached below a Medium level resource
The medium/low level resources can be browsed using Uniform resource navigation screen, an their properties may be viewed using Resource properties view ...
|
MPage: Mailman integrationInstall and configure mailman with xml-rpc functionality
Be sure you have python installed
Get mailman sources from http://mailman.sourceforge.net/download.html
Get appropriate patch with xml-rpc support i.e. Mailman integration
Apply patch
Build ...
Page:
Medium level resource
Medium level resources correspond to the different modules available within a High level resource.
For the System high level resource these may include:
user administration
organization administration
site administration
categorization
reports and statistics
For the Organization high level resource ...
|
||||||||||||||||||||||||||||||
N |
OPage: OrganizationOrganizations are entities that group multiple Sites together. They usually represent a real world organization that operates the website. From System administrator perspective, they organize the information in site list view, and can possilbly be used for accounting purposes mapping a site to a client ...
Page:
Organization administration feature
Description
This feature groups together all the self-service tasks Organization administrators are able to perform withing the System.
Roles involved in using the feautre
Organization administrator role
Use cases for the feature
Site management
Browsing sites by organization administrator ...
Page:
Organization administrator role
Description
Each Organization is assinged and Organization administrator upon creation. Adminstrator's resonsibilities include creating and deleting Organization workgroups, adding and removing users to these workgroups and assigning privileges to workgroups. Note that the organization administrator is not allowed to create and delete Sites on his ...
Page:
Organization team
Organization team is the primary Workgroup of an Organization. All users added to the Site team workgroups of all of the organization's Sites are implicitly added to the Organization team. Organization administrator may add or remove users from this workgroup as necessary
Page:
Organization workgroup
Organization workgroup is associated with an Organization. It is managed by the Organization administrator. Each organization has at least one workgroup - the Organization team. Organization administrator may create additional workgroups as needed. A workgroup of this kind can be used for sending notifications to all ...
|
||||||||||||||||||||||||||||||
PPage: PageSite content visible to web sufers is divided into pages. A page is associated with a Page layout family, a Document, and settings for each Portlet slot present in the page: the type of portlet displayed, portlet template variant (used to render the portlet as HTML) and all ...
Page:
Page layout
Each page is associated with a page layout, through it's assigned Page layout family and Page nesting depth. A layout determines the number of the Portlet slots on the page, and their respective names. It determines the page layout template that will be used to render the page as HTML
Page:
Page layout family
Page layouts are grouped in familes. A family is a set of Page nesting depth : Page layout pairs. If a family does not specify a layout for a specific nesting depth, the layout with the greatest nesting level, lesser than the requested level is used for rendering the page
Page:
Page nesting depth
number of the ancestor pages in the site structure tree for a specific page. Thus, the home page of the site has nesting depth of 0, it's immediate children have depth of 1, it's "grandchildren" of 2 and so
Page:
Page validity time
Page visibility may be limited temporaly in the following way:
If a validity start date is defined, the page is not visible to the Site visitors before the given date.
If a validity end date is defined, the page is not visible to the Site visitors after the given date.
The page ...
Page:
Passive components
Page: Personal information number of information items about an user is stored within the system.
The basic information is:
the login identifier
the password (or rather it's message digest)
surname
familiy name.
email addresses may also be interesting:
to address (used for sending mail to the user ...
Page:
Platform Core documentation
Page: Pluggable extensions feature Description
The System administrator should be able to enable or disable optional extension packages.
Roles involved in using the feautre
System administrator role
Use cases for the feature
use case]
Active components that implement the feature
component]
UI elements for this feature ...
Page:
Portlet
visual component that can be placed on a Page, in one of it's Portlet slots
Page:
Portlet management feature
Description
This feature groups together activiteis performed by the users in Site author role on the Portlets embedded in the Page's Portlet slots defined by the relevant Page layout.
Roles involved in using the feautre
Site author role
Use cases for the feature
use ...
Page:
Portlet slot
Page layout may contain one or more slots in which Portlets are placed. Portlet slot is uniquely named across a Page layout
Page:
Post installation application tuning
1. Short dashboard administration panel introduction.
After the installation finished successfully you can start to work with Cyklotron2 system.
Administrator account comes in default initial data. Login is root and password is 12345.
Remember to change default administrator ...
Page:
Privilege
Privilege determines an user's ability to view the Resource in a certain way, or perfrom an activity upon it.
Privileges may be created and deleted by the user in the Site administrator role, based on the Privilege templates associated with the resource's Resource class.
Privileges may ...
Page:
Privilege inheritance
Certain Privileges on a resource may be inherited by it's child resources - for example, if Anonymous user role is granted view recursive privilege on a Home page of a Site, the anonyoums users are also allowed to view all sub pages of the site (that are visible due to Workflow ...
Page:
Privilege template
privilege template is associated with a Resource class. The Site administrator may create Privileges for a specific resource, based on the privilege templates available.
A template specifies privilege name, description and wether the created permission will be inherited.
Usually only a small number of privileges ...
Page:
Project
Project sections
Features distinct features of the system.
Roles different roles of the users of the system.
Use cases different activities of the users of the system.
Active components are functional modules that provide system's functionality.
Passive components constitute the data model of the system ...
Page:
Public space
Public space of the site contains Pages that are visible to the visitors of the Site
|
Q |
||||||||||||||||||||||||||||||
RPage: Registered user roleDescription
All users that have a valid account in the Cyklotron2 system and have logged into it, have the Registered user identity.
Features this role is using
feature]
Use cases this role is involved in
use case
Page:
Removing users from workgroup use case
Description
It should be possible to remove each of the workgroup members from the workgroup except the one appointed to Workgroup administrator role. This one may be removed from the workgroup only while Deleting a workgroup use case.
Features that introduce this use case ...
Page:
Resource
Resources are building blocks of Sites. Many types of resources exist (see Resource class). Certain types of resources are grouped together in tree structures (most notably Pages). Other resources are grouped as unordered or ordered lists attached to a common parent ...
Page:
Resource class
Resource belongs to exacly one of the predefined resource classes.
A resource class determines the administrative operations available, and presentation techniques for the resource.
The resource class defines the Privilege templates, that specifiy what priviletes can be created for the resources of this class
Page:
Resource class definition
Resource class definition is a part of System registry that stores all the usefull meta information about Resource class i.e.:
skinnable resource icon
aggregation copy action
aggregation update action
is categorizable
Security helper class
etc
Page:
Resource state
Resource that is subject to a Workflow assumes various states during it's lifetime.
The obvious states for a resource are:
new
accepted
published
expired
hidden
The ways in which the state may be changed is defined by the Resource state transitions that are part of the Workflow definition.
The state is related ...
Page:
Resource state transition
Workflow for a Resource class is defined in terms of Resource states and transitions between them.
The transitions come in two flavours, and have the following additional properties
Guarded transitions: are performed manually by an appoited users.
The required Privilege
The action that must be executed ...
Page:
Restricted space
Restricted space contains pages that are visible to Site team members only. It is an intermediate area between a Workspace that is visible to single user only and the site's Public space
Page:
Roles
System administrator role
Organization administrator role
Site administrator role
Site author role
Site visitor role
Workgroup administrator role
User role
Registered user role
Anonymous user role
|
SPage: SandboxUsing mod_rewrite with Cyklotron
Page:
Screenshots
Administration dashboard view - both English and Polish locale version:
english version (oryginal size: Screenshots):
and after changing personal preferences to Polish (oryginal size: Screenshots
Page:
Search concern
Description
The users need the ability to search the System for Resources, using full text queries.
A Resource class defines wether it's resources are serchable or not. If yes, a helper Java class that is able to retrieve data from resource and convert it to the format required by the indexer ...
Page:
Search feature
Description
This feature groups togeter activities performed by the Site admnistrator to set up search facility for the site, and by the Site visitor that use this facility.
Roles involved in using the feautre
Site administrator role
Site visitor role
Use cases for the feature ...
Page:
Security Concern
Security
Page:
Security helper
delegate object that contains security logic for a Resource class.
The method implemented by Security helper:
boolean canAddChild(Resource resource, Subject subject)
boolean canModify(Resource resource, Subject subject)
boolean canRemove(Resource resource, Subject subject)
boolean ...
Page:
Security management feature
Description
This fature groups together activities performed by various administrators to control access to the Resources using Privileges.
Roles involved in using the feautre
System administrator role
Organization administrator role
Site administrator role
Use cases for the feature
use ...
Page:
Signup for account use case
Description
In systems intended for intranet use, user account creation is reserved to the System administrator role.
In the public websites that support user registration the anonymous user should be able to create an account for himself without any human interaction. After ...
Page:
Site
Single Cyklotron2 System may host multiple sites. Each site has a Site administrator, an associated Site team Workgroup, and a Public space, containing at least one Page. Each site can define it's own Page layout ...
Page:
Site administration feature
Description
This feature groups together all the self-service tasks Site administrators are able to perform within the System.
Roles involved in using the feautre
Site administrator role
Use cases for the feature
Site management
Viewing site properties use ...
Page:
Site administrator role
Description
Site administrator may create and delete Workgroups, optionally designate a Workgroup administrator, add and remove users from workgroups. The site administrator may also grant privileges to workgroups.
Features this role is using
feature]
Use cases this role ...
Page:
Site appearance management feature
Description
This feature groups together operations performed on Site's Skins.
Roles involved in using the feautre
Site author role
Use cases for the feature
use case]
Active components that implement the feature
component]
UI elements for this feature
UI element ...
Page:
Site author role
Description
Site author is an Registered user, that is a member of a Site team, and has been assigned some Privileges that allow him to create new Resources in the site and/or modify existing ones.
Features this role is using
Site authoring feature
Use ...
Page:
Site authoring feature
Description
This feature gruoups together different acitivities performed by users in Site author role.
Roles involved in using the feautre
Site author role
Use cases for the feature
Accessing the dashboard use case
Browsing site resources use case ...
Page:
Site browsing feature
Description
This features groups the activities of users in Site visitor role upon Site's Public space.
Roles involved in using the feautre
Site visitor role
Use cases for the feature
use case]
Active components that implement the feature
component]
UI ...
Page:
Site browsing screen
Description
Site browsing screen is a screen showing site contents. It may display a Site browsing toolbar on top of the screen, if user browsing the site is logged in and is a team member of the viewed site.
Mockups
Site browsing screen
Use cases this UI ...
Page:
Site browsing toolbar
Description
Site browsing toolbar is a component displayed on top of a site contents on Site browsing screen. Only logged in site team members may see the toolbar.
Toolbar contains following elements:
user information with logout button
browse mode ...
Page:
Site customization metric
Site customization metric is used to determine how much work went into customizing the site's appearance.
It is a comparative only quantity, presented to the users as a percentage of the metric value of the top-ranked site.
The value of the metric is computed the following way:
scm = <skins ...
Page:
Site layout management feature
Description
This feature groups together operations performed by users in the Site author role on Site's Page layouts, Page layout families and layout-related properties of the Pages.
Roles involved in using the feautre
Site author role
Use cases for the feature ...
Page:
Site statistics and accounting information
Here are a few ideas of the statistical information about a Site that may be of intrest to the users in System administrator role, Organization administrator role as well as Site administrator role. They could also be used as a basis of computing the usage fees by the entity operating the System ...
Page:
Site structure management feature
Description
This feature groups together various operations performed by the users in Site author role on the Pages in the Site's Public space.
Roles involved in using the feautre
Site author role
Use cases for the feature
use case]
Active components that implement ...
Page:
Site team
primary workgroup of a Site. Being a member of that group an user is granted the permission to access the administrative interface of the site
Page:
Site visitor role
Description
Site visitor is an Registed user or Anonymous user that browses the site's public interface.
Features this role is using
Site browsing feature
Use cases this role is involved in
use case
Page:
Site workgroup
Site workgroup is associated with an Site. It is managed by the Site administrator. Each organization has at least one workgroup - the Site team. Site administrator may create additional workgroups as needed. Workgroup of this kind are typicaly used to assign access priviletes ...
Page:
Skins
Skins control the appearance of the site to the visitors. A HTML template is defined for each layout, and each portlet, along with neccessary media files (images, animations) and sylesheets. Multiple appearance variants may be defined for each portlet withn a site
Page:
Space index
index}{index
Page:
System
whole Cyklotron2 installation deployed as a web application in an J2EE application server. Multiple Sites can be hosted in a single Cyklotron2 system
Page:
System administration feature
Description
This feature groups together all the tasks that the System administrator performs.
Roles involved in using the feautre
System administrator role
Use cases for the feature
Organization management
Browsing organizations use case
Viewing overall organizations information and statistics ...
Page:
System administrator role
Description
Also refered to as the root user. The user who has complete admistrative privileges over the whole Cyklotron2 System. He is able to create and delete sites, manage System workgroups and reset user passwords.
Features this role is using
feature ...
Page:
System registry
central point of the system. It stores system information about all Applications deployed in the system and used Resource classes
Page:
System workgroup
system System workgroup is not associated with any System workgroup. The System workgroup is responsible for adding/removing users from them, and granting privileges to these workgroups
Page:
Systemwide statistics and accounting information report use case
Description
The system administrator should be able to download a spreadsheet containing a systemwide report of statistics and accouting information in CSV or XLS (http://jakarta.apache.org/poi/hssf/) format.
The report would contain Site statistics and accounting information for each Site, grouped ...
|
||||||||||||||||||||||||||||||
TPage: Technical referenceHere you can find technical documentation and developer's manual for Cyklotron2 system
Page:
Terms and definitions
Anonymous user role
B
Breadcrumbs
Browse mode
C
Clipboard
D
Document
Document field
Document metadata
Document type
Domain name
E
Email verification
H
High level resource
Home page
I
Included ...
|
UPage: UI elementsScreens
Dashboard screen
Uniform resource navigation screen
Site browsing screen
Components
Dashboard components
Site browsing toolbar
Browse mode toolbar
Wizards
Page:
Uniform resource navigation screen
Description
The resource navigation screen always works in the context of a High level resource, which is the System, an Organization or a Site. The users navigates to the resource navigation screen for a particular high level resource from his Dashboard.
The resource navigation screen ...
Page:
Use cases
System administration feature
Organization management
Browsing organizations use case
Viewing overall organizations information and statistics use case
Systemwide statistics and accounting information report use case
Viewing organization properties use case
Viewing organization ...
Page:
User Guide
Here you can find information how to get started with Cyklotron2
Page:
User management feature
Description
Roles involved in using the feautre
Anonymous user role
Registered user role
System administrator role
Workgroup administrator role
Use cases for the feature
Browsing users use case
Viewing user's profile use case
Signup ...
Page:
User role
Description
User is the generic identity assigned to all users, both registered and anonymous.
It can be used to assign certain privileges to all users.
Features this role is using
feature]
Use cases this role is involved in
use case
Page:
Using mod_rewrite
Guide to cyklotron2 to produce short, nicely looking URLs.
Configure a virtual server in apache2:
<VirtualHost *:80>
ServerName DOMAIN
DocumentRoot DATA_DIR_PATH
CustomLog /var/log/apache2/DOMAIN-access.log combined
ErrorLog /var/log/apache2/DOMAIN-error.log
RewriteEngine on
RewriteRule ...
|
||||||||||||||||||||||||||||||
VPage: Viewing organization properties use caseDescription
An information summary screen shoul be available for each Organization.
The following information should be displayed on the screen:
identifier
full name of the organization
contact details for the organization (postal address, telephone, fax)
user appointed to the Organization administrator role ...
Page:
Viewing organization statistics and accounting information use case
Description
The statistics and accounting information should display sums of Site statistics and accounting information over all sites defined for the organization.
Features that introduce this use case
System administration feature
Roles involved in this use case
System administrator role ...
Page:
Viewing overall organizations information and statistics use case
Description
An administrator should be able to a summary of information about Organizations registered in the System.
Here are a few ideas for the information items to be displayed:
number of organizations
total number of team members
average number of sites per organization
average number ...
Page:
Viewing site properties use case
Description
Administrators should be able to view information about a Site.
The following information should be dispalyed:
site identifier
site's primary Domain name
site's creation date
user appointed in the Site administrator role
number of Site team members ...
Page:
Viewing site statistics and account information use case
Description
The page should display Site statistics and accounting information for the selected site.
Features that introduce this use case
System administration feature
Organization administration feature
Site administration feature
Roles involved in this use case
System administrator role ...
Page:
Viewing user's profile use case
Description
Workgroup adminstrators, and the system administrator should be able to view users profile information.
The extent of information shown (for example email addresses, telephone numbers and postal contact addresses) depends on the Privileges of the user.
Features that introduce this use case
Workgroup ...
Page:
Viewing workgroup properties use case
Description
The following information about a wokrgroup should be displayed:
identifier
description
appointed Workgroup administrator
date of creation
number of members
number of Included workgroups
Features that introduce this use case
Workgroup administration feature
Roles involved in this use case ...
|
WPage: WorkflowWorkflow is a set of Resource states, and Resource state transitions that a Resource is subject to.
Resources of selected classes have defined workflow automaton. Such resources are visible to site visitors only when they are in published state. Changing resource state from new to published ...
Page:
Workflow automaton
defines the set of states and transitions for a particular Resource class. The automaton can be defined for all resources from whole system or can be scoped for only the particular organisations or even sites resources.
In case the organisation or site that had used the system automaton ...
Page:
Workflow concern
Description
Certain resources need to pass an acceptance process in order to be published. Albeit the differences in the process flow the mechanism based Resource states and Resource state transitions is common, and the UI support representation should be uniform across different applications ...
Page:
Workgroup
workgroup is used for security management. A workgroup may be associated with a Site, and the Site administrator may create any number of groups. System workgroups are not associated with any site and are managed by the System administrator. Each site has at least one initial workgroup ...
Page:
Workgroup administration feature
Description
This feature groups together all the tasks that Workgroup administrators perform in the System.
Roles involved in using the feautre
Workgroup administrator role
Use cases for the feature
Browsing workgroups use case
Creating a workgroup use case
Viewing workgroup ...
Page:
Workgroup administrator role
Description
A workgroup administrator may add and remove users from his assigned Workgroup.
Features this role is using
feature]
Use cases this role is involved in
use case
Page:
Workspace
workspace is an users' personal storage area for documens an files he is working on. Not all registered users own a workspace - a browse workspace permission is reqiuired, that is by default granted to all site team workgroups
Page:
WYSIWYG HTML editing feature
Description
Is a sub-feature of Document editing feature that applies to HTML formatted Document fields.
A WYSIWIG visual editor component will be displayed on the document edition page for each of the HTML formatted fields present.
The user should be able to control these attributes of the text ...
|
||||||||||||||||||||||||||||||
X |
Y |
||||||||||||||||||||||||||||||
Z |
!@#$ |
||||||||||||||||||||||||||||||
Labels: