1. ARIADNE V4 Filip Neven, Stefaan Ternier & Erik Duval Dept. Computerwetenschappen, Katholieke Universiteit Leuven, Belgium E-mail: ariadne@cs.kuleuven.ac.be

2. Ariadne V3 architecture Access to database through Query Tool (TM5) Maintenance is difficult –Database structure is hardcoded at many places –Duplication of functionality (TM5, replication) Installation is difficult –Different tools have to be installed seperately KPS WEBLEQuery Tool (TM5)TM6Replication... Document Repository

3. A new V4 architecture: Why? Programmers point of view –Old 2-tier architecture is difficult to maintain –Exploit KPS as a component Users point of view –End users Want easy user inferface (integrated in the tool they use) Automatic metadata generation –Application developers Technical users (e.g. Blackboard) Provide easy solution for accessing the knowledge pool Blackboard, SILOGIC,...

4. Ariadne V4 architecture KPS ClientSOAP InterfaceQuery Tool SQL SOAP API JAVA API KPS Document Repository

5. Ariadne V4 packages KPS ClientSOAP InterfaceQuery Tool KPS client development package Query tool package (TM5) KPS Document Repository KPS package

6. Ariadne V4 packages KPS SOAP Interface KPS Client Query Tool KPS Client Blackboard Your (non java) application KPS Client SILOGIC Document Repository

7. Soap Interface XML technology –Easy processing of metadata –Validation of metadata –LOM export Hide complexity of database for query tool –Query Service Keyword Query Advanced Query Get Results –Insert Service Insert Delete Update –Download Service

8. KPS Client Application Development Kit Offers Java API that talks with SOAP interface –Query, Insert, Update,... –methods to handle metadata

9. Towards a critical mass Share and reuse -> critical mass –Content –Users Why don’t we reach this critical mass ? Indexation process takes too long # new documents stable Low number of query results Motivation to index new material low

10. Towards a critical mass Share and reuse -> critical mass –Content –Users Why don’t we reach this critical mass ? Indexation process takes too long # new documents stable Low number of query results Motivation to index new material low

11. Towards a critical mass Share and reuse -> critical mass –Content –Users Why don’t we reach this critical mass ? Indexation process takes too long # new documents stable Low number of query results Motivation to index new material low

12. V4 Indexation- and Query Tool Simplify the indexation procedure –Profiles –Automatic metadata generation –Less = more E.g. Hide concept management

13. V4 Indexation- and Query Tool Integration in existing infrastructure –Institutions have their own house-style Allow to customize the look-and-feel –Institutions have specific metadata requirements Allow to define new metadata fields –E.g. FEICO -> Product Line

14. V4 Indexation- and Query Tool KPS KPS ClientSOAP InterfaceQuery Tool Ariadne Metadata Insert Advanced Query XML Configuration files

15. V4 Indexation- and Query Tool KPS KPS ClientSOAP InterfaceQuery Tool Ariadne Metadata Insert Advanced Query XML Configuration files Java layer GUI XML

16. V4 Indexation- and Query Tool KPS KPS ClientSOAP InterfaceQuery Tool Ariadne Metadata Insert Advanced Query XML Configuration files Java layer GUI XML XSLT Processor Look and feel (Stylesheet) HTML

17. V4 Indexation- and Query Tool

18. V4 Indexation- and Query tool Demo

19. Blackboard Own document repository with a (poor & optional) description of LO’s Building Block program –Offers an API to third parties to extend functionality of Blackboard –Their way of doing “open source”

20. Blackboard

21. User Support http://www.cs.kuleuven.ac.be/cwis/research/hmdb/bugzilla/index.cgi

22. Status & planning Almost finished –Web services layer All functionality is implemented Testing phase –Indexation- and Query tool Most functionality is ready Todo –Advanced query –Support of multiple languages –...