NEW FEATURES AND CHANGES:

• Categorization feature
  Documents are automatically sorted by given criteria into categories. Queries, field values and manual input can be used. See documentation for details.
  
  
• Metadata feature
  Users can interactively add data to documents (notes, images, links, access counters etc.). Metadata structure can be configured by administrator (what data types, access to metadata etc.). See documentation for details.
  
  
• User credentials cache
  User credentials are stored in cache to speed up authorization.
  
  
• Caching authentication
  Information about the authenticated user can be stored in cache, so subsequent requests from same user can be processed without authentication.
  
  
• Extended LDAP authentication
  LDAP server support was completely rewritten.
  
  
• Anonymous and pre-authenticated user support
  Server can process requests in anonymous mode. Also pre-authenticated users can be used. In this case server does not authenticate users’ identity and trusts to sender.
  
  
• Possibility to activate profiling from external scripts
  Profiling can be activated from external scripts by creating specified file.
  
  
• Storing profiling results and profiles into SQL database
  Profiling results and profiles can be stored in SQL database. MS SQL, Oracle, MySQL and PostgreSQL databases are supported.
  
  
• On-demand profiling
  Possibility to send document text from the client into profiler added.
  
  
• Faster searching
  idField, sourceField and dbuniquekeys parameters allows more efficient source identification. This speeds up searching, especially if a lot of result lines are requested.
  
  
• Document level security and integrated windows authentication
  Document level security can be combined with integrated windows authentication.

BUGS FIXED:

NEW FUNCTION AND CHANGES:

• You can define conditions for detecting new documents for profiling in the configuration.
  The filter and sort tags can be used in the <collection> tag in the ts_prffeed.xml configuration file. The filter tag defines a condition in VQL format, which can contain links to field values as follows: ${filed_name=default_value}. This default value is used while first running. The sort tag contains sort rules (in VDK sortspec format). The initial settings after the installation are <filter>_DOCID > ${_DOCID=0}</filter> <sort>_DOCID asc</sort>.
  ATTENTION! As the configuration is stored in XML, you must use html entity instead of > and < characters!
• MS Office 2007 support
  DOCX, PPTX and XLSX formats
• The Czech locale was supplemented with stemming according to rules.
  For transformation to basic form are in addition to dictionary used rules, which mostly solves problem with words not present in the dictionary.
• Indexing and searching are installed as separate NT services.
  In order to increase the system stability, the indexing was separated into a special service.
• The profiler configuration was divided into more files.
  ts_profiler.xml – common configuration
  ts_prffeed.xml – profiled sources configuration
  ts_prfstore.xml – result store configuration
• Demo collections were moved from <install_dir>/vdk/610/demodata folder into <install_dir>/data/demodata folder.
• If the database initialise is not successful, the server initialise is not terminated.
  If the database tag contains the required_init="false" attribute, the server will start even if the relevant database is not initialised.
• Parameters common to all databases using the same plugin, can be placed into the TS_Plugins.xml file.
  Any parameters stated in <dbparam> tags can be stated as <plgparam> tags in the TS_Plugins.xml file. These parameters are shared among all databases, which use the relevant plugin.
• The groups are supported in the profiling.
  If the users are authenticated against Windows domain, a group can be used as a user in a profile.
• Profile was supplemented with Locale and Userdata items.
  A profile can contain query locale. It is UNI locale by default. UserData are any binary data, which can client application store together with the profile and use subsequently on editing or viewing.
• The source tree in the Java client was supplemented with a root knot with a server name.
• Internal Java client field with source name was renamed from Source to TS_Source.
• Updated developer and administrator documentation and examples.

SOLVED PROBLEMS:

• An incorrect request for server containing an empty enumerative value (enum) caused memory exception.
• Clustering did not take into consideration maximal number of retrieved documents setting (all documents meeting query were clustered).
• A request for found words list passing occasionally retrieved stems instead of words
• The JobNew function retrieved the job ID in different format, than requested in other functions.
• A trailing space in a path to collection in TS_Databases.xml caused the collection authentication failure.
• Text of some documents couldn't be withdrawn from profiling results.
• If TS_ProfilerDocFeed module doesn't have access to folder with stored history, all documents were send to profiler repeatedly.
• User names were case sensitive.
• Conditions for fields in profiling queries did not work always correctly.
• Highlights flag in a request for profiling results was ignored (the words are always retrieved).
• The clusters in the Java client did not expand when clicking the [+] icon.
• The Java client did not remember source tree "expanding status".
• If a source in the Java client couldn't be opened, the whole client finished with error.
• The Java administrative client ignores the Enter key in dialogs.
• The User has no permissions for "TS_Profiler:Profiles:Admin" message was recorded to log even if this permission is not required for the requested function.
• The wrong profiles job synchronisation during the profiler start up.
• Some error messages from profiler were not send to client application.
• A user name authenticated against Windows domain did not contain a domain name.
• Automatically created folders were not established, if there were more than one level to establish.