Custom Query (44 matches)

currently the own value is used everywhere (lists/comboboxes) to represent an entity.

the own value was thought to be a technical internal value. Nobody knows what it stands for. We need to be able to configure an atribute (later a list of attributes) the build the own value. This information has to be stored in the definition defining section of the datastore.

Please do not forget who is using the own value and what happens if we change that. There are also already data in the own value field. So we can not use it as on-the-fly generated field. I suggest to add a method getLabelString to the entity or entity shape class. Then the definition metadata get read and used to provide the label. This is then used instead of the getOwnValue in the user interface for entity lists and combobox labels.

If it is not clear we shall speak about that ticket in detail.

Later we can rename the now used own value fields to get names which have a meaning such as all the other attributes.

in the admin section we need a special form to save that metadata. The we might simply save the data in the datatbase instead of the openmind,txt as suggested above. Whoever fixes this ticket, please speak to Robert M. before.

currently we do not come back to the list of definitions where we came from if we edit/create a entity.

we know what we have edited (definition of edited/created entity. So if we come back and show the initial repository overview we can also go to a certain list as if we would click on the definition name and then on show-all-entites of that definition.

currently the combobox values (fixed values, query based) are not always sorted correctly. I assume the own value of an entity is rendered as label in the comboboxes if they come from a query.

Check who is building the comboboxes or provides the values. Find a way to add maybe a simple arrays.sort or something (Defaultentitycomparator.java if query bases) to the called controller class.