Academic records should not disappear inside folders, drives, or physical archives.
WHY INREP SCHOLAR
The research repository built for African higher institutions.
Inrep Scholar gives institutions one governed place to receive submissions, run review workflows, protect files, enforce access policy, and publish research to a searchable public repository.
OAI-PMH
Dublin Core
DataCite
ORCID
Sample record
Evaluating AI Adoption in Institutional Libraries: Access, Ethics and Repository Governance
Published
Library Science
9
Access policies enforced
WHY IT EXISTS
Most higher institutions already have research. The problem is access, structure, and control.
Theses, dissertations, projects, and journal papers are scattered across offices, drives, and laptops. Inrep Scholar gives institutions one place to preserve records, run structured review, publish metadata, protect files, and report on repository health.
Institutions decide what is open, view-only, restricted, embargoed, or internal — per record, enforced on every request.
Good metadata makes research easier to find, cite, and reuse — harvested over OAI-PMH and exported in Dublin Core and DataCite formats.
Every upload, review, access request, and publication action is traceable and reportable.
Real repository answers, grounded in your own records
Try the repository assistantThe repository assistant answers questions about published records directly, instead of returning a list of links to search through.
Answers are generated only from records actually retrieved from the repository, with citations back to the source — never invented from general knowledge.
The assistant stays inactive until an institution configures a model provider, and prompts or completions are never logged — only outcome and timing.
VERIFIED PLATFORM FACTS
See how controls work
What the platform actually enforces
Live counts derived from the same application rules used by repository workflows—not campaign estimates.
- Research output types
- 31
- Tracked workflow states
- 13
- Access policies enforced
- 9
- Interoperability standards
- 4
WHO IT'S BUILT FOR
One platform, built around institutional roles
Every team involved in getting research from submission to public discovery — not a generic document tool retrofitted for higher institutions.
Institutional Libraries
Bulk upload, metadata standards, access governance, OAI-PMH harvesting, and repository reporting.
Research Offices
Track institutional research outputs, submission activity, compliance readiness, and publication metrics.
Graduate Schools
Preserve theses and dissertations with structured approval, embargo controls, and supervisor sign-off.
ICT / Digital Services
Choose the deployment model, manage integrations, and keep infrastructure decisions with the institution.
Supervisors & librarians
Review and approve submissions directly in the platform, with corrections routed back automatically.
Students & researchers
Submit work into a structured institutional process with guided forms, validation, and status tracking.
WHAT BUILDING THIS REQUIRED
Repository infrastructure, not a generic form builder
A submission form is easy. A governed repository is not. What Inrep Scholar had to get right:
A real workflow engine
Draft, supervisor review, correction loops, library review, and publication are enforced server-side as actual state transitions — not a status label a form can skip.
An access-policy layer
9 access policies enforced on every request, not checked once at upload — institution boundaries and embargo dates are validated server-side, every time.
Multi-tenant by design
Every institution's data is scoped and isolated at the query level, whether the institution is hosted centrally or runs its own self-hosted InRep Campus node.
Standards, not a proprietary format
OAI-PMH harvesting, Dublin Core and DataCite metadata output, and Google Scholar-compatible citation tags — records stay reachable by the tools researchers already use.
WHERE WE STAND ON DATA OWNERSHIP
Your research, under your institution's control
Ownership isn't a slogan here — it's a deployment choice with real consequences we design for, not around.
Self-hosting is a real option
InRep Campus runs on infrastructure your institution provisions and controls — files never have to leave a server you operate, if that's what your policy requires.
Access decisions are enforced, not advisory
Restricted, embargoed, and institution-only records are protected by server-side checks on every request — access control is not a setting that can be bypassed by guessing a URL.
Honest disclosure over marketing claims
The Trust Center states plainly what is implemented today and what depends on your institution's own agreement — we would rather under-claim than have a procurement team catch us overstating.
Data subject rights, not just a policy page
Access, correction, export, and deletion requests are submitted and tracked through a real form and workflow at the Trust Center — not a mailto link that goes nowhere.
HOW WE APPROACH IMPLEMENTATION
Guided setup, backed through every stage
An institution isn't handed a login and left to figure out academic structure, metadata rules, and access policy alone.
2–4 weeks
Typical starter-tier planning range — not a fixed commitment; see the full sequence for what changes it.
Institution structure → roles → submission configuration → launch.
Support runs through each stage, not a single onboarding call.
Talk to the team
Aligned with repository, metadata, and privacy standards
OAI-PMH
Dublin Core
DataCite
ORCID
Controlled Access
Ready to launch a proper institutional repository?
Get your institution set up with guided onboarding, metadata configuration, and access control built in from day one.
Request institutional proposal