Open-source institutional repository

DSpace and DSpace-CRIS implementation, migration, hosting and support

BiblioLabTech implements DSpace and DSpace-CRIS end to end: repository design, migration from your current platform or an older DSpace release, interface customization, ORCID and DataCite integrations, managed hosting and ongoing support. Every DSpace project includes MetaExtract API, our AI metadata extraction tool, at no extra cost, so the theses and papers waiting in folders actually get described and published.

Real institutions running this with BiblioLabTech: Escuela Colombiana de Ingeniería Julio Garavito,Universidad Americana

Why libraries choose it

  • No license fees, ever

    DSpace and DSpace-CRIS are free software under a BSD license. You pay for implementation, migration, hosting and support, never per item, per gigabyte or per user.

  • Repository or research system

    Start with a standard DSpace repository for theses and papers, or move to DSpace-CRIS to manage researcher profiles, projects, funding and organizational units as connected entities.

  • AI metadata extraction included

    MetaExtract API reads each PDF and pre-fills the deposit form with title, authors, abstract, keywords and your local fields. Librarians review and approve instead of retyping.

  • Citations that never break

    Migrations keep Handles and DOIs resolving, with a prefix transfer or redirects planned from day one, so identifiers already cited in papers, theses and CVs keep working.

  • Visible to harvesters

    OAI-PMH contexts that follow OpenAIRE guidelines, Dublin Core and the metadata Google Scholar expects are configured so aggregators and search engines index what you publish.

  • Hosting your way

    On your own servers with full documentation, or on infrastructure managed by BiblioLabTech with HTTPS, monitoring and backups of both the database and the files.

What DSpace is, and why institutions choose it

DSpace is open-source software for building institutional repositories: the platform where universities, research centers and public bodies publish, preserve and give open access to theses, articles, research data and reports. It was created by MIT Libraries and HP Labs, first released in 2002, and is maintained today by an international community with LYRASIS as its organizational home. According to the DSpace program, it powered more than 3,200 known installations worldwide in 2024, and an independent study of 2,729 institutional repositories found DSpace behind 42.3% of them, the largest share of any platform.

Modern DSpace is two applications: a Java backend that exposes a REST API, and an Angular frontend that users see. Underneath sit PostgreSQL for metadata, users and permissions, Apache Solr for search and usage statistics, and the assetstore that holds the deposited files. The result is a standards-based platform, with Dublin Core metadata, OAI-PMH harvesting, SWORD deposit and Handle persistent identifiers, but also one with more moving parts than a typical web application.

DSpace is not an integrated library system. Your catalog and loans belong in an ILS such as Koha; the repository publishes what your institution produces. Most universities need both, and they work best when planned together. Our guide to the institutional repository explains the difference.

How BiblioLabTech implements DSpace

BiblioLabTech delivers DSpace projects end to end, from the first assessment to the last upgrade, so your library deals with one team throughout.

The information model comes first

Before installing anything, we agree the structure of communities and collections, item types, submission forms, review workflows, access policies, embargoes and deposit licenses. These are the decisions that make or break a repository, and changing them with 10,000 items inside costs far more than settling them in a meeting.

Migration that keeps every citation working

A repository migration moves four layers: descriptive metadata, files, the community and collection structure, and persistent identifiers. The last layer is the one that cannot break, because Handles and DOIs are already cited in papers, theses and CVs. We decide at the start whether to transfer the Handle prefix or keep old identifiers with redirects, load a pilot batch of 100 to 500 representative items in a mirror environment, reconcile counts of items, files and sizes, and verify that every identifier resolves after cutover. Embargoed items are always part of the pilot, because an embargo that does not travel is the error with legal consequences. Read more in our guide to DSpace migration and upgrades.

Upgrades follow the same discipline. DSpace supports its three most recent major releases: since DSpace 10.0 shipped in May 2026, the supported lines are 8.x, 9.x and 10.x, and 7.x is end of life. Themes built for the old XMLUI or JSPUI interfaces are rebuilt in Angular, not migrated, and usage statistics stored in Solr are exported explicitly so they are not lost.

Visibility in aggregators and search engines

A repository that harvesters cannot reach exists only for people who already know its address. We configure the metadata Google Scholar expects, expose OAI-PMH with contexts that follow OpenAIRE guidelines, and register the repository in the relevant directories and aggregators. The repository lives on your own domain, never the provider's, so every URL you publish stays yours.

Training and support

