Registry of Used Parameters

1. Service integration parameters
1. org.openpsa.jabber
2. org.routamc.photostream:flickr
3. org.routamc.positioning:plazes
4. org.openpsa.skype
5. org.routamc.statusmessage:jaiku
2. User interface parameters
1. Interface
2. display_setting
3. Content storage parameters
1. images

Many Midgard applications define their own parameter domains and names for configuration purposes. This page aims to list all reserved domains and most common parameter names for reusability purposes. If you are developing a Midgard application, try to reuse the parameters provided here for better integration with the rest of the environment.

Service integration parameters

These parameters are used by various components for integrating with popular social web services. The parameters are easily made editable with datamanager schemas.

org.openpsa.jabber

This domain of parameters is used by several components for Jabber/Google Talk integration purposes. Stored to Person object.

jid

User's Jabber ID

org.routamc.photostream:flickr

This domain of parameters is used by org.routamc.photostream for holding user's Flickr account details for photo importing. Stored to Person object.

username

User's Flickr username

org.routamc.positioning:plazes

This domain of parameters is used by org.routamc.positioning for holding user's Plazes account details for location importing. Stored to Person object.

username

User's Plazes username

Password

User's Plazes password

org.openpsa.skype

This domain of parameters is used by several components for Skype integration purposes. Stored to Person object.

name

User's Skype name

org.routamc.statusmessage:jaiku

This domain of parameters is used by org.routamc.statusmessage for holding user's Jaiku account details for status importing. Stored to Person object.

username

User's username in the Jaiku service

personal_key

User's personal Jaiku key

User interface parameters

Interface

This domain of parameters is used by Aegir and Boyan for holding user's defaults for interface. Nowadays these have been superseded by MidCOM ACL privileges.

Power_User

Applicable to Person object. If it is set to NO (upper-case) then the user sees only basic features, else he is given the full power of low-level access.

Approve_Website

Applicable to Group object. If it is set to NO (upper-case) then the user is not allowed to approve any kind of objects.

View_*

Applicable to Group object. If it is set to NO (upper-case) then the user is not allowed to View/Edit kind of objects specified by '*'. Terms are derived from Aegir and can be (but are not limited to): news, websites, snippets, groups

display_setting

This domain relates to visual representation of Administrative UI. Applicable to Person object.

encoding

Complete definition of Content-type http-header of the page. example: Content-Type: text/html; charset=windows-1251

lang

The name of library to be used by NemeinLocalization. example: ru_cp1251

locale

Users preferred Locale string. example: ru_RU.CP1251

browseopt

Default action to perform when opening an object, if applicable. We consider two values to be standard: edit - mode which uses some kind of input mechanism for altering value of the object, browse - mode which gives a preview or an overview of an object and doesn't allow direct editing of an object.

Content storage parameters

images

Settings where images and other attachments related to this object and its children are to be stored.

witharticle

Applicable to Topic object. If the value is YES, attachments should be stored to the Article object itself, if the value is NO attachments are sored in the Topic. Default behaviour of application is left undefined for compatibility issues, but recommendation is storing attachments in articles.