DuraSpace Technologies The DuraSpace technology portfolio crosses the boundaries of institutional systems, the Web, and cloud infrastructure and inherently addresses representation and preservation of digital content. Our open source software and services help to ensure that current and future generations have access to our collective digital heritage and currently power more than 2,000 sites in 90 countries. DSpace ( is a turnkey institutional repository application, Fedora ( is a framework for building digital repositories, VIVO ( is a locally hosted system for showcasing the scholarship of an institution, and DuraCloud ( an open source platform and managed service that provides on-demand storage and services for digital content in the cloud. We are continually improving and expanding DuraSpace open technologies to provide you with durable, flexible software solutions that integrate seamlessly with your infrastructure.
InnovCity | Tout savoir sur l'innovation urbaine dans le monde, pour une ville durable et intelligente eSciDoc.PubMan, a publication repository software MPG.PuRe This is the publication repository of the Max Planck Society. It contains bibliographic data and numerous fulltexts of the publications of its researchers. The repository is based on eSciDoc.PubMan, a publication repository software developed by the Max Planck Digital Library. Currently we are working on the migration of the data base of the predecessor system eDoc into this repository. Read more Search for publications here ... or browse through different categories. Tools and Interfaces Search and Export Do you want to integrate your PubMan Data within an external system? Service for data transfer Do you want to fetch data from external sources like arXiv, BioMed Central, PubMed Central or Spires? Validation service Check your XML data for formal correctness with our validation service. Control of Named Entities (CoNE) Search and administrate controlled vocabularies for persons, journals, classifications or languages. SWORD-Interface
EPrints | open-source digital repository platform About EPrints Welcome to the home of EPrints, the world-leading open-source digital repository platform. Developed at the University of Southampton, EPrints has been providing stable, innovative repository services across the academic sector and beyond for over 15 years. About EPrints Services EPrints Services is our not-for-profit commercial services organisation, which has been building & hosting repositories, training users and developing bespoke functionality for over 10 years. The EPrints team is committed to working closely with clients to develop tailor-made repositories that fulfil their requirements, and we are proud to be supporting EPrints installations throughout the world.
CNRI Handles - Handle.Net Registry PURL help What is a PURL? A PURL is a persistent URL, it provides a permanent address to access a resource on the web. When a user retrieves a PURL they will be redirected to the current location of the resource. PURLs with a common prefix are grouped together into domains. PURL types Each PURL has a target and status code or type. A partial PURL is a special type which will match the beginning of a URL. The HTTP status code definitions provides more detail about the different status codes and thier meanings. Claiming a PURL domain The PURL service is now administered by the Internet Archive. Administering PURLs The PURL system is a service of the Internet Archive. Search for a PURL PURLs are grouped into domains, domains can be searched from the home page. The domain search shows a list of domains that match the search criteria. Viewing the contents of a PURL domain The domain details page displays the list of PURLs within the domain. There is a form that can be used to add new PURLs. Version
Persistent uniform resource locator - Wikipedia OCLC-designed persistent identifier scheme A persistent uniform resource locator (PURL) is a uniform resource locator (URL) (i.e., location-based uniform resource identifier or URI) that is used to redirect to the location of the requested web resource. PURLs redirect HTTP clients using HTTP status codes. Originally, PURLs were recognizable for being hosted at purl.org or other hostnames containing purl. Early on many of those other hosts used descendants of the original OCLC PURL system software. has a "root URL" as the resolver reference (e.g. means, to its user-community, to include new names in the root URL (e.g. means to associate each name with its URL (to be redirected), and to update this redirection-URL;ensure the persistence (e.g. by contract) of the root URL and the PURL resolver services. PURL version numbers may be considered confusing. Principles of operation [edit]
Handle System - Wikipedia As with handles used elsewhere in computing, Handle System handles are opaque, and encode no information about the underlying resource, being bound only to metadata regarding the resource. Consequently, the handles are not rendered invalid by changes to the metadata. The system was developed by Bob Kahn at the Corporation for National Research Initiatives (CNRI). The original work was funded by the Defense Advanced Research Projects Agency (DARPA) between 1992 and 1996, as part a wider framework for distributed digital object services,[2] and was thus contemporaneous with the early deployment of the World Wide Web, with similar goals. The Handle System was first implemented in autumn 1994, and was administered and operated by CNRI until December 2015, when a new "multi-primary administrator" (MPA) mode of operation was introduced. Thousands of handle services are currently running. Specifications[edit] Some Handle System namespaces define special presentation rules. Implementation[edit]
Apache Lucene - Welcome to Apache Lucene Institutional repository software comparison The Guidelines to compare Institutional Repository Software have been published as part of UNESCO’s Open Access Strategy. The publication compares the features of the major platforms and is intended to help libraries focus on which features will help facilitate the success of their repository. Institutional Repositories (IRs) were first developed as an online solution for collecting, preserving, and disseminating the scholarship of universities, colleges, and other research institutions. Since 2000, a number of repository platforms have been developed, each with their own set of benefits and technical criteria. All of these put libraries exploring IRs for the first time in an enviable position. The products have richer feature sets, and all the major platforms are available as a hosted service, which arguably has a lower total cost of ownership and is less time-consuming than running an IR locally.
Institutional Repositories | EBSCO Discovery Service Institutional Repositories (IRs) can be directly loaded into EBSCO Discovery Serviceso that they can be fully searched alongside all other EDS resources/content. Loading Institutional Repositories EBSCO supports harvesting institutional repositories via Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) or via File Transfer Protocol (FTP). EBSCO has developed a flexible framework for mapping your data to EDS. At this time we are able to load IR records in XML format that is OAI-PMH retrievable in the following metadata formats: Dublin Core (qualified and unqualified)EADJunii2METSMODS