2.1. Archiving Methods (Videos)


SWING Seascape generates two different types of archives—the Full Archive and the Plain Archive

Additionally, the built-in SharePoint Upload Utility enables you to upload your PDF files and metadata from the Full or the Plain archives into SharePoint at any time. 

Full Archive

When you export a Notes database to a Full Archive, Seascape creates a new archive folder in the selected destination folder and names it using the database replica ID. The new folder is the root folder of your archive. 

The root folder contains the following files:
  • The PDF documents generated from the Notes documents
  • JSON files which store the Notes metadata
  • Notes attachments (Word, Excel, and similar files)
  • HTML, CSS, and other support files which form the archive’s browser interface 

For a complete overview of the Full Archive’s file and folder structure please see our article on the Full Archive Structure. The archive's browser interface is describe in the Full Archive Interface article. 

The Full Archive can be launched in any web browser by opening the index.html file found in the archive root folder. You can host your Full Archive locally, in a shared network folder, or any web server (eg. IIS, Apache, or other).  

The archive’s interface features all of the application views that you chose to export, and the views are sortable and searchable. Additionally, the links between documents are also preserved and remain functional.

It is also possible to export multiple databases to individual archives in a batch process. In this case Seascape will create multiple root folders in the Destination Folder that you select (one root folder for each database exported).

Furthermore, Seascape will in this case also generate a Database Catalog page which displays all the archives (in a similar way as the Notes Workspace displays Notes applications).

Note: The Seascape archives do not require Lotus Notes or Domino to run or display the exported data, since they are built on open standard formats and are completely standalone.

Here is a quick video showing how to export a few Notes databases to a Full Archive with Database Catalog:

Full Archive Demo



Plain Archive

A Plain Archive consists of Notes documents converted to PDF records, the XML files which store the Notes metadata (optional), and the Notes attachments. The archive is saved in a Destination Folder that you select.

You can use formulas in order to generate the PDF file names automatically, as well as automatically create a folder structure in the Destination Folder to store your documents.

By default, the Notes attachments are embedded in the created PDF records but you can also chose to convert the attachments to PDF, or to save them on disk (externally to the PDF records).

Each Plain Archive folder also contains two special files called the doclinks.html and doclinks.json. These two files are used to enable the document link feature and they contain the information on the variuos documents' IDs and their relative file paths. 

When you open a PDF file and click on a document link, the linked PDF file will automatically open in a new window (similarly as when clicking a doclink in Notes). 

Because the document linking feature relies on relative file paths, it is important to never alter the folder structure within the Plain Archive once it has been generated, since this can cause the document links to break. 

Here is a quick video showing how to export a Notes database to a Plain Archive:


Plain Archive Demo



SharePoint Archiving


The PDF files and the metadata from both the Full Archive and the Plain Archive can be easily uploaded into SharePoint using Seascape’s SharePoint Upload Utility. 

The SharePoint uploader moves the archive’s PDF files into a selected SharePoint library and it transfers the Notes metadata to the corresponding SharePoint properties. 

For more information on using the SharePoint uploader please see our article on Archiving in SharePoint.

Also here is a quick video showing how to export a Notes database and move it into SharePoint:


MS SharePoint Archiving Demo




Comments