|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||
See:
Description
| Interface Summary | |
|---|---|
| OlObjectClass | Enum: OlObjectClass Copyright: Copyright (c) 2003 Organisation: www.gnowsis.com |
| Class Summary | |
|---|---|
| OutlookAccessor | Access individual Outlook Objects. |
| OutlookAccessorFactory | |
| OutlookCrawler | Outlook Crawler Crawler that wraps Microsoft Outlook. |
| OutlookCrawler.OLConst | Constants from outlook |
| OutlookCrawlerFactory | Create a new Outlook crawler |
| OutlookDataSource | Data source class file. |
| OutlookDataSourceDetector | Detect Microsoft Outlook. |
| OutlookDataSourceFactory | Creates Microsoft Outlook Datasources. |
| OUTLOOKDS | Vocabulary File. |
| OutlookOpenerFactory | An outlook opener factory. |
| OutlookResource | Outlook Resource For each outlook class, a outlook resource class exists. |
| OutlookResource.Appointment | Copyright: Copyright (c) 2003 Organisation: Gnowsis.com |
| OutlookResource.Calendar | wraps an outlook calendar folder as vcalendar - leap of faith to do this. |
| OutlookResource.Contact | |
| OutlookResource.DistList | |
| OutlookResource.Document | |
| OutlookResource.Folder | |
| OutlookResource.Mail | |
| OutlookResource.Note | |
| OutlookResource.OutlookResourceSave | a OutlookResource that has a "save" object from redemption. |
| OutlookResource.RootFolder | |
| OutlookResource.Task | |
| VariantDate | copied from http://discuss.microsoft.com/SCRIPTS/WA-MSD.EXE? |
This package holds a crawler for Microsoft Outlook. It extracts the information from Outlook and represents it using our Data-Schema plus ICAL and VCARD as RDF. To use the Crawler, you have to:
The nifty formats we use for Outlook can be found in the doc/ontology folder. we used:
The outlook nag screen will popup and we cannot remove that. Even using Outlook Redemption, which removes this nag screen for many issues does not help when reading the e-mail adresses of e-mail recipients. It just doesn't work.
Not all data of outlook is available. Repeating events are only limited extracted, many other data items are missing. This is partly because we don't have the time to code all that. You are welcome to improve that!
Threading and Memory leaks. We see that when crawling Outlook data, Java and Outlook memory consumption rises significantly. Both may hang. Although we close all our handles, something is wrong. Also, do not use the crawler in more than one thread. Seriously, multithreading over a Java-Com bridge is no fun.
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||