Difference between revisions of "SUNScholar/Audit"
|Line 11:||Line 11:|
The audit is usually
The audit is usually between the [[SUNScholar/Capacity_Building|repository management team]] and the [[Stellenbosch_University/Research_Office|institutions research office]] which is used by library top management to assess the quality of the repository and whether the repository is meeting the institution's business or academic objectives.
Revision as of 01:23, 20 July 2015
The following documentation was downloaded from the above site on 2015/05/11:
Also see: http://www.datasealofapproval.org
The audit is usually an activity undertaken between the repository management team and the institutions research office which is used by library top management to assess the quality of the repository and whether the repository is meeting the institution's business or academic objectives.
An audit tries to answer several of the following questions from users.
- How can I trust that the information in this repository is accurate and authoritative?
- How can I trust that the embargoes I request, will be properly enforced?
- How can I trust that the information I digitally store, will be available now and in the future, on the internet?
- How can I trust that my bibliography of electronic citations using the repository, will work today and in the future, on the internet?
We are very aware of the accounting audit function. In the course of an enterprise conducting business, records of account are kept by clerics and bookkeepers which are then managed by accountants. Auditors inspect the work of the accountants to determine if the accounts satisfy generally accepted accounting principles (GAAP). If they do, then they sign the financial statements.
A similar process could be involved in the audit of open access publishing systems. A possible definition of the process could be as follows:
"In the course of a University conducting research, publications are produced by researchers which are then deposited into a research repository by research librarians. The research collections in the repository are managed by research repository managers. Auditors inspect the work of the research repository managers to determine if the repository satisfies generally accepted repository practice (GARP). If it does, then they certify the repository for an agreed period of time."
GARP or Generally Accepted Repository Practice
Below are listed some sections that could form part of the audit and a draft GARP document, that would allow the audit to proceed in a generally accepted manner,
- Section 1: Policy
- Section 2: Preservation
- Section 3: Sustainability
- Section 4: Visibility
- Section 5: Security
- Section 6: Ingest
- Section 7: Customisation
- Section 8: Digitisation
- Section 9: Promotion
- Section 10: Legal
- Section 11: Community
- Section 12: Compliance
Below are links to what an audit report may look like. These are very brief and are NOT authoritative at ALL.
If audits are conducted, using GARP as described above, as the accepted benchmark amongst library professionals, then the report would be a valuable tool for library top management, to assess the quality of the repository and to suggest where corrective strategic and tactical measures should be taken, to meet the academic or business objectives of the institution.
Click on the heading above.