FISE Gentics Integration Validation and Online Demo

From IKS Project
Jump to: navigation, search

Demo

The implementation is available to the public on

http://labs.gentics.com:8080/Portal.Node/content/Autotagging.html (Login: hmeran, Pass: hmeran)

(we use the FISE engine on the same server http://labs.gentics.com:9000)

and

http://semantic-editor.org/try_it/


Aloha Editor Annotation plugin

The annotation plugin is available as opensource under the MIT & GPL license hosted on github (https://github.com/alohaeditor/Aloha-Plugin-Annotations).

Validation

Gentics Software GmbH is an Austrian CMS and Portal Software Provider. We integrated FISE into our main product Gentics Content.Node through the Aloha Editor. The integration is done on client side in javascript as Aloha Editor plugin which provides an easy to use live stack of annotations. As one use of the live stack we implemented an automatic live annotation of tags.

Use-Case

When leaving (ESC or click in the surrounding content) an Aloha Editor editable the content is sent to the backend FISE engine for a REST response. FISE returns annotations and the top level annotations are used for the auto tagging. The tags are automatically added to the document, so there is no need for further user interaction. A user may discard tags which he thinks are not appropriate, with one single click.

Due to the fast response from the FISE developers an implementation could be done straight forward.

Lessons learned

  1. Problems finding the best FISE version to use. We followed the instructions on the google code website but had problems compiling on a MAC. A hint from the FISE developer team lead to the early adopter precompiled version, which worked for the first steps.
  2. More issues emerged when requesting from different browsers. The problem could be identified as a content charset issue and was reported (http://code.google.com/p/iks-project/issues/detail?id=93). A solution was provided in a short timeframe.
  3. There are still some issues open that produce unexpected behavior (http://code.google.com/p/iks-project/issues/detail?id=100)


Performance

To enable live annotation on smartcontentchange event high performance responses from the backend are necessary. Therefore a performance test with jemeter has been done. To setup the environment we tested with 100 concurrent requests 100 times with a simple sentence (the same for all requests). The first 1800 requests delivered good response. The last 200 requests and all following failed. The reason was: Fise error message: Error 500 'LocationEnhancementEngine' failed to process content item 'urn:content-item-sha1-84854eb6802a601ca2349ba28cc55f0b930ac96d' with type 'text/plain': the hourly limit of 2000 credits for the IP address 188.40.152.152 has been exceeded. Please throttle your requests or use the commercial service.

We reported the problem and the FISE team found the reason: The problem is that the LocationEnhancementEngine (eu.iksproject.fise.engines.geonames.impl.LocationEnhancementEngine) does use the geonames.org webservices. In detail for each Location dedected by FISE it sends up to 5 webservice requests. So a enhanced document with 5 detected locations will use up to 30/2000 free credits/h. That means that the LocationEnhancementEngine can not be used for much more than 100 requests/h.

RICK will provide a solution for the issue. We could not complete our performance tests and decided to wait for call for evaluation for RICK and than do further performance evalutation.

Visibility

We plan announced the plugin and FISE integration among the Aloha Editor community and website as well as among the Gentics clients through the Gentics Newsletter and Gentics website. The FISE annotation plugin is not yet in a state to be implemented in a production system so the plugin is available for customers to integrate in Gentics Content.Node 5.

Software components used

  1. FISE

Industrial Validation Metrics

Validation Questions
Yes / Strongly
Agree
Agree
Disagree
No / Strongly
Disagree
Don't know / n.a.
Comments
Do I understand what IKS FISE is?
X




Does IKS FISE add value to my product?
X




Is that added value demonstrable/sellable to my customers?




X
Can I run IKS FISE alongside with or inside my product?





both
Is the impact of IKS FISE on runtime infrastructure requirements acceptable?


X

at time of evaluation
How good is the IKS FISE API when it comes to integrating with my product?

X


REST was not reliable
Is IKS FISE robust and functional enough to be used in production at the enterprise level?


X


Is the IKS FISE test suite good enough as a functionality and non-regression "quality gate"?




X
Is the IKS FISE licence (both copyright and patents) acceptable to me?




X are there any patents or copyrights on it?
Can I participate in IKS FISE's development and influence it in a fair and balanced way?

X



Do I know who I should talk to for support and future development of IKS FISE?
X




Am I confident that IKS FISE still going to be available and maintained once the IKS funding period is over?




X
Does IKS help in retrieving relevant information fast and efficiently for decision making / to solve problems?

X



Does IKS help in creation of business relevant information that can be shared fast and efficiently / making implicit knowledge explicit to increase competitive advantage?
X




Does IKS help managing the business processes to increase the flexibility for changing customer needs or processes?




X
Does IKS help to increase contacts with potential customers to aquire new customers or to increase customers loyality?

X



Does IKS help in selling complex products, which require individual, fast and efficient configuration?

X



Does IKS help in communication of events to attract new customers and to inform/take care of existing ones?

X


 ;-) and keep people simling
Does IKS help establishing personalized customer relationship management? X Would appreciate that