Configuration

• general
• vocabulary file
  LOM is using a fixed vocabulary for designated elements. To ensure language independence numerical values are defined which can be mapped to a textual representation in different languages.  This mapping is defined in the file specified at this entry. The file is textoriented and can be easily changed to include new languages or to change values, as long as there is an equivalent number of entries for every language. ( original vocabulary file )
  
  Note: While the editor is able to start without any other predefined values in this config file; it is not possible to start the editor without specifying the location of the Vocabulary file
  Note2: Changes to the vocabulary file will only take affect after restarting the editor
  
  
• location of the classification files
  The editor is using different classification files for the classification category. You can build your own files and add them to the specified directory to use them inside the editor (see ACM Computer Classification  as an example for the syntax of the files).


• categories
  
  This section controls the display of the different LOM categories.
  
  general, educational, technical, lifecycle (includes the rights category), metametadata, relation, annotation, classification
  If you don't want to display a LOM category int he GUI of the editor, just delete the appropriate line or put a comment (#) in front of the line. It is also possible to change these setting from the menu bar of the editor.
  
  
• preferences
  
  • language
    At the moment the editor supports english, german and spanish. Changing the language does not only change the language of the labels and menues in the GUI of the editor, it also changes the display of LOM langstring elements according to the associated language.
    Example
    

    If you have a LOM description with the following entry for the general/title element

               <title><langstring lang="de">Ein Test-Titel</langstring></title>
    
    
    and you have specified english as language, you won't see a title in the textfield of the GUI. Changing the language with the menue bar of the editor to german, will display the value above.
    

    
    It is possible to change and store this setting with the menu bar of the editor.
  
  
• database
  
  • This entry specifies, where the editor can find information about the connection to a relational database. To store LOM descriptions in a database, the editor is using the castor framework . Accessing a database with castor is not included in this version of the editor. If you want to use a databse to store your description, send an email to  iteach@kom.tu-darmstadt.de for more information.
  
  
• xml
  
  • dtdlocation
    URL of the DTD, when referencing an external DTD (default: www.multibook.de/xml/lom1.dtd ). If this entry contains the value "include" the editor will include a DTD for LOM in every xml encoded LOM description, so descriptions can be imported again, without depending on a networtk connection.
  • validation
    Specifies if the parser should stop when reading a xml encoded LOM description as soon as he finds something that violates the referenced DTD, or if the parser should ignore the error and try to read and build a LOM represenatation. 
  • jaxpProperty
    This entry speicifes the instance of the xml parser the editor should use.