ESA > Join & Share > HMA-T > ERGO PROGRESS 0809 4CT

ERGO PROGRESS 0809 4CT

WP2200 Support to the requirement definition: OMAR

Activities performed

none.

Outcomes and results

none.

Problems and concerns

none.

Plans for next period

This WP has been completed

WP3200 Implementation of the CSW/EbRim and EO Application Profile for CSW 2.0 /EbRim based on the OMAR

Activities performed

Most of the work has been directed to re-factor the persistence layer of the ebRR. The main reason to do this was the unsatisfactory performance caused by the rather complex queries that the Hybernate engine generates from the data access object model. This was a drastic decision, but its was based on query tests that we manually produced outside of Hybernate on the database. With the re-factored persistence layer we can control exactly how to build the queries and are confident that we reach a satisfactory query performance.
There's work done on a Java client API to access the ebRR, but there's more work to be done on a Java API that connects directly with the core registry (needed for Toolbox integration).

Outcomes and results

Improved persistence layer.
Java Client API to access the ebRR

Problems and concerns

The new persistence layer requires more testing.

Plans for next period

More testing on the new persistence layer.
Java API connecting to the core of the ebRR

WP4200 Support to the testing activities: OMAR

Activities performed

Activity is not yet started.

Outcomes and results

none.

Problems and concerns

none.

Plans for next period

none

Contributors to this page:

Jef Vanbockryck .

Page last modified on Thursday 09 of October 2008 09:28:18 CEST by Jef Vanbockryck.

Category: HMA-T

wiki page:

Category: ERGO

wiki page:

History

Search Help

Non Advanced Search or Natural Search

The documents are returned sorted on relevance depending on order, proximity, frequency of terms.

Advanced Search or Boolean Search

Default search behavior

By default, all search terms are optional. It behaves like an OR logic. Objects that contain the more terms are rated higher in the results and will appear first in their type. For example, wiki forum will find:

objects that include both terms
objects that include the term wiki
objects that include the term forum

Requiring terms

Add a plus sign ( + ) before a term to indicate that the term must appear in results. Example: +wiki forum will find objects containing at least wiki. Objects with both terms and many occurences of the terms will appear first.

Excluding terms

Add a minus sign ( - ) before a term to indicate that the term must not appear in the results. To reduce a term's value without completely excluding it, use a tilde. Example: -wiki forum will find objects that do not contain wiki but contain forum

Grouping terms

Use parenthesis ( ) to group terms into subexpressions. Example: +wiki +(forum blog) will find objects that contain wiki and forum or that contain wiki and blog in any order.

Finding phrases

Use double quotes ( " " ) around a phrase to find terms in the exact order, exactly as typed. Example: "Alex Bell" will not find Bell Alex or Alex G. Bell.

Using wildcards

Add an asterisk ( * ) after a term to find objects that include the root word. For example, run* will find:

objects that include the term run
objects that include the term runner
objects that include the term running

Reducing a term's value

Add a tilde ( ~ ) before a term to reduce its value indicate to the ranking of the results. Objects that contain the term will appear lower than other objects (unlike the minus sign which will completely exclude a term). Example: +wiki ~forum will rate an object with only wiki higher that an object with wiki and forum.

Changing relevance value

Add a less than ( < ) or greater than ( > ) sign before a term to change the term's contribution to the overall relevance value assigned to a object. Example: +wiki +(>forum < blog) will find objects that contain wiki and forum or wiki and blog in any order. wiki forum will be rated higher.