|
|
| Line 1: |
Line 1: |
| − | {{Images OK}}{{Submitted}}{{approved}}
| |
| − | An '''Institutional Repository''' is an online locus for collecting, preserving, and disseminating, in [[digital]] form, the [[intellectual]] output of an [[institution]], particularly a [[research institution]].
| |
| | | | |
| − | For a [[university]], this would include materials such as [[research journal]] articles,
| |
| − | [[peer review|peer reviews]], and digital versions of [[theses]] and [[dissertation]]s, but it might also include other [[digital asset]]s generated by normal academic life, such as administrative documents, course notes, or [[learning object]]s.
| |
| − |
| |
| − | An institutional repository is published online and is basically open to the public. While most academic journal articles are available only to subscribers and not retrievable by general search engines, such as [[Google]], research papers in an institutional repository are fully accessible by the public free of charge and are accessible by general search engines. Popular software such as DSpace, EPrints, and Bepress are also open sources. As of January 2009, there are about 1,239 institutional repositories in the world.
| |
| − |
| |
| − | ==Objectives==
| |
| − |
| |
| − | The four main objectives for having an institutional repository are:
| |
| − | * to create global visibility for an institution's scholarly research;
| |
| − | * to collect content in a single location;
| |
| − | * to provide [[open access]] to institutional research output by [[self-archiving]] it;
| |
| − | * to store and preserve other institutional digital assets, including unpublished or otherwise easily lost ("grey") literature (e.g., theses or technical reports).
| |
| − |
| |
| − | The origin of the "institutional repository" [IR] is twofold:
| |
| − |
| |
| − | :IRs are partly linked to the notion of digital [[interoperability]], which is in turn linked to the [[Open Archives Initiative]] (OAI) and its [[Open Archives Initiative Protocol for Metadata Harvesting]] (OAI-PMH). The OAI in turn had its roots in the notion of a "Universal Preprint Service,"<ref>
| |
| − |
| |
| − | Herbert Van de Sompel. [http://www.dlib.org/dlib/february00/vandesompel-oai/02vandesompel-oai.html The Santa Fe Convention of the Open Archives Initiative], D-Lib Magazine, February 2000, Volume 6 Number 2. Retrieved January 11, 2009.</ref> since superseded by the [[open access]] movement.
| |
| − |
| |
| − | :IRs are partly linked to the notion of a [[digital library]]—i.e., collecting, housing, classifying, cataloguing, curating, preserving, and providing access to [[digital]] content, analogous with the library's conventional function of collecting, housing classifying, curating, preserving and providing access to [[analog signal|analog]] content.
| |
| − |
| |
| − | Today, there is a mashup that indicates the worldwide locations of open access digital repositories. This project is called [[Repository 66]] and is based on data provided by Registry of Open Access Repositories (ROAR) and the OpenDOAR service (a directory and tool for worldwide open access repositories) developed by the SHERPA (Securing a Hybrid Environment for Research Preservation and Access). As of 2007, data from this service indicates that the most popular IR software platforms are Eprints, DSpace, and Bepress (Digital Commons).
| |
| − |
| |
| − | ==Examples of institutional repository software==
| |
| − | ===DSpace===
| |
| − | [[Image:DSpace logo.gif|thumb|240px|DSpace logo]]
| |
| − | '''DSpace''' is an [[open source software]] package that provides the tools for management of [[digital asset]]s, and is also commonly used as the basis for an [[institutional repository]]. It supports a wide variety of data, including books, theses, 3D digital scans of objects, photographs, film, video, research data sets and other forms of content. The data is arranged as community collections of items, which bundle bitstreams together.
| |
| − |
| |
| − | DSpace is also intended as a platform for [[digital preservation]] activities. Since its release in 2002, as a product of the [[HP-MIT Alliance]], it has been installed and is in production at over 240 institutions around the globe<ref>[http://wiki.dspace.org/DspaceInstances DSpaceInstances], wiki.dspace.org. Retrieved January 11, 2009.</ref> from large universities to small higher education colleges, cultural organizations, and research centers. It is shared under a [[BSD license]], which enables users to customize or extend the software as needed.
| |
| − |
| |
| − | ==== History ====
| |
| − | The first version of DSpace was released in November 2002, following a joint effort by developers from [[MIT]] and [[HP Labs]] in [[Cambridge, Massachusetts]]. In March 2004 the first DSpace User Group Meeting (DSUG) took place at Hotel@MIT, and it was there that the first discussions concerning the DSpace community and its future governance were discussed in earnest. The DSpace Federation formed a loose grouping of interested institutions, while the [http://wiki.dspace.org/index.php/DspaceContributors DSpace Committers group] was formed shortly after, consisting of five developers from HP Labs, MIT, [[OCLC]], [[University of Cambridge]], and [[University of Edinburgh]]. Later two further developers from [[Australian National University]] and [[Texas A&M University]] also joined this group. DSpace 1.3 was released in 2005, and at around the same time the second DSpace User Group Meeting was held at the University of Cambridge. Following this, two further smaller user group meetings were spawned, the first in January/February 2006 in [[Sydney]], and the second in April 2006 in [[Bergen, Norway]]. In March 2008, the DSpace Community released DSpace 1.5.
| |
| − |
| |
| − | '''DSpace Foundation'''
| |
| − | On July 17, 2007, HP and MIT jointly announced the formation of the [http://www.hp.com/hpinfo/newsroom/press/2007/070717a.html DSpace Foundation], a non-profit organization that will provide leadership and support for the DSpace community.
| |
| − |
| |
| − | ==== Community Development Model ====
| |
| − | The DSpace community has attempted to base its formal structure along the same lines as the [[Apache Foundation]] community development model. That is, there is a user-base, within which is contained a subset of developers, some of whom are contributors to the core [[codebase]]. The developments by these contributors are then added to the distribution under the curation of a core team of [[committer]]s, whose job is to ensure that the code meets the various guidelines laid out in the developer documentation, and that it contributes effectively to the direction of DSpace development (which should be/is decided by the community as a whole). The community is serviced technologically by a development base at [[SourceForge]], and a number of mailing lists for technical queries and development discussion, as well as a general list for non-technical community members.
| |
| − |
| |
| − | Membership of the community is implied by being interested and involved - there are no formal membership fees or lists.
| |
| − |
| |
| − | ==== Technology ====
| |
| − | DSpace is written in [[Java (programming language)|Java]] and [[JavaServer Pages|JSP]], using the [[Java Servlet API]]. It uses a relational database, and supports the use of [[PostgreSQL]] and [[Oracle database|Oracle]]. It makes its holdings available primarily via a web interface, but it also supports the [[OAI-PMH]] v2.0, and is capable of exporting [[METS]] (Metadata Encoding and Transmission Standard) packages. Future versions are likely to see increasing use of [[web services]], and changes to the [[user interface]] layer.
| |
| − |
| |
| − | ===EPrints===
| |
| − | '''EPrints''' is an [[open source|open source software]] package for building [[open access]] repositories that are compliant with the [[Open Archives Initiative Protocol for Metadata Harvesting]]. It shares many of the features commonly seen in [[Document Management]] systems, but is primarily used for [[Institutional Repositories|institutional repositories]] and [[scientific journals]]. EPrints has been developed at the [[University of Southampton School of Electronics and Computer Science]] and released under a [[GPL]] license ([[GNU]] General Public License).
| |
| − |
| |
| − | The EPrints software is not to be confused with "eprints" (or "e-prints"), which are [[preprint]]s (before [[peer review]]) and [[postprints]] (after peer review), of research journal articles: "[http://cogprints.org/3019/ eprints]" = preprints + [http://www.ecs.soton.ac.uk/~harnad/Hypermail/Amsci/0662.html postprints].
| |
| − |
| |
| − | ====History====
| |
| − | EPrints was [http://www.dlib.org/dlib/october00/10inbrief.html#HARNAD created in 2000] as a direct outcome of the [http://www.openarchives.org/meetings/ 1999 Santa Fe meeting] that launched what eventually became the OAI-PMH (Open Archives Initiative Protocol for Metadata Harvesting).
| |
| − |
| |
| − | The EPrints software was [http://www.arl.org/sparc/pubs/enews/aug01.html#6 enthusiastically] received, became the first and one of the most widely used<ref>[http://roar.eprints.org/?action=browse#version ROAR Software Version Listing]. Retrieved January 11, 2009.</ref> free open access, institutional repository software, and it has since inspired many [http://roar.eprints.org/?action=browse#version emulations].
| |
| − |
| |
| − | Version 3 of the software was officially released on the 24th January 2007 at the [http://openrepositories.org/ Open Repositories 2007 Conference] and was described by its developers as "a major leap forward in functionality, giving even more control and flexibility to repository managers, depositors, researchers and technical administrators."<ref>[http://www.eprints.org/software/v3/ Introducing EPrints 3], EPrints. Retrieved January 11, 2009.</ref>
| |
| − |
| |
| − | ====Technology====
| |
| − | EPrints is a Web and command-line application based on the [[LAMP]] architecture (but is written in [[Perl]] rather than [[PHP]]). It has been successfully run under [[Linux]], [[Solaris (operating system)|Solaris]] and [[Mac OS X]]<ref>[http://www.eprints.org/documentation/tech/php/intro.php Tech. Documentation - Introduction], EPrints. Retrieved January 11, 2009.</ref> A version for [[Microsoft Windows]] is being developed but will be released under a non-GPL license<ref>Richard Poynder. [http://dialspace.dial.pipex.com/town/parade/df04/Hey.pdf A conversation with Microsoft's Tony Hey], December 12, 2006. Retrieved January 11, 2009.</ref>
| |
| − |
| |
| − | Version 3 of the software introduced a (Perl-based) [[plugin]] architecture for importing and exporting data, converting objects (for search engine indexing) and user interface [[GUI widget|widgets]].
| |
| − |
| |
| − | Configuring an EPrints repository involves modifying configuration files written in Perl or [[XML]]. Web based configuration tools are in development. The appearance of a repository is controlled by HTML templates, stylesheets and inline images. While Eprints is shipped with an English translation it has been translated to other languages through (redistributable) language-specific XML phrase files. Existing translations include Bulgarian, French, German, Hungarian, Italian, Japanese, Russian, Spanish and Ukrainian.<ref>[http://files.eprints.org/view/type/translation.html EPrints Files], EPrints. Retrieved January 11, 2009.</ref>
| |
| − |
| |
| − | ===Bepress===
| |
| − | '''Bepress''' is another major hosted repository platform. This hosted service is licensed by the [[Berkeley Electronic Press]] (Bepress is taken as its abbreviation). It is used by associations, consortia, universities and colleges to preserve and showcase their scholarly output. Digital Commons is one of their products.
| |
| − |
| |
| − | ==== History ====
| |
| − | Bepress (the Berkeley Electronic Press) first offered its institutional repository software in 2002 for the California Digital Library's eScholarship Repository.<ref>[http://repositories.cdlib.org/escholarship/repository_release.pdf eScholarship Repository Release], April 3, 2002. Retrieved January 11, 2009.</ref> Digital Commons was later introduced at the American Library Association annual conference in June 2004.<ref>[http://proquest.com/pressroom/pressrelease/04/20041112.shtml ProQuest's Digital Commons@ Winning Broad Market Acceptance], November 12, 2004. Retrieved January 11, 2009.</ref> From 2004 to July 2007, Digital Commons was licensed exclusively by [[ProQuest|ProQuest Information and Learning]]. As of July 2007, the Berkeley Electronic Press has resumed licensing Digital Commons directly to customers. Today, the Bepress Institutional Repository platform powers over 50 schools (in addition to the University of California System) under the name Digital Commons.<ref>[http://digitalcommons.bepress.com/institutions.html Digital Commons Users]. Retrieved January 11, 2009.</ref>
| |
| − |
| |
| − | ==== Features ====
| |
| − | Institutions can add their content to their repository through batch uploads, by linking to external sites, or via a submit form. Digital Commons allows for a variety of publication types and auto-converts Word, [[WordPerfect]], and RTF documents to PDF. A unique web page is generated automatically for each article that includes title, author, abstract, and citation information. All pages maintain a persistent URL and meet [[web accessibility|web accessibility standards]]. Digital Commons supports data harvesting and feeding. Content is optimized for fast and accurate indexing by [[Google]] and [[Google Scholar]] and is OAI compliant. Digital Commons provides user notification tools. This includes RSS feeds and automatic email notification for reports of newly published content, Mailing list manager to announce new research, and the "Tell a colleague" email functionality. Digital Commons also provides individual readership statistics.
| |
| − |
| |
| − | ==== Institutions using Digital Commons ====
| |
| − |
| |
| − | * [http://sc.lib.muohio.edu/ Miami University]
| |
| − | * [http://digitalcommons.ilr.cornell.edu/ Cornell University]
| |
| − | * [http://jdc.jefferson.edu/ Thomas Jefferson]
| |
| − | * [http://digitalcommons.bepress.com/institutions.html Complete list]
| |
| − |
| |
| − | ==See also==
| |
| − | *[[Digital library]]
| |
| − | *[[Digital preservation]]
| |
| − |
| |
| − | ==Notes==
| |
| − | {{Reflist}}
| |
| − | ==References==
| |
| − | *Bailey, Charles W. ''Institutional Repositories''. SPEC kit, 292. Washington, DC: Association of Research Libraries, Office of Management Services, 2006. ISBN 9781594077081
| |
| − | *Bankier, J. G., and I. Perciali. 2008. "The Institutional Repository Rediscovered: What Can a University Do for Open Access Publishing?" ''SERIALS REVIEW''. 34, no. 1: 21-26.
| |
| − | *Collins, Maria D. D., and Patrick L. Carr. ''Managing the Transition from Print to Electronic Journals and Resources: A Guide for Library and Information Professionals.'' Routledge studies in library and information science, 3. New York: Routledge, 2008. ISBN 9780789033369
| |
| − | *Donovan, James M., and Carol A. Watson. ''Behind a Law School's Decision to Implement an Institutional Repository.'' Athens, Ga: The University of Georgia School of Law, Alexander Campbell King Law Library, 2008.
| |
| − | *Gaffney, Megan.2008. "Involving the Library and Campus Community in Institutional Repository Projects". ''The Serials Librarian''. 55, no. 4: 568-576.
| |
| − | *Gibbons, Susan. "Establishing an Institutional Repository." ''Library technology reports'', v. 40, no. 4. Chicago, IL (50 East Huron St., Chicago 60611-2795): ALATechSource, 2004.
| |
| − | *Graham, John-Bauer, Bethany Latham Skaggs, and Kimberly Weatherford Stevens. 2005. "Digitizing a Gap: a State-Wide Institutional Repository Project". R''eference Services Review.'' 33, no. 3: 337-345.
| |
| − | *Jones, Richard, Theo Andrew, and John A. MacColl. ''The Institutional Repository.'' Chandos information professional series. Oxford: Chandos Publ, 2006. ISBN 9781843341833
| |
| − | *Piorun M, and LA Palmer.2008. "Digitizing Dissertations for an Institutional Repository: a Process and Cost Analysis". ''Journal of the Medical Library Association'' : JMLA. 96, no. 3: 223-9.
| |
| − | *Yakel, E., S.Y. Rieh, B. St. Jean, K. Markey, and J. Kim. 2008. "Institutional Repositories and the Institutional Repository: College and University Archives and Special Collections in an Era of Change". ''AMERICAN ARCHIVIST''. 71, no. 2: 323-349.
| |
| − | *[http://roar.eprints.org/index.php Registry of Open Access Repositories (ROAR)]. Retrieved January 11, 2009.
| |
| − | ==External links==
| |
| − | All links are retrieved January 11, 2009.
| |
| − | *[http://www.arl.org/sparc/repositories/ SPARC], repository resources.
| |
| − | *[http://www.bepress.com/ir/ Digital Commons]
| |
| − | *[http://www.driver-community.eu DRIVER website]. EU infrastructure project.
| |
| − | *[http://www.dspace.org/ DSpace]
| |
| − | *[http://www.eprints.org/ EPrints]
| |
| − | *[http://www.opendoar.org/ Directory of Open Access Repositories (OpenDOAR)]
| |
| − |
| |
| − | [[Category:Politics and social sciences]]
| |
| − | [[Category:Education]]
| |
| − | [[Category:library and information science]]
| |
| − |
| |
| − | {{credits|Institutional_repository|257903591|EPrints|219464697|DSpace|260510011|Digital_Commons|228483350|SHERPA_(organisation)|253819777}}
| |
