Difference between revisions of "Property Groups"
(Created page with '== Metadata == OpenKM comes with metadata support; You need to create some file, for example my_groups.cnd and insert some values in other two files PropertyGroupBundle.propertie…') |
|||
| Line 2: | Line 2: | ||
OpenKM comes with metadata support; You need to create some file, for example my_groups.cnd and insert some values in other two files PropertyGroupBundle.properties and PropertyGroupValues.properties. | OpenKM comes with metadata support; 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/my_groups.cnd | + | *$JBOSS_HOME/my_groups.cnd |
| − | $JBOSS_HOME/PropertyGroupBundle.properties | + | *$JBOSS_HOME/PropertyGroupBundle.properties |
| − | $JBOSS_HOME/PropertyGroupValues.properties | + | *$JBOSS_HOME/PropertyGroupValues.properties |
To try this test login as okmAdmin ( or user with adminitration grants ), put your local path for the my_groups.cnd file, and the properties will be registered. | To try this test login as okmAdmin ( or user with adminitration grants ), put your local path for the my_groups.cnd file, and the properties will be registered. | ||
Revision as of 12:36, 21 January 2010
Metadata
OpenKM comes with metadata support; 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/my_groups.cnd
- $JBOSS_HOME/PropertyGroupBundle.properties
- $JBOSS_HOME/PropertyGroupValues.properties
To try this test login as okmAdmin ( or user with adminitration grants ), put your local path for the my_groups.cnd file, and 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 not in a production environment.
About files: On my_groups.cnd there are general definitions on each parameter ( for example the parameter okp:tecnologia.tipo )
On PropertyGroupValues.properties are the values, for example for parameter (okp\:tecnologia.tipo=0,4,uno,dos,tres ) has 3 values (uno,dos,tres) the first number indicates the ordering - starting with 0 - the second number indicates the type ( 1=list, 2=input, 3= select multiple, 4=Text area )
In PropertyGroupBundle.properties are general translations for each value you can have more files for each language like PropertyGroupBundle_ES.properties etc... For example here are some translations:
okp\:tecnologia.tipo=Tipo okp\:tecnologia.tipo.uno=Tipo Uno okp\:tecnologia.tipo.dos=Tipo Dos okp\:tecnologia.tipo.tres=Tipo Tres
OpenKM tries to find the correct language in your property files. If it does not exist uses it uses PropertyBundle.properties.
This is easy and powerfull for building custom properties.
