Page tree
Skip to end of metadata
Go to start of metadata

Teamstudio Export can generate a static HTML site from an archive. The site contains a representation of all of the views in the database, including categorization, along with a simple document viewer. The document viewer does not attempt to recreate the look and feel of the original Notes application, but provides an effective way to view the data. For most situations, this is quite sufficient to retrieve valuable information from archived data.

Generating an HTML Site

To export archives to HTML, select the database or databases to be exported from the main window, right-click on one of the selected databases and select Export to HTML from the context menu. As with standard Windows controls, you can use Ctrl-Click to select a range of databases and Alt-Click to add a database to the selection. You do not need to wait for all existing export operations to complete before adding more, but note that Export will run at most 3 tasks at once and all other tasks will be queued until earlier operations have completed.

You can view the status of any active and queued tasks from the Progress Window. Please see that page for details of how to handle errors and warnings encountered during exporting.

HTML sites will be generated inside the HTML Output Folder specified in the Configuration.

HTML sites are self-contained and have no runtime requirements. You can copy the site folder to another location on the file system or onto a web server and view it with any modern browser. While a Teamstudio Export license is required to generate the site, there are no ongoing licensing or runtime costs to distribute and view generated sites.

Viewing an HTML Site

Once an archive has been exported to HTML, you can view the site by right-clicking on the database in the main window and selecting View HTML from the context menu. This will launch your default browser to the home page of the site.

Clicking on the database will show a list of views in the database, along with a count of documents in each view.

Clicking on a view will show a representation of the view. This does not attempt to fully match the look of the original Notes view, but does contain all of the data and matches most of the original format.

Clicking on a document in the view will show a representation of the document. The document is shown as a table with Notes item names in the first column and data values in the second. Rich text is supported, including images and attachments, although some formatting details may be lost.

Doclinks within a single database are supported. Doclinks between databases are also supported as long as the target database has been archived. Of course the target database will also have to be exported to HTML for the doclink to function correctly, but the doclink will still be created as long as an archive exists for the target database.

If you have a group of databases that contain doclinks between themselves, you should archive all of the databases before exporting any of them to HTML. This ensures that all doclinks will be exported correctly.

Full Text Search

Starting with Export 2.0, databases exported to HTML are full-text searchable. To start, select the view that you want to search and click the magnifying glass to show the search box. The search will be performed when you hit the Enter key. All documents in the view that match all of the search terms will be displayed. The documents are sorted based on the the strength of the match, which is determined by how many matches are in the document, and how common the matched words are in the database. For example, matching a search term that only appears a few times in the database is a stronger match than matching a common word like the.

The full text index contains all words of 2 or more letters found in text or rich text fields. It does contain 'words' that are a mixture of letters and digits (such as 3M) but does not contain numbers or dates. It also only matches search terms found at the beginning of words. For example, searching for at would match attach but would not match cat.

The search index does not contain text within attachments.

 

  • No labels