These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- E-library / Digital Repository
- Who it's for
- Public sector repositories
Public sector repositories
An agency can use organization and project records to separate its collections while keeping item review consistent. Content items retain assigned people, source references and revisions. A reviewer records the decision on the precise revision seen, and the team can trace later corrections through tasks and status history.
How E-library / Digital Repository is set up for you
Agency ownership
An organization owns projects and content items, giving staff a clear operating scope.
Document checks
Supporting files carry a date, external reference and named verifier.
Decision record
The decision includes the reviewer, source revision, reason and evidence reference.
Post-delivery work
A compensating task records what must happen when an executed delivery is superseded.
An agency can use organization and project records to separate its collections while keeping item review consistent. Content items retain assigned people, source references and revisions. A reviewer records the decision on the precise revision seen, and the team can trace later corrections through tasks and status history.
Select one organization, one collection project and a modest set of content items. Include a draft awaiting evidence, an item ready for review and a delivered item that may need correction. Agree who maintains the project policy reference and who can act as an independent reviewer. Define a source identifier format that can be matched to the sending system.
Rehearse an operator submitting an item and a reviewer returning it with a reason. Assign the correction to a named person, update the evidence and review the successor revision. Then test a delivered case: the previous receipt should remain visible while the new task explains the required follow-up. Use authorized role accounts to confirm that an analyst can inspect summaries without changing operational records.
[Walk through correction](/e-library-digital-repository/processes/correction-and-supersession) and [review the roles](/e-library-digital-repository/roles).
Features to start with
Roles on the team
- Digital Repository Administrator
- Maintains approved configuration: record entry on Projects, read-only on all operational, review and provenance tables, and access to all four repository pages. No schema editing, deletion, bulk operations or export grants.
- Digital Repository Operator
- Prepares assigned work: record entry on Content Items, Application Requirements, Production Tasks and Content Files, read-only on configuration, review and provenance tables. Scope to authorized organizations is enforced by workflow guards.
- Digital Repository Reviewer
- Reviews independent assigned work: record entry on Review Decisions only, read-only on every other table. Reviewers cannot approve their own preparation; the workflow guards enforce reviewer independence.
- Repository Read Only Analyst
- Reads authorized summaries and aggregates across every table plus the four repository pages. No record creation or editing, no schema or administrative capability.
Set up E-library / Digital Repository your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.