Configuration and administration
TemaTres has three management settings which can be modified.
1. Parameters defining the controlled vocabulary. Apart from poly-hirearchy and vocabulary base address (URI), these parameters are mostly descriptive. These parameters can be modified by any user with administrative permissions.
2. Operational configuration parameters of the controlled vocabulary These parameters define and regulate the extended capabilities of TemaTres. These parameters can be modified by accessing the config.tematres.php file located in the vocabulary (eg http://localhost/tematres/vocab/).
3. Connection parameters to the database These parameters establish the connection to the database and need to be modified during installation and when adding additional vocabularies. The parameters are located in the db.tematres.php file located in the vocabulary (eg http://localhost/tematres/vocab/).
Parameters defining the controlled vocabulary
These settings in the Administration menu are available to those with administrator privileges.
To access the configuration options for the vocabularies use: Administration -> Settings.
Through this menu you can describe the characteristics of:
Vocabularies of origin or source vocabularies Local reference vocabularies External reference vocabularies via web services
The information provided will only impact on the vocabulary data that is actually managed by TemaTres. For reference vocabularies, the settings can be used to establish relations of equivalence or non equivalence between vocabularies.
Setup options for a controlled vocabulary
These options are used to create the metadata which describes the controlled vocabulary and to set some features of the vocabulary. The metadata will appear in any format which describes the vocabulary (Meta-Tags, Dublin Core, SKOS-Core, RSS) and will appear in the header of all pages
Title Title of the vocabulary.
Author Author, author, or entity responsible for the intellectual content of the vocabulary in its present form.
Language The language of vocabulary in its present form. It is used to set the default language of the TemaTres web interface.
Date Shows the date when the vocabulary was created.
Keywords Keywords that describe the thematic scope of the vocabulary.
Type of vocabulary Whether the vocabulary is a thesaurus, taxonomy, keyword list, etc..
Allow poly-hierarchy Poly-hierarchy is where a term can be subordinate to more than one term in the hierarchical relationships (eg MeSH). This parameter is used to establish rules of consistency check on the operations of subordinate terms.
URI Base address and only in the context of the Internet (URI = Uniform Resource Identifier).
Scope Description of the scope of the vocabulary.
Operational configuration parameters of the controlled vocabulary
TemaTres supports re-direction of a search term to other searchable web resources such as Google Scholar, where the target service can receive and correctly interpret queries via URL.
The available services are configured using the [SEARCH_URL_SITES] array in the config.tematres.php file located in the /tematres/common/include directory. The default settings are shown below.
$ CFG ["SEARCH_URL_SITES"] = array ("wikipedia", "Google exact", "Google scholar", "Google images", "Google books");
The following configurations are available in the standard distribution of TemaTres and can be activated by adding their names to the [SEARCH_URL_SITES] array.
• E-LIS • Wikipedia • CreativeCommon • Google books • Google • Google scholar • Google images • Google books
Optional configurations are also available for the following services:
• CAICYT • VOCED • ERIC • CEDEFOP • REDINED • BNM • TRT
Additional resources can be added, provided the target service can receive and correctly interpret queries via URL. For each new entry the following will be required;
The Standardized name of the service: which will be used later to invoke the target service. eg: 'Google'.
Favicon: file name to use as the icon for the link to the search via url. The file should be on the path tematres/common/images
Legend: Legend on the icon that appears to link the search via url.
URL: URL to use to carry out the search. The search variable will need to be replaced by STRING_BUSQUEDA in the URL. For example, 'url' => http://del.icio.us/search/?fr=del_icio_us&p=STRING_BUSQUEDA&type=all' encode: Optional, TRUE will render the search expression as HTML
Base URI for XML exports
For exports in SKOS-Core and other formats URI based identifiers can be used. If this parameter is left empty, will use the vocabulary URI. $ CFG ["_URI_BASE_ID"] =;
Binding configuration and base URI identifier term For exports in SKOS-Core and other formats, one or more specific characters can be configured to act as a union between the identifier and the identifiers of vocabulary terms. eg $ CFG ["_URI_SEPARATOR_ID"] = '? Theme =';
Character Encoding This sets the type of character encoding to be used by TemaTres. Since Version 1.05 the default encoding is utf8. Prior to this Latin1 was used. $ CFG ["_CHAR_ENCODE"] = 'utf-8';
Maximum depth This is the maximum depth of hierarchical displays on one screen or view. This parameter is useful to prevent overloading of the system with highly branched and deep hierarchies. The default value is 3. define ('CFG_MAX_TREE_DEEP', '3 ');
Status Display of terms This sets the ability to view rejected and candidate terms. Publishing Data 1 = 2 = not publish data define ('CFG_VIEW_STATUS', '1 ');
Availability of Web Services This parameter lets you enable or disable the web service interface for a vocabulary. 1 = enabled, 0 = not enabled define ('CFG_SIMPLE_WEB_SERVICE', '1 ');
Minimum number of characters to search This parameter sets the minimum number of characters that will be needed to perform a search. This limit is also used by the Web Services interface. define ('CFG_MIN_SEARCH_SIZE', '3 ');
Connection parameters to the database
File configuration options for db.tematres.php
By default TemaTres uses MySQL. You can select MySQLi, Postgres, OCI8, MSSQLl and more. (For a list of php supported databases see http://phplens.com/adodb/supported.databases.html) To use MySQL leave this parameter empty. $ DBCFG ["DBdriver"] = "";
IP address or name of the database server $ DBCFG ["Server"] = "localhost";
Database Name $ DBCFG ["DBName"] = "tematres";
Username for connection to the database $ DBCFG ["dblogin"] = "username";
Password to connect to the database $ DBCFG ["dbpass"] = "password";
Prefix for tables. Use a prefix for each installation of TemaTres can have multiple installations in one TemaTres database. $ DBCFG ["dbprefix"] = "LC_";
Encoding used for connection to the database. If you have an earlier version TemaTres 1.05, you may find it convenient to use utf8 as the encoding for the connections of the database. $ DBCFG ["DBcharset"] = "utf8";
Error detection mode queries. This parameter, when the value 1 will display errors in queries to the database. These errors should not occur in normal conditions and contexts. $ DBCFG ["DebugMode"] = "0";
TemaTres has a public interface services for each controlled vocabulary and these can be managed by two levels of users: Editors and Managers.
Access all management functions of terms Create, modify, delete terms Create, modify, delete relationships between terms Create, modify, delete relationships between vocabulary words and terms of reference Assign terminology mappings between terms of vocabulary and terms of reference vocabularies through web services Update terminology mappings between terms of vocabulary and terms of reference vocabularies through web services Create, modify, delete notes Modify your identification data Access to audit data themselves Generate reports simple and advanced terminology
Includes all the capabilities of the editor Access the administrative functions Modify the configuration of the controlled vocabulary Create, modify, delete users Record, edit, delete reference vocabularies Export full versions of the controlled vocabulary Performing maintenance of the database Access to audit data totals Vocabularies import from text files or from sources SKOS-Core Register reference vocabularies through web services
Different Vocabulary Formats
Since version 1.2 TemaTres makes it possible to implement two different models of multi-lingual controlled vocabularies: a vocabulary centred model and a federated model
Reference model with local vocabulary: This model has both a source and target vocabulary, where the vocabulary terms in the source vocabulary have an equivalence in the target vocabulary. All vocabularies (source and target) are managed by TemaTres. This option can be useful if the target vocabulary (target vocabulary) does not exist or there are incomplete terminological correspondences.
Advantages of this model:
Allows mapping and establishment of nominal reference vocabularies where vocabularies do not exist or are unavailable. Mapped terms can be retrieved on search and alphabetical browsing. It provides full control over the management of the terms from the reference vocabularies. The mapping relations are normalised, allowing complete, partial or non-equivalence relations.
Disadvantages of this model:
Nominal mappings are set on the resulting complex inferences or develop other advanced processes When were they recorded many vocabularies of reference (10 languages, for example) search operations generate results irrelevant and inaccurate, since it includes the results of all reference vocabularies. If changes in the actual reference vocabulary, there are no automatic mechanisms alert and updated text. For example, if stated as a vocabulary reference to UNESCO Thesaurus, and such change or delete a thesaurus term, there is no automatic mechanisms for notification and update.
Federated model with external reference vocabulary:
This model allows to relationships to be established between various independent vocabularies, whether equivalence relations between languages or other relationships between terms and concepts. Each of the vocabularies (target vocabulary) can be used to offer web services through TemaTres. This option can be useful for medium and large multilingual projects.
Advantages of this model:
A wide range of terminology mappings can be set, with a unique URI for each mapping terminology. Relationships can be described in terms consistent with the linked data model. An unlimited number of reference vocabularies can be added without impacting on the functionality and performance of each. It is a federated model therefore has an autonomous user schema for each vocabulary. It has automated mechanisms for federated updating of terms, which means that if a term is changed or removed in a reference vocabulary, the changes are notified to the original vocabulary. Mapping relations are not standardised, therefore it is therefore possible to establish relationships between all vocabularies, such as translation, extension, equivalence.
Disadvantages of this model:
It is only possible to use this model where vocabularies are provided as a web service. By allowing different types of relationships, there is a greater reliance on the judgement of those creating the vocabulary to use terminology mappings which are cohesive and coherent.