Eric Barroca - 12/02/07 20:55 George: Please write a short implementation detail.

George Lefter - 28/02/07 17:53 1. In the first page, the user chooses a vocabulary from a list obtained from DirectoryService. 2. The next page displays the entries in the selected directory, allowing the user to filter / edit / delete / create entries. The user should also be able to translate the labels. For this, each vocabulary needs an associated table for each locale, e.g. "<tablename>_translations_fr" with columns "label" and "translation". These tables have to be set up as directories first. A list of locales should be read from a configuration file. When creating/editing an entry, the user will be allowed to enter a translation for each locale defined in the config file - if the translation directory exists. The vocabulary will be changed to look for a translation first in the corresponding table, and then in the messages file.

George Lefter - 28/02/07 17:54 please review

Delphine Renevey - 09/03/07 14:34 First screen, available by a link "Vocabulaires" only for administrator. Administrator chooses a vocabulary from a list obtained from DirectoryService.  The next page allows admin to search for an entry ( search widget necessary, for simple & hierarchical vocabularies) When an entry is selected, admin can edit it Delete entry is not allowed. (when an entry is obsolete, admin does not delete it, admin sets a value to Obsolete , by editing it) Admin can create a new entry, which means entering Id, label, sort, state(obsolete or not). When an entry is obsolete, it doesn't appear anymore when someone creates a document)