Difference between revisions of "Dashboard"
Jump to navigation
Jump to search
| Line 20: | Line 20: | ||
</div> | </div> | ||
| + | =Requirements= | ||
| − | = | + | ==Release 0.7-alpha== |
1) Provide updates on the Archivematica processes by reading rows from the MCP 'Task' table in its MySQL dbase. | 1) Provide updates on the Archivematica processes by reading rows from the MCP 'Task' table in its MySQL dbase. | ||
*This will likely have to happen through some kind of polling by the Django app of the MySQL database. | *This will likely have to happen through some kind of polling by the Django app of the MySQL database. | ||
| Line 31: | Line 32: | ||
* i.e. at certain stages in the Archivematica workflow we will stop and await the explicit approval from an archivist to trigger the next series of Archivematica tasks. So somewhere in the Django Dashboard there will be a list of jobs awaiting approval (retrieved from the Archivematica API) and then the ability for an archivist to click a button thereby approving a job and notifiying Archivematica MCP of that action (again, via the Archivematica API). | * i.e. at certain stages in the Archivematica workflow we will stop and await the explicit approval from an archivist to trigger the next series of Archivematica tasks. So somewhere in the Django Dashboard there will be a list of jobs awaiting approval (retrieved from the Archivematica API) and then the ability for an archivist to click a button thereby approving a job and notifiying Archivematica MCP of that action (again, via the Archivematica API). | ||
| + | |||
| + | ==Post release 0.7-alpha== | ||
| + | |||
| + | |||
=User interface= | =User interface= | ||
Revision as of 15:41, 15 November 2010
Main Page > Development > Development documentation > Dashboard
Design
This page proposes a new feature and reviews design options
Development
This page describes a feature that's in development
Documentation
This page documents an implemented feature
Requirements
Release 0.7-alpha
1) Provide updates on the Archivematica processes by reading rows from the MCP 'Task' table in its MySQL dbase.
- This will likely have to happen through some kind of polling by the Django app of the MySQL database.
- One other implementation option we've discussed is having Archivematica publish a RSS/Atom feed that the Django app reads.
2) Interact with the the Archivematica API:
- getListOfJobsAwaitingApproval
- approveJob
- i.e. at certain stages in the Archivematica workflow we will stop and await the explicit approval from an archivist to trigger the next series of Archivematica tasks. So somewhere in the Django Dashboard there will be a list of jobs awaiting approval (retrieved from the Archivematica API) and then the ability for an archivist to click a button thereby approving a job and notifiying Archivematica MCP of that action (again, via the Archivematica API).
Post release 0.7-alpha
User interface
Early mockup (March 2010)
