1 / 25

D15: Value Added Publications (VAP) pilot

D15: Value Added Publications (VAP) pilot. IST- 200 1- 3 3 127. IST- 200 1- 3 3 127. www.SciX.net. Content. D15 progress – deliverables Scix VAP principles Demonstrations Scix Interface Content syndication Management interface Conclutions. Introduction.

oro
Download Presentation

D15: Value Added Publications (VAP) pilot

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. D15: Value Added Publications (VAP) pilot IST-2001-33127 IST-2001-33127 www.SciX.net

  2. Content • D15 progress – deliverables • Scix VAP principles • Demonstrations • Scix Interface • Content syndication • Management interface • Conclutions

  3. Introduction D15 deliverables - prototypes: • Content mangement system • Syndication server • Syndication client (server-application) • Demonstrator - IBRI Rheocenter, Centre of Excellence at IBRI

  4. Introduction Industry editor, publisher Value added publications Client applications (MS-WORD, OpenOffice) WORD DOC, HTML,XML SciX Services Web client Repository service HTTP file upload SciX API proxy Content Management System XML protocols over HTTP Content Store Syndication server Syndication client data HTTP / XML_RPC / RSS HTTP / RSS & File Download RSS enabled Web-application, Web-portal orWeb-server Industry User D15 deliverables:

  5. Introduction Progress • CMS –Slide implementation in progress, Turbine appl. running, role based user management • SS,SC in prototype version • Interface to CMS .. to be done • Subscription catalogues –content map implemented as XML-vocabulary .. to be done • Demonstrator IRBI Rheocentre – Concrete information portal – Layout done, based on Uportal software

  6. Introduction Implementation • Apache JakataTurbine web-application framework • Content management system - Apache Jakarta Slide, integrated in Turbine as a service implementation • Demonstrator IRBI Rheocentre – Concrete information portal - based on Uportal software

  7. Introduction Prototype

  8. Introduction Scix VAP principles • Habygg.is IBRI information service based on VAP principles • IBRI Technical data sheets • Byggdoc in Sweden www.byggdoc.se

  9. Introduction IBRI habygg.is

  10. Introduction IBRI Technical Data Sheets

  11. Demo 1 Demo 1 • Goal to demonstrate the VAP interface to Scix archives

  12. Demo 1 Scix interface • Connect to Scix archive • set/get Scix archive connection info • SearchScix archive • set/get search profile • Download files – full text • set/get bookmark • Download metadata • get citation index • get bibliographic record

  13. Demo 1 Scix Interface

  14. Demo 2 Demo 2 • Goal to demonstrate syndication of content

  15. Demo 2 INTERNET VAPCMS VAPCMS Syndication Syndication Client Syndication Server New updates syndicated by RSS New updates published by RSS Document uploaded demonstrated To be added CMS client Web-Application

  16. Demo 2 Update available RSS Update Files OK I am available to receive Send me update Send me files XML-RPC protocol Client mode Server mode Server mode Client mode VAP Client VAP Server

  17. Demo 3 Demo 3 • Managing the servers • Adding a syndication client • Adding a subscription etc...

  18. Demo 3 Server Management Interface

  19. End Conclutions • Demonstration of early prototype M21 • Finalize pilot in M23 • Implement IBRI Rheocenter in M23 • Clean-up code - publish in M24 -

  20. End The End more information atwww.SciX.net

  21. Q&A • Why is Woda not used in VAP? • Which Scix services is VAP using

  22. Architecture Content Management System User workspace client Admin client WebDAV. HTTP Jakarta Tomcat Turbine SciX Repository SciX VAS API SciX API XML-RPC / XML SciX VAS user mgr resource mgr workflow mgr SLIDE API JNDI security lock structure content macro Jakarta - SLIDE SLIDE STORE API JTA helpers - adapters File System JDBC MySQL Indice SLIDE Store

  23. Architecture Syndication Server HTTP client RSS client RSS server Management API Dispatcher Formatter RSS/HTML Aggregator Syndication engine Server Manager Scheduler Schedule Manager Transaction Manager Syndication Registry API CMS API Subscriptions Catalogue Log Content store

  24. Architecture Syndication data model SyndicationClient where subscriptions 1..* Subscription Catalogue what when Schedule SubscriptionLog

  25. Review comments • 9a pt.6 • The “logical architecture” of the SciX VAS software in fig. 3 on p. 13 of the paper (and its details in fig. 4a on p.16) is a logical architecture in itself (namely the common open source RSS architecture); but it is not imbedded in an overall logical architecture. The CMS architecture in fig. 4 on p. 15 is a logical architecture (the common open source implementations of the Slide framework), too; but what would be interesting for the SciX project were the definitions of relations of inter-working with the other parts of the system (beyond the trivial statement that relevant interfaces have to be provided, see above). • 9b • Must use knowledge management • The local/remote distribution is not present • The mechanism of syndication adopted is not present • Eg: search: what the user interface will offer • What key web services will be activated • How the query will flow in the system • How it will be validated and trusted • How if the request goes to a service which becomes not available • Where is the access permission granted (locally, globally? Single sign in) • Where logging will take place • Where billing will take place

More Related