Maarch RM 2.8: A New Version Is Now Available!

Maarch announces the release of major version 2.8 of its Electronic Archiving System software, Maarch RM

This brand-new version brings a host of new features to go even further in managing your archives and binding documents.

Extraction, Indexing, and Full-Text Search

New functions allow the text of preserved digital documents to be indexed and searched via the search bar.

A new type of component makes it possible to integrate text extraction engines from digital documents. For example, the Apache Tika software can process tagged-content, office, and PDF documents, while the Tesseract OCR engine can recognize text present in images.

Maarch RM incorporates the text extracted during transfer or preservation into the indexed metadata, allowing users to easily search for documents across the full text.

Query Builder

The registry screen allows users to build queries using archive profile metadata. Each metadata field can be added and tested for equality or a range depending on its type; if the same metadata field is added multiple times, the engine considers that at least one of the tests must be satisfied (OR).

Favorites Collection

Collections are arbitrary sets of archive units, populated by the user, that simplify management actions.

The management screen allows managers to flag archive units from the results list in order to group them into a favorites collection. A new screen makes it possible to display favorites and carry out management operations such as access requests, disposal, or modifying management rules, for example.

Retention Period and Active Files

It is now possible to extend the retention period of files while they are still being added to.

The administrator can now define, for archive profiles of type “file,” that the start date for calculating the retention period expiry of the corresponding archive units must be updated each time a document is added to the file.

Customizing notifications

The event logging service now includes a brand-new email notification system.

It is now possible to dynamically determine the list of recipients for each notification: producer, manager, administrator, for an agent or a department.

In addition, the messages sent use notification templates in text or HTML format, including variable information from the event, the objects affected, or the agents involved in the event.

Need to Know

Behind this well-established expression lies the ability for users to discover the existence of archive units even if they don’t have consultation access to them, so that they can make an access request.

The administrator can now define, for archive profiles, which ones allow the corresponding archives to be displayed in search results, independently of users’ access rights or their releasability, thus allowing users to be aware of the existence of a file or document and, where applicable, to request access.

Modifying the Producer

Archive managers can now modify the identification of the producer for archive units after their transfer, in order to better track the evolution of the organization’s activity over time.

Digital Document Search

The API includes a new service that allows digital documents to be searched directly using technical criteria such as file name, format, or size.

This search does not bypass the rules governing access to information, since only technical metadata is accessible, and access rights to content remain guaranteed by the consultation functions, which are unchanged.

SEDA 2 Metadata Modification

A new form allows managers to modify the metadata of archive units transferred via SEDA 2 format packages, similar to the existing form for SEDA 1.0 modifications. The goal is to constrain the model to the one that will be accepted for all output types: access, outgoing transfer, and return.

T@ct API Recovery Connector

A new connector allows the reception of packages returned from the T@ct platform by API.

These packages contain restitution messages in the SEDA 0.2 standard, using the operator’s repositories rather than those of the target SAE, and containing a number of non-conformities with Maarch RM’s requirements.

The connector notably makes it possible to convert this message into a valid SEDA 2.1 transfer slip and to transform the reference values from the source platform into internal repository values.