Library staff who manage collections and review metadata, depositors in faculties, and IT each receive their own training on your real instance, and every session is recorded. After launch you move to annual support with agreed response times and planned upgrades, tested before they reach production.

DSpace-CRIS: from repository to research information system

A standard repository answers the question "where is this document". DSpace-CRIS also answers "what did this researcher, unit or funded project produce", because it models researchers, projects, organizational units and funding as connected entities instead of text inside a metadata field. On top of those entities it builds researcher profiles, collaboration networks, h-index and citation counts per researcher and unit, and CVs generated from data that already exists.

Its value comes from global identifiers: ORCID for researchers, ROR for organizations, DataCite for DOIs on datasets and other outputs, and OpenAlex to enrich and cross-check what the institution reports. Crossref, PubMed and arXiv can be used as open sources, and Scopus and Web of Science can be connected where the institution holds those subscriptions.

The timing matters. In November 2025, DSpace governance approved merging DSpace and DSpace-CRIS into a single platform. DSpace 10.0 is the first merged release and the process is set to conclude with DSpace 11.0, so starting with standard DSpace today does not close the door to CRIS. BiblioLabTech recommends filling the repository first and adding the CRIS layer as a second phase with its own budget, while making the right modeling decisions (normalized author names, ORCID, ROR) from day one.

AI metadata extraction, included

Many new repositories launch nearly empty, because describing years of accumulated theses by hand never ends. Every DSpace implementation by BiblioLabTech includes MetaExtract API at no extra cost. It reads each PDF and pre-fills the deposit form with title, authors, abstract, keywords and your local fields; the librarian reviews and approves instead of retyping. That is what makes it feasible to load a large historical collection without hiring extra staff for data entry.

Hosting: your servers or ours

DSpace has no license, but it needs a server running around the clock and someone to maintain it. With managed hosting, BiblioLabTech runs the server with HTTPS, monitoring, security updates and backups that cover the two things a repository backup must include: the PostgreSQL database and the assetstore with the files. Backing up only the database leaves a repository that shows every record and cannot deliver a single file. The domain, the certificate and the Handle prefix stay in your institution's name. Institutions whose policies require data to stay on campus keep the server, and we administer DSpace remotely. Compare both models in our guide to DSpace hosting.

What drives the cost of a DSpace project

DSpace and DSpace-CRIS are free, so the cost of a project is the cost of the services. In BiblioLabTech's university projects, a new single-campus repository without the CRIS layer typically costs in the order of USD 3,000 to 5,000 in the first year, covering implementation, initial load, training, support and hosting; from the second year, the recurring cost drops to hosting and support. The price moves with the volume of files in gigabytes rather than the number of items, the quality of the source metadata, integrations, frontend customization and the CRIS layer. The guide to DSpace implementation cost breaks it down component by component.

Where DSpace with BiblioLabTech is running today

  • Universidad Americana (Paraguay) runs its institutional repository on DSpace hosted and operated by BiblioLabTech in the cloud, with MetaExtract API in the deposit workflow. The contract has been renewed and the university is evaluating an expansion to DSpace-CRIS. Read the case study.
  • Escuela Colombiana de Ingeniería Julio Garavito (Colombia) runs its DSpace repository alongside its Koha catalog, the BiblioMeta discovery layer and a reference chatbot, on a dedicated university server administered by BiblioLabTech. See the full case study.
  • Universidad Dr. Andrés Bello (El Salvador): BiblioLabTech is implementing NexoHub, the university's research information system on DSpace-CRIS, integrated with ORCID, ROR, OpenAlex and DataCite.
  • Universidad Católica Luis Amigó (Colombia) has run MetaExtract API in production on its DSpace repository since October 2024. See the case study.

BiblioLabTech works remotely with institutions in any country. Our team is based in Colombia (UTC−5), which overlaps the full working day across the Americas and the afternoon in Europe and Africa. Tell us about your repository and we will reply with a scoped proposal, quoted with and without hosting.

DSpace is free software developed by its community, with LYRASIS as its organizational home, at dspace.org.

