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
  2. Audit
  3. Creating an audit job

Object audit

PreviousDisk auditNextAudit job details

Last updated 3 years ago

Was this helpful?

When selecting object audit, a list with all the objects in the system will be loaded, so that those required for audit can be selected. To facilitate the selection task, the list comes with several filters: object name, range of object creation dates, and preservation area and plan.

Note: to facilitate the selection of many objects, when we click on check on the column ‘Object name’ in the object list, we can select all those in that current page or even select every object that has been filtered.

The second phase in the creation of an audit job presents information about the elements that have just been selected for audit and the options for the execution of the job.

In the list of objects selected for audit, we can access the object detail or select one more time those objects to be audited (out of those which had already selected in the previous step). Next, there is another section where the periodical execution of the disk audit can be programmed (daily, weekly, quarterly, biannual or annual, or with a date and time of execution start), or request a single execution as soon as possible, instead.

Note: for the configuration of the programmed tasks, audits in this case, we must take into account that the time configured is the period going from the finish of the execution of a task to the beginning of the execution of the next one.