LogoLogo
  • LIBSAFE Advanced Pro - User Administration Manual
  • Introduction
    • Basic concepts
    • General considerations
  • Access
    • Access with a two-factor authentication
    • Access via API to the application data
  • General browsing
  • General system configuration
  • Home
  • Catalog
    • Catalog – Browse catalog by object
    • Catalog – Browse by tree
    • Catalog – Search catalog by object
    • Catalog – Object detail
      • General Information
      • Metadata
        • Metadata descriptor value editing
        • Comparing updated metadata set with original
        • Additional information on metadata
      • eXtended Metadata
        • Functional concepts
        • Technical concepts
        • Interface schema
          • Metadata type configuration
          • Sets and Block configurations
        • Creating and editing extended metadata
          • Structured type block
          • Free type block
        • Special links into blocks to an object’s files
        • Visualisation and download of structured blocks
      • File and folder structure
        • Object Explorer
        • Retrieving a complete object by applying a DIP profile
        • Files’ details
      • Object health
      • Storage
      • Data Integrity
        • Provenance metadata and events (Event management)
      • Executing Transfer Connectors
      • Object history
    • Catalog – Object group detail
  • Ingestion
    • Ingestion – Creating a new ingestion job
    • Ingestion – Execution of an ingestion job
  • Retrieval
    • Object retrieve from catalog
    • Retrieval from an object detail
    • Retrieve job details
  • Active preservation
    • File format evolution jobs
      • Manual object evolution
      • Approve evolution jobs selected by the system
    • Digital signature jobs
    • Object metadata update
      • Update via web interface
      • Update through a massive update job
        • Structure and syntax of massive metadata update files
        • In multiple files
        • In a single file
        • Basic conditions of the metadata update operations
        • Available metadata operations
      • Metadata update job detail
  • Document repository
  • Advanced options
    • Audit
      • Creating an audit job
        • Disk audit
        • Object audit
      • Audit job details
    • Reports
      • Reports generation
      • General information on objects and status of the system
      • Customized Reports
      • Evolution of ingestion jobs and preserved objects
      • Ingestion job report
      • Audit job reports
      • METABASE reporting
  • Other user sections
    • User configuration
    • Notifications panel
Powered by GitBook
On this page

Was this helpful?

  1. Advanced options

Audit

PreviousAdvanced optionsNextCreating an audit job

Last updated 3 years ago

Was this helpful?

Audit jobs are the processes used in LIBSAFE to check that any object is correctly preserved in the audit moment. This kind of job should be done periodically, and the configuration of the time frame should be decided either by the preservation administrator or the system administrator.

It may also be useful to carry out a manual audit at a given moment, be it of a storage system, a preservation area or a specific collection of objects. The two first types of jobs are generated preferably from the audit main page, whereas the third one must be created after selecting from the results page with the catalog functionality.

The main Audit page shows lists for audit jobs running, programmed, latest executed, with integrity faults, and with errors. The type of audit jobs is indicated out of these possible options: object audit, disk audit, and automatic audit from an ingestion job.

  • An audit job with integrity faults is the audit job that detects errors in the preserved objects, but as an audit job it is finished successfully.

  • An audit job with errors is the audit job that cannot be run successfully, and needs not determine if all or part of the audited objects are correctly preserved.

Should audit jobs appear under one of these two states, the system administrator will have to be consulted, who in turn will have to investigate what caused the failure and make the necessary adjustments (with or without the assistance of the LIBNOVA consultants).

Audit jobs will include the following checks:

  • All the copies of an object are equal.

  • The hash has not changed.

  • The structure of the metadata saved is correct.

  • Each one of the objects supposed to be found in an expected path is there.

In an audit job, it is not necessary to perform certain actions, such as rechecking a metadata structure, recharacterizing a format, validating a format or reviewing a signature, since any change producing such effects would mean a change in the file formation, and that would reflect immediately in a change of the file hash.

Likewise, audits of formats and signatures are independent processes that can be initiated from information saved in the cataloging system of LIBSAFE, without having to inspect the objects.