Administrator manual¶
- Installation
- Intended audience
- Technical Requirements
- Linux - Ubuntu 20.04 LTS (Focal Fossa)
- Windows
- Mac OS X
- Advanced configuration using Ansible
- Upgrading
- Check minimum requirements
- Read the release notes
- Make sure the dependencies are updated
- Install the latest version of AtoM
- Copy your old data
- Run the upgrade task
- Restore configuration changes
- Migrate translations
- Regenerate the digital object reference and thumbnail images (optional)
- Rebuild search index and clear cache
- Check the services configuration
- Restart services
- Set site base URL
- Upgrading with a custom theme plugin
- Recompiling after making modifications
- Start using the software!
- PHP execution limits
- Maintenance
- Command line tools
- Find out what version of AtoM you’re running
- Add a SuperUser (Admin) account
- Promote a user to an administrator
- Change a password
- Delete a user account from the command-line
- Check the status of your Elasticsearch index
- See the search index output for a description
- Regenerating derivatives
- Re-indexing PDF text
- Rebuild the nested set
- Generate slugs
- Rename slugs via command line
- Taxonomy normalization
- Manage physical storage locations
- Update the publication status of descriptions
- Unlink creators from child descriptions and reapply inheritance to hierarchy
- Move description relations from one authority record to another
- Delete a description
- Delete all draft descriptions
- Delete a digital object
- Delete temporary data (saved clipboards, access log, and downloads)
- Generate and cache XML for all archival descriptions
- Remove HTML content from archival description fields
- Export a list of terms linked to one or more descriptions from a taxonomy
- Auto-populate repository latitude and longitude values
- Installer
- Purging all data
- Generate an XML sitemap for search engine optimization
- Manually upload Archivematica DIP objects
- Generate a finding aid
- Run a generic PHP script
- Import and export from the command-line
- Bulk import of XML files
- Bulk export of XML files
- Validate CSV files via the command-line before import
- Import CSV files via the command-line
- Audit a CSV import
- Delete descriptions created by a CSV import
- Load digital objects via the command line
- Index your content after an import
- Export CSV files from the command-line
- Clear cache
- Web analytics
- Logging
- Web server logs
- Monitoring
- Data backup
- Common AtoM database queries
- Backing up the database
- Accessing the MySQL command prompt
- SQL maintenance, tuning, and logging
- General AtoM entity SQL queries
- Archival description SQL queries
- Get description record counts
- Update draft archival descriptions to published
- Globally update archival description fields
- Move descriptions to a different repository
- Bulk change levels of description
- Delete translations
- Get the source name and ID of a description for import updating
- Output the OAI identifier values of descriptions
- Digital object SQL queries
- Authority record and event SQL queries
- Term and Taxonomy SQL queries
- Note and Property table SQL queries
- Populate search index
- Tuning server parameters
- Asynchronous jobs and worker management
- Troubleshooting
- Figure out the nature of the problem
- Error logs and Debug mode
- Restarting services
- Monitoring active processes and checking execution limits
- Running AtoM’s most common maintenance tasks
- Dealing with data corruption
- Getting support
- Troubleshooting FAQ
- Why do I get a blank white screen?
- Why do I get a 500 (Internal Server) error?
- Why do I get a “Max execution time” exceeded error?
- Why do I get a “Allowed memory size” exhausted error?
- Why do I get a “Too many connections” error?
- Why do I get a “MySQL has gone away” error?
- Why do I get a “Parent Resource id: ‘XXXXX’ does not exist” error?
- Why do I get warnings when populating the search index?
- Why do I get a SearchPhaseExecutionException when trying to search?
- Why do I get a 504 Connection timed out error?
- Why am I seeing strange behavior in the AtoM treeview?
- Why can’t I upload (large) digital objects?
- Why can’t I log into AtoM?
- What should I do if I get an error that isn’t described here?
- Debug mode
- Elasticsearch
- Command line tools
- Customization
- Manage AtoM configuration files
- Theming
- Watermarking
- User authentication
- Localization
- Security