Difference between revisions of "Administrator manual"
(Minor changes) |
|||
| Line 2: | Line 2: | ||
| − | =Installation= | + | = Installation = |
* [[Installation|Instructions for installing the latest build of Archivematica on your server]] | * [[Installation|Instructions for installing the latest build of Archivematica on your server]] | ||
| − | =Upgrading= | + | = Upgrading = |
* Currently, Archivematica does not support upgrading from one version to the next. A re-install is required. | * Currently, Archivematica does not support upgrading from one version to the next. A re-install is required. | ||
| − | =Users= | + | = Users = |
== User management == | == User management == | ||
| Line 19: | Line 19: | ||
Our plan is to extend this functionality in the future adding groups and granular permissions support: see issue 922 to read more about it. | 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== | + | == User manual == |
* [[User_Manual|Instructions importing of data into Archivematica]] | * [[User_Manual|Instructions importing of data into Archivematica]] | ||
| − | =Dashboard administration tab= | + | = Dashboard administration tab = |
http://localhost/administration/processing/ | http://localhost/administration/processing/ | ||
| − | |||
| − | ==ContentDM DIP upload== | + | == AtoM DIP upload == |
| − | ==Transfer source directories== | + | |
| − | ==Processing | + | == ContentDM DIP upload == |
| + | |||
| + | == Transfer source directories == | ||
| + | |||
| + | == Processing configuration == | ||
| + | |||
This is the defaul 'processingMCP.xml' that is included, in the root directory, when processing a SIP or Transfer. If a SIP or transfer is submitted with a 'processingMCP.xml' file processing decisions will be made with the included file. Pre-configured choices made here, are based off the choices that appear in the dashboard. | This is the defaul 'processingMCP.xml' that is included, in the root directory, when processing a SIP or Transfer. If a SIP or transfer is submitted with a 'processingMCP.xml' file processing decisions will be made with the included file. Pre-configured choices made here, are based off the choices that appear in the dashboard. | ||
| Line 39: | Line 43: | ||
</pre> | </pre> | ||
Where appliesTo is the name of the job presented in the dashboard, and goToChain is the desired selection. Note: these are case sensitive. | Where appliesTo is the name of the job presented in the dashboard, and goToChain is the desired selection. Note: these are case sensitive. | ||
| − | |||
| − | =Importing= | + | == Users == |
| − | * [[User_Manual| | + | |
| + | = Importing = | ||
| + | * See the [[User_Manual|user manual]] | ||
* Also note the ability to include a processingMCP.xml file [[Administrator_manual#Processing_Configuration|See dashboard.]] | * Also note the ability to include a processingMCP.xml file [[Administrator_manual#Processing_Configuration|See dashboard.]] | ||
| − | =Customization= | + | = Customization = |
* Workflow processing decisions can be made in the processingMCP.xml file. [https://www.archivematica.org/wiki/Administrator_manual#Processing_Configuration See here.] | * Workflow processing decisions can be made in the processingMCP.xml file. [https://www.archivematica.org/wiki/Administrator_manual#Processing_Configuration See here.] | ||
* Workflows are currently created at the development level. [[MCP|See MCP for more details.]] | * Workflows are currently created at the development level. [[MCP|See MCP for more details.]] | ||
| Line 51: | Line 56: | ||
* 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.]] | ||
| − | =[[Data backup]]= | + | = [[Data backup]] = |
* How to protect your data from disaster. | * How to protect your data from disaster. | ||
| − | =Security= | + | = Security = |
* We highly recomend chaning the default passwords. | * We highly recomend chaning the default passwords. | ||
[LIST OF DEFAULT PASSWORD LOCATIONS] | [LIST OF DEFAULT PASSWORD LOCATIONS] | ||
| Line 65: | Line 70: | ||
* 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. | * 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. | ||
| − | =Questions= | + | = Questions = |
| − | ==Frequently asked questions== | + | |
| + | == Frequently asked questions == | ||
* [[AM_FAQ|Solutions to common questions]] | * [[AM_FAQ|Solutions to common questions]] | ||
| − | ==Discussion | + | == Discussion group == |
* [http://groups.google.com/group/archivematica?hl=en For questions not on the FAQ] | * [http://groups.google.com/group/archivematica?hl=en For questions not on the FAQ] | ||
Revision as of 15:00, 21 August 2012
Main Page > Development > Administrator Manual
Installation
Upgrading
- Currently, Archivematica does not support upgrading from one version to the next. A re-install is required.
Users
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
http://localhost/administration/processing/
AtoM DIP upload
ContentDM DIP upload
Transfer source directories
Processing configuration
This is the defaul 'processingMCP.xml' that is included, in the root directory, when processing a SIP or Transfer. If a SIP or transfer is submitted with a 'processingMCP.xml' file 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:
<preconfiguredChoice>
<appliesTo>Workflow decision - send transfer to quarantine</appliesTo>
<goToChain>Skip quarantine</goToChain>
</preconfiguredChoice>
Where appliesTo is the name of the job presented in the dashboard, and goToChain is the desired selection. Note: these are case sensitive.
Users
Importing
- See the user manual
- Also note the ability to include a processingMCP.xml file See dashboard.
Customization
- Workflow processing decisions can be made in the processingMCP.xml file. See here.
- Workflows are currently created at the development level. See MCP for more details.
- Normalization commands can be viewed in the presveration planning tab.
- Normalization paths and commands are currently edited/created at the development level. See transcoder for more details.
Data backup
- How to protect your data from disaster.
Security
- We highly recomend chaning the default passwords.
[LIST OF DEFAULT PASSWORD LOCATIONS]
- 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.