The conversion of all Lotus Notes database content (application database, mail database, QuickR database ...) into an open format (XML/HTML/XSL) requires the installation of the Notes Extractor product, which includes a Notes setup database (NotesExtractor.nsf) and an executable (NotesExtractor.exe). The executable setup is done in the NotesExtractor database by creating Setup documents. The product can be used on a Domino server or on a Notes client desktop. In any case, XML/HTML/XSL files are created on the hard drive of the machine hosting the executable.
The data from the Notes databases is converted into market standard formats appropriate to its type:
- XML for structured data (Text/Number/Date fields) and document properties (creation date, ID, security ...).
- HTML for rich information (Rich Text or Mime) with preservation of styles, tables, graphics, sections, tabs, links ...
- GIF / JPEG / PNG for images (individually stored: Single Instance Storage).
- EML for messages.
- XSL for data display elements (Form).
- Attached files and OLE objects are directly detached on disk.
In order to preserve the information related to Notes documents security (reading, modification, deletion), user identities (Notes names of FullName type) can be translated according to the target directory (UPN for Active Directory). Notes Extractor also translates the names of groups present in document fields and analyzes the database ACLs in order to solve [Roles].
Indexes of Notes databases' views and folders are exported as XML or HTML files, so that the information related to the document structure is preserved.
If the exported Notes databases have a known template (Mail, QuickR, Library, TeamRoom, Forum databases …), Design elements used for data display (browsers, views, forms) are provided as standard in the Notes Extractor product (as XSL files). If the databases use an unknown template (application database), Notes Extractor will automatically convert database forms and views into XSL files to allow document display.
The conversion result can be used locally with a Web browser (Internet Explorer, FireFox, Chrome) or directly integrated on a Web server. This way, the navigation in the application is done in read-only mode. The result file tree can also be injected using dedicated tools into application architectures such as Microsoft SharePoint, Google Apps, Alfresco, etc.