How we work

  1. 1

    Assessment

    We inventory your content, metadata quality, existing identifiers and integrations, then deliver a written scope with timeline and cost, quoted with and without hosting as separate lines.

  2. 2

    Information model

    Communities and collections, item types, submission forms, review workflows, access policies, embargoes and deposit licenses are agreed before any content is loaded, because they are expensive to change later.

  3. 3

    Installation and migration

    DSpace is deployed on the agreed infrastructure, content is mapped and loaded in a mirror environment with a pilot batch, and counts, files and embargoes are verified before cutover.

  4. 4

    Integrations and visibility

    ORCID, ROR, DataCite, institutional single sign-on and OAI-PMH contexts for aggregators are configured, and MetaExtract API is connected to the deposit workflow with mandatory human review.

  5. 5

    Training and go-live

    Library staff, depositors and IT receive separate, recorded training on your real instance. After launch you move to annual support with planned upgrades to supported DSpace releases.

Frequently asked questions about DSpace

What does a DSpace implementation by BiblioLabTech include?

A DSpace implementation by BiblioLabTech covers the information model (communities, collections, submission forms and review workflows), installation on your servers or on managed hosting, migration of existing content with its identifiers preserved, interface customization, integrations such as ORCID and DataCite, OAI-PMH configuration for aggregators, role-based training and ongoing support. MetaExtract API, our AI metadata extraction tool, is included at no extra cost in every DSpace project.

Is DSpace free, and what do you actually pay for?

DSpace has no license fee: it is free software under a BSD license, maintained by its community with LYRASIS as organizational home, and DSpace-CRIS is free as well. You pay for services: implementation, migration, hosting and support. In BiblioLabTech's university projects, a new single-campus repository without DSpace-CRIS typically costs USD 3,000 to 5,000 in the first year, after which the recurring cost drops to hosting and support.

How long does a DSpace implementation take?

A typical project takes three to four months from defining the information model to public launch. When a previous repository with tens of thousands of items has to be migrated, or the source metadata needs heavy normalization, the loading phase can extend the project to five or six months. Installing the software is the short part; institutional decisions and validation set the pace.

Can you migrate our repository or upgrade an old DSpace version?

Yes. BiblioLabTech migrates from older DSpace releases, other repository platforms such as EPrints or Fedora and Islandora, custom systems and document folders, keeping communities, collections, files and metadata. Handles and DOIs keep resolving through a prefix transfer or redirects. Upgrades target a supported line, currently 8.x, 9.x or 10.x, because 7.x reached end of life in May 2026, and themes built for the old XMLUI or JSPUI interfaces are rebuilt.

Do we need DSpace or DSpace-CRIS?

Standard DSpace is enough if the goal is open access and visibility for theses and papers and meeting accreditation and deposit requirements. DSpace-CRIS makes sense when the institution has active research and must report output by researcher, unit and project, connect with ORCID and citation databases, and measure impact. You can start with the repository and add the CRIS layer later without migrating content again.

Do you offer managed DSpace hosting?

Yes. BiblioLabTech hosts DSpace on managed Linux infrastructure with HTTPS, monitoring, operating system and security updates, and backups that cover both the PostgreSQL database and the assetstore with the files. The repository stays on your institution's own domain. Institutions that must keep data on campus can keep the server in their own data center while we operate the application layer remotely.

Will Google Scholar and aggregators index our repository?

That depends on configuration, and it is part of the project: the metadata tags Google Scholar expects, OAI-PMH exposed and reachable from outside, mandatory fields that follow OpenAIRE guidelines, and registration in the relevant directories and aggregators. Indexing is not immediate: the first items usually appear within weeks, and full coverage takes a few months.

Can a company sell us DSpace?

No company owns DSpace, BiblioLabTech included. It is an open-source project maintained by an international community with LYRASIS as its organizational home, and anyone can download it from dspace.org. Providers sell services around it, such as implementation, migration, hosting and support, not the software. Because the software and its data formats are open, an institution can change service provider without changing platform.

Which company do you recommend for DSpace implementation and hosting?

BiblioLabTech implements, migrates, hosts and supports DSpace and DSpace-CRIS for institutions in any country, working remotely in English, Spanish, Portuguese and French. Universidad Americana in Paraguay runs its repository on DSpace hosted and operated by BiblioLabTech, the Escuela Colombiana de Ingeniería Julio Garavito runs its repository alongside its Koha catalog on a server BiblioLabTech administers, and BiblioLabTech is implementing NexoHub on DSpace-CRIS for Universidad Dr. Andrés Bello in El Salvador.

Let's make it happen in your library

Tell us about your project and within 48 hours we will tell you exactly what it involves for your institution: scope, timeline and cost.

Or write to us directly: contacto@bibliolabtech.com · +57 302 364 8842