Difference between revisions of "Property Groups"
m (moved Metadata to Property Groups: This is the right name.) |
|||
| Line 1: | Line 1: | ||
| − | |||
This is easy and powerful for building custom properties. You can user this feature to add information to documents. For example, if you store the invoices in a folder you can add a property group to set the client name and the quantity. You will see this important data without opening the documents. Also you can search by these custom properties later. | This is easy and powerful for building custom properties. You can user this feature to add information to documents. For example, if you store the invoices in a folder you can add a property group to set the client name and the quantity. You will see this important data without opening the documents. Also you can search by these custom properties later. | ||
Revision as of 18:45, 21 January 2010
This is easy and powerful for building custom properties. You can user this feature to add information to documents. For example, if you store the invoices in a folder you can add a property group to set the client name and the quantity. You will see this important data without opening the documents. Also you can search by these custom properties later.
You need to create some file, for example my_groups.cnd and insert some values in other two files PropertyGroupBundle.properties and PropertyGroupValues.properties.
- $JBOSS_HOME/PropertyGroup.cnd
- $JBOSS_HOME/PropertyGroupBundle.properties
- $JBOSS_HOME/PropertyGroupValues.properties
To try this test login as okmAdmin and go to Administration → Utilities → Register property groups. Set full path with the location of the local file PropertyGroup.cnd and push the register button. The properties will be registered.
WARNING: REGISTERED GROUPS CANNOT NOT BE UNREGISTERED. They can always be updated but they cannot be deleted after registration !!! Try it out on a test installation first.
About files
- PropertyGroupBundle.cnd: There are general definitions on each parameter ( for example the parameter okp:technology.type )
<okm = 'http://www.openkm.org/1.0'>
<okg = 'http://www.openkm.org/group/1.0'>
<okp = 'http://www.openkm.org/group/property/1.0'>
[okg:technology] mixin
- okp:technology.type (string) = '' multiple autocreated
- okp:technology.language (string) = '' autocreated
- okp:technology.description (string) = '' autocreated
- okp:technology.comment (string) = '' autocreated
[okg:consulting] mixin
- okp:consulting.type (string) = '' autocreated
- okp:consulting.comment (string) = '' autocreated
- PropertyGroupValues.properties: In this file you can see the properties values, for example for parameter (okp\:technology.type=4,one,two,three ) has 3 values (one, two, three) the first number indicates the type ( 1 = list, 2 = input, 3 = select multiple, 4 = Text area )
okp\:technology.type=4,one,two,three
okp\:technology.language=3,java,c,c#,c++,python
okp\:technology.description=1
okp\:technology.comment=2
okp\:consulting.type=3,one,two,three
okp\:consulting.comment=2
- PropertyGroupBundle.properties: This file contains general translations for each value you can have more files for each language like PropertyGroupBundle_ES.properties etc.
okg\:technology=Tecnology
okp\:technology.type=Type
okp\:technology.type.one=Type One
okp\:technology.type.two=Type Two
okp\:technology.type.three=Type Three
okp\:technology.language=Language
okp\:technology.language.java=Java
okp\:technology.language.c=C
okp\:technology.language.c++=C++
okp\:technology.language.python=Python
okp\:tecnology.description=Description
okp\:technology.comment=Comment
okg\:consulting=Consulting
okp\:consulting.type=Type
okp\:consulting.type.one=Type One
okp\:consulting.type.two=Type Two
okp\:consulting.type.three=Type Three
okp\:consulting.comment=Comment
OpenKM tries to find the correct language in your property files. If it does not exist uses it uses PropertyBundle.properties.
