Difference between revisions of "Reporting"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
*Archivematica needs to be able to produce reports in the following ways: | *Archivematica needs to be able to produce reports in the following ways: | ||
| − | + | **During processing, to assist the archivist to have a better understanding of what's in the SIP and to make appraisal decisions. These reports would appear at pre-determined points during processing and may or may not be retained as part of the AIP. | |
| − | + | **After SIPs have been fully processed, to support ongoing preservation planning and administrative activities. These reports would be run through queries input by the user. | |
*The primary user interface for generating, viewing and saving reports would be the dashboard. | *The primary user interface for generating, viewing and saving reports would be the dashboard. | ||
[[Category:Development documentation]] | [[Category:Development documentation]] | ||
Revision as of 09:58, 1 March 2011
Main Page > Development > Development documentation > Reporting
- Archivematica needs to be able to produce reports in the following ways:
- During processing, to assist the archivist to have a better understanding of what's in the SIP and to make appraisal decisions. These reports would appear at pre-determined points during processing and may or may not be retained as part of the AIP.
- After SIPs have been fully processed, to support ongoing preservation planning and administrative activities. These reports would be run through queries input by the user.
- The primary user interface for generating, viewing and saving reports would be the dashboard.