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
- Academic repositories
Academic repositories
An academic repository can use a project to define a collection and a content item to carry each deposit through preparation, evidence review and decision. The operator records the item's source reference, owner and supporting file. A reviewer decides the exact submitted revision, with a reason available when the work must return.
How E-library / Digital Repository is set up for you
Thesis deposits
Link the source document and requirement lines to the item; keep the document date and external reference visible to the reviewer.
Collection definitions
Use project code, operating dates and policy reference to place each item under the right collection.
Independent review
Record the reviewer, decision, source revision and evidence reference before the item proceeds.
Changed deposits
Assign a production task when a file or source identifier changes, then submit a successor revision.
An academic repository can use a project to define a collection and a content item to carry each deposit through preparation, evidence review and decision. The operator records the item's source reference, owner and supporting file. A reviewer decides the exact submitted revision, with a reason available when the work must return.
Choose one active collection and a small set of representative items. Prepare one complete deposit, one with a missing supporting file and one that will be returned for correction. Set up the organization and project first, then assign people and create the content items. Agree how the institution identifies the source record and how a delivered reference is obtained from its repository endpoint.
Walk the operator and reviewer through the Content Items and Details workspace. The operator should see the selected item's requirement strip and status history. The reviewer should be able to identify the submitted revision and explain a return from the recorded reason. Rehearse a changed file after an approval so the successor receives a fresh decision and the original remains traceable.
[Review the intake process](/e-library-digital-repository/processes/content-intake-to-decision) and [implementation plan](/e-library-digital-repository/implementation).
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.