Im Langacker 16
+41 (0)56 470 03 37
Im Langacker 16
+41 (0)56 470 03 37
Diese Seite wurde noch nicht vollständig übersetzt. Bitte helfen Sie bei der Übersetzung.
(diesen Absatz entfernen, wenn die Übersetzung abgeschlossen wurde)
Executing Ingest processes of digital deliveries automatically, rather than manually, is standard operation. As soon as a new SIP is delivered to the intended folder, an appropriate Ingest workflow will be launched. This workflow will process the SIP in several steps. The process is logged and can be monitored online.
The interaction with docuteam feeder takes place via web front-end.
Accessing docuteam feeder in your browser will display a login window.
If you activate the checkbox “remember me”, the entered data will be suggested, the next time you log in.
After a successful login, you will land on the page “executions”. If you’ve logged in as administrator you’ll find a menu bar to the top right with five sections: executions, workflows, steps, users, cockpit:
If you’ve logged in as a user, following sections are available:
showin the row of the corresponding workflow.. * SIP shows the SIP currently being processed. * The column Status displays each processing step of a workflow as a dot. The colour of the dot indicates the status of the corresponding step: * brown: this step is still outstanding. * yellow: this step is being processed. * green: this step was completed successfully. * red: this step was aborted due to an error. * black: this step was skipped. * Starting time shows the time, the execution process was launched.. * Duration shoes the elapsed time since the launch of the process. Please note that the information given, refers to the time the page was first visited. If you wish to know the current status, you have to reload the page. To call up details of an execution, click on the link “show” at the right end of the corresponding row. The amount of information shown at each workflow-step depends on the log-level. If a step was completed successfully, a green „completed with code 0“ is displayed and the next step will commence. Should a step fail, an error-code will be signalled in red. In the example below a file migration could not be executed correctly. The same rule applies in this case: to view the current status, the page needs to be reloaded. ===== Menu option „workflows“ ===== The menu option „Workflows“ shows all defined ingest-workflows, that can be applied to a SIP. By clicking „show“ the individual steps of the particular workflow will be shown. The link „edit“ und „Bearbeiten“ leads to a page in which workflows can be edited. A workflow always has a linear progression: Basically, a SIP is sent into a pipeline, in which each step is processed successively. In case of an error, the process is stopped and the pending steps are omitted. In the trial operation, ingest-workflows of individual SIPs can be executed manually. The button
startwas designed for this purpose. After you’ve clicked on the button a dialogue box appears in which you can type in the name of your SIP. Important: the name should be entered without the file-ending .zip. ===== Menu option „steps“ ===== The menu option „steps“ shows all workflow-steps, which are available in docuteam feeder and can be compiled into an ingest-workflow. New steps can also be added, for example, to integrate additional migration tools or to expand the ingest-process with additional functionalities. ===== Menu option „users“ ===== To add a new user, a user-name, email adress and pasword need to be created. Additionally, the role of the user needs to be defined: * An executor can execute and monitor ingest-workflows, yet cannot create or change them. * An administrator can execute as well as create or change ingest-workflows. In addition, an administrator can manage users.. ===== Menu option „cockpit“ ===== The cockpit informs you about memory conditions, the amount of various file formats, or the number of ingests and objects. The cockpit gathers information from the fedora commons repository mostly docuteamOAIS). Detailed reports on file formats or memory conditions can be issued.