Page History

...

		<explorerTask name="Archive Catalogue">
			<iconFile>Archive.png</iconFile>
			<mnemonic>A</mnemonic>
			<displayConfigFileName>ArchiveModuleDisplay</displayConfigFileName>
			<toolbarTask>false</toolbarTask>
			<menubarTask>true</menubarTask>
			<accelerator>ctrl A</accelerator>
			<loadAtStartup>false</loadAtStartup>
		</explorerTask>

Create a new event tab

The first tab in the display can be used to create/read/update or delete events. Adding an event doesn't add data to the archive but marks a part of the data in the archive as being part of an event.

Data which is part of an event is treated differently than regular data in the archive. Data which is related to an event can for example have an longer expiry time. 

Image Removed

Search for event

The second tab in the display can be used to search for events.

Image Removed

The download button can be used to download the data which is related to that event. The 'paperclip'-button can be used to download attachments of the event.

Search and download datasets

The third tab of the display is used when the user wants to search and download from the archive without using events.

Image Removed

It is possible to select which type of dataset the system should look for. In addition a search period can be defined.

The selected data set type determines how the search period is used. For example for messages the search period will be used to search for messages which are created within that period.

However when dataset type forecast is selected the search period will be used to search for all forecasts for which the time zero is in between the search period.

The search button will execute a search for datasets in the archive.

The download and import data button will download the data but also import the data after the download.

The ArchiveModuleDisplay configuration

The configuration file for this display resides in the DisplayConfigFiles folder. It primarily contains references to the archive server, while it also specifies tte download folders, i.e. the destination folders for data being downloaded.

Image Added

While the xsd is mostly self explaining some remarks can be made:

• it is recommended to use global properties to define the server details and the download folders.
• When Historical Events are defined as an event type, the defaultHistoricalEventTimeStep needs to be defined. This time step becomes part of the historical event definition as the system needs to know which of the archived observed timeseries has the proper timestep for use as a histroical event.
• Not all archive systems will hold/store all dataset types. To prevent confusion with the user, the search options can be restricted to a limited list of dataset types that can be searched for, using element searchDataTypes.

For snapshots or configuration datasets however a new FEWS instance will be started with the downloaded snapshot or configuration. The download button will only download the data without importing it.