Administrator manual

From Archivematica
(Difference between revisions)
Jump to: navigation, search
Line 82: Line 82:
= Customization =
= Customization =
* Workflow processing decisions can be made in the processingMCP.xml file. [ See here.]
* Workflow processing decisions can be made in the processingMCP.xml file. [ See here.]
* Workflows are currently created at the development level. [[MCP|See MCP for more details.]]
* Workflows are currently created at the development level.  
*: Some resources avialable
*:* [[MCP_Basic_Configuration]]
*:* [[MCP]]
*:* [[Creating_Custom_Workflows]]
*:* [[Development]]
* Normalization commands can be viewed in the presveration planning tab.
* Normalization commands can be viewed in the presveration planning tab.
* Normalization paths and commands are currently edited/created at the development level. [[Transcoder|See transcoder for more details.]]
* Normalization paths and commands are currently edited/created at the development level. [[Transcoder|See transcoder for more details.]]

Revision as of 17:16, 27 August 2012

Main Page > Development > Administrator Manual




  • Currently, Archivematica does not support upgrading from one version to the next. A re-install is required.


User management

The dashboard provides a simple cookie-based user authentication system using the Django authentication framework. Access to the dashboard is limited only to logged-in users and a login page will be shown when the user is not recognized.

If the application can't find any user in the database, the user creation page will be shown instead in order to create a new account. Users can be also created, modified and deleted from the Administration tab. Also, an user can be temporary disabled in case that you want to block its access but keep its data.

Archivematica uses PBKDF2 as the default algorithm to store passwords. This should be sufficient for most users: it's quite secure, requiring massive amounts of computing time to break. However, other algorithms could be used as the following document explains: How Django stores passwords.

Our plan is to extend this functionality in the future adding groups and granular permissions support: see issue 922 to read more about it.

User manual

Dashboard administration tab

The Archivematica administration pages allow you to configure application components and manage users.

AtoM DIP upload

Archivematica can upload DIPs directly to an AtoM website so the contents can be accessed online. The AtoM DIP upload configuration page is where you specify the details of the AtoM installation you'd like the DIPs uploaded to (and, if using Rsync to transfer the DIP files, Rsync transfer details).

The parameters that you'll most likely want to set are url, email, and password. These parameters, respectively, specify the destination AtoM website's URL, the email address used to log in to the website, and the password used to log in to the website.

AtoM DIP upload can also use Rsync as a transfer mechanism. Rsync is an open source utility for efficiently transferring files. The rsync-target parameter is used to specify an Rsync-style target host/directory pairing, "" for example. The rsync-command parameter is used to specify rsync connection options, "ssh -p 22222 -l user" for example.

To set any parameters for AtoM DIP upload change the values, preserving the existing format they're specified in, in the "Command arguments" field then click "Save".

ContentDM DIP upload

Archivematica can also upload DIPs to ContentDM websites. Multiple ContentDM destinations may be configured.

For each possible ContentDM DIP upload destination, you'll specify a brief description and configuration parameters appropriate for the destination. Possible paramters include %ContentdmServer%, %ContentdmUser%, and %ContentdmGroup%.

When changing parameters for a ContentDM DIP upload destination simply change the values, preserving the existing format they're specified in. To add an upload destination fill in the form at the bottom of the page with the appropriate values. When you've completed your changes click the "Save" button.

Transfer source directories

Unlike previous versions, Archivematica v0.9 allows you to start transfers using the web interface rather than the operating system's file browser. Source files for transfers, however, can't be uploaded using the web interface: they must exist on volumes accessible to the Archivematica server.

When starting a transfer you're required to select one or more directories of files to add to the transfer. To speed up the process of selecting directories, Archivematica allows you to specify "source directories". A source directory is a directory in which files and directories likely to be added to a transfer are present.

To add a source directory, while on the transfer source directories page, simply click the folder icon to expand the starting directory and navigate the interface until you find a directory you'd like to select as a source directory. Once you've found a suitable source directory, click the "Add" link to the right of the directory and it will be added.

The remove a source directory, simply click the "Remove" button to the right of it in the source directory path list.

Processing configuration

When processing a SIP or transfer, you may want to automate some of the workflow choices. Choices can be preconfigured by putting a 'processingMCP.xml' file into the root directory of a SIP/transfer. The processing configuration administration page allows you to configure the default 'processingMCP.xml' that's added to a SIP or Transfer if it doesn't alreay contain one. If a SIP or transfer is submitted with a 'processingMCP.xml' file, however, processing decisions will be made with the included file.

Pre-configured choices made here are based off the choices that appear in the dashboard.

The format is:

            <appliesTo>Workflow decision - send transfer to quarantine</appliesTo>
            <goToChain>Skip quarantine</goToChain>

Where appliesTo is the name of the job presented in the dashboard, and goToChain is the desired selection. Note: these are case sensitive.


The user administration page allows you to manage which uses have access to Archivematica and what level of access they have. Standard users are able to access all sections of the interterface except for the administration section. Only the first user created will have administrator capability.

You can add a new user to the system by clicking the "Add new" button on the user administration page. By adding a user you provide a way to access Archivematica using a username/password combination. Should you need to change a user's username or password, you can do so by clicking the "Edit" button, corresponding to the user, on the administration page. Should you need to revoke a user's access, you can click the corresponding "Delete" button.



Data backup

  • How to protect your data from disaster.


  • It is recommended to change the default passwords.
    • The ICA-ATOM/ContentDM passwords can be set in the administration tab in the dashboard.
    • The database connection credentials can be set in the /etc/archivematica/archivematicaCommon/dbsettings. These will need to a mysql user with permissions to the MCP database.
  • Database
  • The database user
  • /etc/archivematica/archivematicaCommon/dbsettings
  • The dashboard config file?
  • Content DM
  • ICA-AtoM
  • Archivematica does not presently support secured sockets. See Issue 990, Issue 690 Because of this, it's highly recommended to run Archivematica on a secure, isolated network.


Frequently asked questions

Discussion group

Personal tools