LogoLogo
  • LIBSAFE Advanced Pro - System Administrator Manual
  • Introduction
    • Basic concepts
    • General considerations
  • System configuration
    • Storage
      • Storage groups
      • Disks
        • Different storage system types and their integration in LIBSAFE
      • Datamover
    • Digital signature profiles
      • Certificates for the digital signature service
    • Access
      • Users
        • Two-Factor Authentication (2FA)
      • Groups
      • User permissions
    • Alarms and Notifications
      • Alarm definition
      • Configured alarms
        • Configuring an alarm: example 1
        • Configuring an alarm: example 2
      • Notifications panel
    • Extras and tools
      • Programmed tasks
      • Logs manager
      • File management
      • Database management
      • Database management (read-only mode)
      • Web interface configuration variables
      • Configuration variables
      • API system services
      • Server cluster - Parallelization
        • Details of activity in one node
        • Editing or creating a node and its associated services
        • Node deactivation
        • Deleting nodes
        • Processing Cluster customization
      • SAML integration as a SSO (Single Sign On) when login in LIBSAFE
    • License
  • Preservation configuration
    • Ingestion sanitizers
      • Ingestion sanitizers detail
      • Ingestion sanitizer editing
    • Preprocessors
      • Preprocessor details
      • Creation of the preprocessor
      • Preprocessor editing
    • Ingestion checks
      • Ingestion check details
      • Creation of the ingestion check
      • Ingestion check editing
      • Main ingestion checks
    • Metadata filters
      • Metadata filter detail
      • Creation of metadata filter
      • Metadata filter editing
    • Dissemination Information Package (DIP) profiles
      • DIP profile detail
      • Creation of DIP profiles
      • DIP profile edition
    • Connectors
      • Connector Detail
      • Create a new connector
      • Edit a connector
    • File formats
      • File format detail
    • File format characterizers
      • File format characterizer detail
    • File format validators
      • File format validator detail
    • File format evolvers
      • File format evolver detail
  • Frequently Asked Questions (FAQ) and additional notes
Powered by GitBook
On this page

Was this helpful?

  1. System configuration
  2. Extras and tools

Database management

PreviousFile managementNextDatabase management (read-only mode)

Last updated 3 years ago

Was this helpful?

LIBSAFE provides an integrated layer in the very web interface to access the database. Available access and operability is managed by the phpMyAdmin software, together with the user for whom access is requested.

Database management is accessible from the Systems configuration section, by clicking on the Database management link. The following image shows the login screen that will appear.

Note: the user / password we will have to enter to access is not about a LIBSAFE user, but a user / password in MySQL.

Note: every functionality and action we may be able to perform against the database will be defined by the privileges the user may have granted in MySQL. If we try to perform actions for which we have no privileges, we will obtain error messages indicating that.

For any doubt or question related to the database management control panel, we can approach the LIBSAFE consultants, or access available documentation in the official site of phpMyAdmin.

Once logged in, the system shows the initial screen where we can see all available actions, existing databases and additional information on the databases.

The interface shown allows for all the functions we might be able to carry out with phpMyAdmin, only that we will have the privilege restrictions assigned to the user with whom we are accessing said panel.

It is recommended that access to this database management control panel (and by extension any database user with sufficient privileges) be restricted to only a few administrators in order to avoid, as much as possible, potential problems which might arise from a poor management of the database.