Open Source Document Management System | OpenKM

Hi All,

This is not a serious problem as I'm working with a test installation and can just start again. I'm using an HSQL database. I accidently set the following in my PropertyGroups.cnd file:

- okp:publication.author (string) = '' multiple autocreated

thinking that I could have multiple authors, but the term "multiple" really means that I have to provide a select box. Removing the word "multiple" now causes an error when importing the PropertyGroups.cnd file. I tried using the repository viewer to access the cell of:

BOOLEAN jcr:multiple true

and set it to false, but this cell is not editable. I was hoping to set it to false. Is there a tool to traverse and edit the internals of the HSQL database?

Maybe this is one of the reasons for using MySQL or another database system rather than HSQL. For example the package Webmin allows direct editing of MySql databases via a web interface. Very useful.

Multiple indicates that can be stored several keys at same node, this can not be changed to other which stores only one, is a repository restriction ( not database ). In version 6 this kind of problems can be solved in version 5.1.x and older this kind of changes can not be done, reason why must play with care with property groups. At least create in test environment and then register on production, that's good practice.

In xml normally goes associated select with type multiple that allows selecting several values.

jllort wrote:Multiple indicates that can be stored several keys at same node, this can not be changed to other which stores only one, is a repository restriction ( not database ). In version 6 this kind of problems can be solved in version 5.1.x and older this kind of changes can not be done, reason why must play with care with property groups. At least create in test environment and then register on production, that's good practice.

In xml normally goes associated select with type multiple that allows selecting several values.

Thanks I'll make sure I always test this in a test environment first when I go to a live system.