INSTALL (Debian Lenny)
======================
1. Requirements

	pylons
	------
	apt-get install python-pylons 
	(>= 0.9.7, can be found in lenny backports) 
	apt-get install python-psycopg2
	apt-get install python-pybabel

	libformed
	---------
	wget \
	http://wald.intevation.org/frs/download.php/710/libformed_0.1.tar.gz
	tar xzvf libformed.tar.gz
	cd libformed
	python setup.py install

	libmpuls
	--------
	wget \
	http://wald.intevation.org/frs/download.php/705/libmpuls_0.4.4.tar.gz
	tar xzvf libmpuls_0.4.4.tar.gz
	cd libmpuls_0.4.4
	python setup.py install

	mpuls
	-----
	svn checkout \
	https://svn.wald.intevation.org/svn/mpuls/wasko/branches/2.0 mpulsweb

2. Installation

	The server can be run in 3 ways. In general the three ways differ in
	the way the user credentinals to connect to the database are provided.
	In general the crededtionals can be provided in a configuration file,
	or within the SSL-Client certificate. The latter needs a apache server
	involved which can extract these information from the SSL-Client
	certifiacte. If a database name is configured in the "ini" file it
	will be taken for the connection. Leave the databasename blank, to let
	the serve look for the credentionals in the HTTP-Headers.

	2.1 Standalone paster server
	The credetionals are provided in the "ini" file.
	
		cd mpulsweb
		cp development.ini wasko.ini
		# Configure wasko.ini for for needs. See details below
		paster serve wasko.ini
		-> Server is up and running. :)

	2.2 Standalone paster server behind a apache reverse proxy.
	The credentionals are taken from the SSL-certificate and are added 
	to the HTTP-Header. Setup a stand alone server as described above.
	Use 'contrib/apache/apache-site-proxy.conf' as base for your
	configuration of your apache server.

	2.3 As WSGI application in Apache (mod_wsgi)
	The credentionals are taken from the SSL-certificate and are added 
	to the HTTP-Header.
	Use 'contrib/apache/apache-site-wsgi.conf' and
	'contrib/apache/mpuls.wsgi' as base for your apache configuration.


CONFIGURATION
=============

1. In the ini file:

	# Choose whatever you want
	mpuls.app.name="MY MPULS APP"
	# Give name of the configuration file. 
	mpuls.app.config=%(here)s/wasko.json
	# Choose the correct foldername where your application is located 
	mpuls.app.instance=mympuls 
	mpuls.app.indexcontroller=mpuls

	* Setup database connection. Only define databasename if you do not
	  want the databasename comming from the SSL-certificate! 

2. Currently there are no more modifications needed. wasko.json already is
ready to run.


CASEMANAGEMENT CONFIGURATION
============================

Field Configuration
-------------------

The json configuration file can contain field-specific settings for each
formed-field.  These settings define whether to show a field in the
default case-digest or whether the user can search for it or whether it
will be automatically be retrieved from the database in the search
results.  See the comment for the "case, fields" setting in
mpulsweb/lib/config.py and the doc-string of the Field class
mpulsweb/model/case.py for details.


Columns in case overview/search results
---------------------------------------

Which columns are shown for whom in which way on the search results page
(URL /case_overview) is determined on two different localtions:

1. The field configuration form above. See details there and
2. the python list called fields near the top of the template
waskaweb/templates/casemanagement/caselist.mako.  See the comments there for
more information.

LOGBOOK CONFIGURATION
=====================

Configuration of available types of logbook entries and their categories is
done in the json file:

Example:

"logbook": {
	"categories": [
		{
			"name": "unmittelbare Arbeit mit dem Jugendlichen",
			"items": ["1", "2", "3"]
		}
		... more categories ...
	],
	"descriptions": [
		{

			"1": "Gespräch mit dem/der Jugendlichen",
			"2": "Kompetenzfeststellung",
			"3": "Korrespondenz mit dem/der Jugendlichen"
			... more descriptions ...
		}
	]
}