2.10 1.5 to 2.0 changes

2.10.1 Core repository

• [important change] Daisy switched to namespaced document IDs. Before, document IDs where simply a sequence number, now they are the combination of a sequence number and a namespace suffix. For example "123-DSY". Namespaced document IDs allow export-import of documents between repositories without collisions in the document IDs. See the docs on namespaces and the import/export tools further on.

• Hierarchical fields: a hierarchical field is a field whose value represents a path in a hierarchy. Practically speaking, a hierarchical value is a sequence of values, much like a multi-value field, but with a different meaning attached to it. The hierarchy property of a field type is orthogonal to its existing properties, so it is possible to have multi-value hierarchical fields, and to have hierarchical fields in a variety of data types (the Wiki's document editor only supports string and link hierarchical fields). The query language has been extended to allow searching on hierarchical fields. The value of a hierarchical field can be selected from a hierarchical selection list, which can be static or query+link based.

• Non-editable parts and fields: parts and fields can be marked as non-editable. This is done in the association with a document type, so a field could be editable in one document type but non-editable in another. This non-editable restriction is a hint towards the frontend GUI that the part or field should not be editable, it is not an access control restriction. Non-editable parts and fields are useful for parts and fields which are automatically assigned by some process (e.g. the image width and height fields and its thumbnail and preview parts).

• Asynchronously loaded selection lists: field types have a new property to indicate that the selection list of a field should be loaded asynchronously (in the document editor), which is useful for large or slow query-based selection lists.

• The remote Java API of the repository server no longer requires that the 'cache user' is a user with the Administrator role. Now any user can be specified (for example guest, pwd guest). The cache user is the user specified in the Credentials object when constructing the RemoteRepositoryManager.

• The repository server now keeps track of the last version in which the data of a part was changed, this information is available in the API (on the Part interface). This allowed to implement the version reversion feature more efficiently.

• Upgrade to ActiveMQ-4.1.0. This fixes an issue where read messages were not always removed from the queue and a possible memory leak. This change also calls for a small modification in the ActiveMQ configuration file.

2.10.1.1 Query subsystem

• Fulltext search enhancements:

• possibility to retrieve relevant fragments from the documents, with matching query words highlighted. This functionality is available through the new FullTextFragment() function in the query language.
• the score of the fulltext search is now accessible via an identifier (called score) in the query language, to allow explicit sorting on this value, or to display the score to the user.
• upgraded the Lucene engine to version 2.0

• Faceted Browser enhancements:

• discrete values (ranges): when confronted with large lists of facet values the user can opt for placing the values in ranges. This reduces the amount of values seen in the list.
• default order by clause: allows specification of the default sort order of search results.
• option lists: users can create sets of options which can be selected using request parameters. This way one set of facets (one definition) can be used with different options.
• active navigation path: the faceted browser can now display a navigation tree. When the active navigation path has been specified as a request parameter the navigation tree will be rendered.
• alternative stylesheets: each facet browser definition can be styled differently using its own stylesheet.
• request parameters: arbitrary request parameters can be included in the facet definition options.

• Link dereferencing in the query language: this is a powerful new capability of the query language, allowing to 'walk through' link fields to access properties of the linked-to documents.

• Chunks of query results can now be retrieved, by using the query options chunk_offset and chunk_length.