StarOffice 6 & Tamino & non-xml indexing

Transcription

1 StarOffice 6 & Tamino & non-xml indexing technical presentation Software AG, Darmstadt

2 Overview Motivation Concept Architecture StarOffice Client StarOffice Future Scenarios 2

3 MS Office vs. StarOffice? Microsoft Office Sun StarOffice Office Package incl Office Package incl. relational Share point Server n/a relational Database Access Database ADABAS D (WebDAV based for collaboration) Indexing Server for text- n/a retrieval based on document content OS OS Windows only Windows Linux Solaris 3

4 MS Office vs. StarOffice incl. Tamino Sun StarOffice Microsoft Office Office Package incl. relational Office Package incl Database ADABAS D relational Database Access Full Tamino WebDAV Server (WebDAV based for collaboration) Solution to Tamino XML Server Indexing Server for textretrieval based on document compete content OS OS against Microsoft Share point Server Windows Windows only Linux Solaris 4

5 SUN s StarOffice & Tamino Offer a full office package solution Include features that are part of competitors offerings already Promote partnership SUN / Software AG Tamino XML Server for XML & SQL storage (SAG) Adabas D (personal edition with limitations) is part of the StarOffice 5.x package Adabas D (personal edition with limitations) will be part of the StarOffice 6.x package 5

6 Reducing Complexity Ma nag ad Checkin Checkout Document Management 6 Da t Da t Vie wh a EB TM L con ten View HTML Query Retrieve data e Lo SQL St or ew t a.csv.doc.xls Publish WEB content HTML.wmf Filesystem WWW-Server

7 Reducing Complexity (2) Q Sto uery Ma re nag e W Data EB con ten Re t trie Loa ve d Vie d Da ata w H ta TM L 7 F FAX D P L M L M W HT TP SM

8 Concept: Tamino non-xml indexing Document Repository StarOffice Dokument Metadata + Content Original 8 XML

9 Concept (2) StarOffice Writer MS-Word PDF <?xml version= 1.0?> <properties mimetype= application...> <content>...some text...</content> <meta> <initial-creator>john glen</initial-creator> </meta> </properties> <?xml version= 1.0?> <properties mimetype= application...> <content>...some text...</content> <meta> <initial-creator>john glen</initial-creator> </meta> </properties> <?xml version= 1.0?> <properties mimetype= application...> <content>...some text...</content> <meta> <initial-creator>john glen</initial-creator> </meta> </properties> StarOffice Spreadsheet MS-Excel Multimedia (pic,mp3,video) <?xml version= 1.0?> <properties mimetype= application...> <content>...some text...</content> <meta> <initial-creator>john glen</initial-creator> </meta> </properties> <?xml version= 1.0?> <properties mimetype= application...> <content>...some text...</content> <meta> <initial-creator>john glen</initial-creator> </meta> </properties> 9 <?xml version= 1.0?> <properties mimetype= application...> <content>...some text...</content> <meta> <initial-creator>john glen</initial-creator> </meta> </properties>

10 Concept Make Dokument content and Meta Data accessible via XML Gain (readonly) meta information from the StarOffice Dokument Use XQuery/DASL using the XML information to find and read non-xml content from Tamino Store non-xml and XML together Zero Learning Curve for Users: Access via File System (via WebDAV) 10

11 StarOffice: User View 11

12 Demo 12

13 Demo 13

14 Demo 14

15 Demo 15

16 Demo 16

17 Demo 17

18 Demo 18

19 Demo 19

20 Demo 20

21 Demo 21

22 Where do you want to go tomorrow? 22

23 Standard non-xml XML schema One XML schema that fits all XML for all mimetypes Content and Metadata always in the same location Some standard fields in the metadata i.e. creator, last-modified, keywords, title etc. therefore you can query for a non-xml document independant of its mimetype if you stick with the standard metadata fields There is also a well-defined place for metadata that exceeds the standard Predefined Schema can be used in any other schema using import 23

24 X-Query _xql=...[properties/meta/keywords~= Tamino ] Finds any non-xml document of any type that has at least one keyword Tamino specified. The result could contain documents of type MS-Office, Staroffice, Pictures, Videos or any other type with that information. 24

25 Possible Future StarOffice & Tamino (2)?? Document or Content Management publishing StarOffice content in different types of media ( publish to anywhere ) use StarOffice with Tamino SQL Digital Signatures access to other data sources (ERP) building new documents from textblocks Demo on Cebit and SUNs Hi Tech (San Francisco) 25

26 Future Scenarios Mobile StarOffice Document Repository XML EntireX Backend System 26 Transformation Original PDA Portal CMS

27 Future Scenarios Browser Search and list documents Show document content 27

28 Future Scenarios Document Browser Title Creator etc. (configurable) Topic View Preview 28

29 Future Scenarios Mobile Document Handling Search for a document via mobile Device start an action for the document Show (parts) online Send original via /fax 29

30 Future Scenarios Text Components Create new Documents from existing ones Get Content Management out of a Standard Office Package! 30