Skip to main content
Version: Any 26

Archiving

This module configures how Any sends contents to an external archiving system: Vitam (in the SEDA format) or Stratow.

It defines which contents leave, how they file into the tree of the archiving system and which description metadata goes with them.

Vitam configuration (in the SEDA format)​

Creating a SEDA archive archives one or several documents, while keeping control over the root of the archive, its tree, and the documents that end up in it.

On each element to export, the archiving module indicates:

  • The title and the description in the archiving system
  • The list of the (typed) parents in the archiving system, to work out an absolute path (submission root) or a relative path (objects under the root)
  • The description and management metadata
  • The recursivity of the search for the elements to export (for instance, exporting the documents linked through a given relation).

At least two archiving modules must therefore be configured, one to configure the root and one, or several, to configure the contents to place in the archive and their locations.

The archiving flow must therefore hold two modules, one to define the root and one to define where and how to place the content or contents. The second module holds no server configuration, since it is defined by the root one.

If the submission is a submission root, tick the "Submission root" box.

Archiving package submission mode​

The SEDA package can be sent to an external queue or to VITAM (archiving product).

  • External queue: enter a queue name (if the queue does not exist, it is created).
  • VITAM: select the server access module* configured for VITAM.

* Choose a server access module to use this external service. The module is available from the general settings and centralizes, for every application, the location of the service and the authentication information.

SEDA package submission configuration​

The following parameters are needed to submit the SEDA package and must be valid on the archiving server when the SIP is submitted:

  • Archival agreement
  • Archival agency ID
  • Transferring Agency ID
  • Originating Agency ID
  • Submission Agency ID

Archive unit configuration​

Title: title of the package in the archiving system
Type: type chosen in the list
Description: description of the package

Content included in the archive​

If the selected root is a package, every component matching the archiving flow is automatically included in the SIP. Otherwise, the archive holds the root itself and every selected content matching the archiving flow.

Parent path​

Configure the location of the archive on the archiving server. A submission-root parent path is an absolute path, but a file parent path is a path relative to its submission root.

Title: enter a title (a template such as ${core.name} can be used)
Description: enter a description (a template such as ${core.name} can be used)
Type: select a type in the list

Archive additional metadata​

Name: name of the metadata in the archiving system
Template: value of the metadata. A template such as ${standard.title} can be used.

Stratow configuration​

Select the server access module* configured for Stratow.

* Choose a server access module to use this external service. The module is available from the general settings and centralizes, for every application, the location of the service and the authentication information.

Archive unit configuration​

File name: name of the file dropped into Stratow. A template such as ${core.name} can be used.
Type: not applicable for Stratow.

Reference kept in Any​

Click "Keep a reference into Any" to keep a reference of the archived content in Any, with its metadata. Once the content is archived, the archive managers can reach it from the "Archives" section.

Duration: if a duration is set, the metadata is deleted automatically from Any after the specified period. The archived file itself is not deleted.

Format to archive​

Choose to archive only the primary format or every format. When every format is archived, the primary format is archived with the "BinaryMaster" usage, the most recent PDF with the "Dissemination" usage and the thumbnail with the "Thumbnail" usage. The other formats are ignored.

Preferred format: select the format to archive, by order of preference in the list. When no format of this list is found, the primary format is archived.
Only primary format: the primary format is then archived.

Parent path​

Configures the placement of the archive in the archiving server.

Title: enter a title (a template such as ${core.name} can be used)
Description: enter a description (a template such as ${core.name} can be used)
Type: select a type in the list

Archive additional metadata​

Name: name of the metadata in the archiving system
Template: value of the metadata. A template such as ${standard.title} can be used.

Flows​

This module can be used in the following flow: