12.09.2012 WP10 - X-Search Integration

From IMarine Wiki

Jump to: navigation, search



Time: Wed, September 12, 2012, 12:10 - 12:40 CEST

  • Planning of this week's activities to prepare for gCube 2.10.0 and the internal evaluation of the application.
  • Status of implemented features
  • Resolution of remaining issues.


  • Alex Antoniadis (NKUA)
  • Gerasimos Farantatos (NKUA)
  • John Gerbesiotis (NKUA)
  • Rena Tsantouli (NKUA)
  • Pavlos Fafalios (FORTH)
  • Yannis Marketakis (FORTH)
  • Claudio Baldassarre (FIPS)

Discussion Summary

Actions to be taken during this and next week are described by NKUA. We should solve all remaining technical issues in preparation for the upcoming gCube release and in order to make available the provided version for internal evaluation. Another call will be scheduled for next week to discuss feedback obtained by the evaluation and plan timely reaction to any issues that are raised. The discussion on technical issues which followed concentrated on issues raised by NKUA last week after using the then available version of the XSearch portlet. (A new version was made available today to NKUA and was deployed at dl10.di.uoa.gr which hosts a development infrastructure portal.)

  • FORTH has already solved the delay in result presentation issue, but there seems to be a delay showing clusters and entities in the XSearch portlet. This problem seems to be related to another issue NKUA reported, concerning inconsistencies between the number of results displayed by the Results portlet and the XSearch portlet. FORTH reported that this is in turn related to the behavior of gRS2 when providing more than 50 results to the XSearch Service. In addition, since according to benchmarks ran by FORTH the processing of results by the XSearch service takes no more than 2 seconds, FORTH believes that the remainder of the delay which is in the order of minutes is caused by gRS2.
    • NKUA made a quick observation about this problem. Since 50 is the default buffer capacity used by gRS2 and this behavior occurs when this limit is exceeded, this is most likely caused by a timeout on the gRS2 writer. This means that it is likely that the issue is related to the usage of gRS2 by the portlet, rather than gRS2 itself. In addition the overhead incurred by normal usage of gRS2 is expected to be no more than a few seconds in the worst case. The issue is going to be better investigated during the day by NKUA and FORTH as it is of high priority. Update 13.09.2012: This issue is tracked in tickets #627 and #628
  • The presented results contain no presentable fields other than the snippet. This is actually not a real issue, but it was pointed out by NKUA because this might have to be revisited in the near future.
    • FORTH had already replied during the previous week informing NKUA about their decision to keep it this way since the application is free to present results in a way of its choosing. FORTH agrees to perform changes if feedback indicating such an action is received from the internal evaluation of the application.
  • When there is a problem with the underlying Search System, the XSearch portlet displays a message that reads "Search was unavailable". NKUA feels that this is misleading to the user. Instead, the message of the exception should be displayed.
    • FORTH will change the message to a more suitable generic message and include the change in 2.10.0. The actual exception message will be displayed by the version targeting the release after 2.10.0.

Additional topics of discussion included:

  • Result analysis over all content using annotated search fields (using the Resource Registry), also discussed during a previous phone call
    • This functionality is not yet implemented and will not be included in release 2.10.0. NKUA stated that given the importance given to semantics in the oncoming review, the functionality should be included in the next release so that a more complete work is presented. FORTH feels that this feature falls under enhanced functionality since (i) the default mode of operation of the portlet which is based on snippets is sufficient to drive all provided functionality showing the value of all features provided by the application; its usage simply results in more enriched results and (ii) other applications developed by FORTH in the context of iMarine already demonstrate this feature. NKUA further added that even so, the effort integrating Resource Registry is minimal so it would still be beneficial to include this feature in the next gCube release.
  • Configurable entity categories. The application should provide a way to configure the categories based on the scope under which the query is run.
    • This functionality has not been implemented yet.
    • Implementation will target the release after 2.10.0.

FIPS feels that a number of use cases/scenarios should be discussed, in order to be used during the internal evaluation but also at the project review. NKUA and FORTH agree. FIPS believes that the scenarios should not be artificial, therefore it would be better if they are created by users and not by the developers of the application (FORTH). FIPS, NKUA and FORTH agree that the availability of XSearch for evaluation before scenarios are agreed upon poses no problems. They can be discussed at the conference call to be held next week, possibly along with the initial feedback obtained by the evaluation.


  • Solve all remaining technical issues of high priority, especially the one regarding delays/the usage of gRS2 by the end of this week.
  • Have the version to be released in 2.10.0 available for internal evaluation by the end of this week.
  • Organize the next phone call for next week.
Personal tools