The Value of Open Source Repository Systems

From SIS Wiki
Revision as of 14:18, 15 April 2017 by Fx9068 (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Shauna Quick

Topic: The value of open source repositories.

Thesis Statement: Many libraries are trying to get their content out to the people. Whether an academic, public or special library they all have resources that they need to share among their peers. Two of the contributing factors of open source repositories are their low cost and ease of use after installation. Many challenges that face these libraries include money, staff time, and expertise to implement the repository using both IT and Librarian set-up knowledge.


Annotated Bibliography

Afroz, H. (2014). Moving towards the next-generation library: BRAC university experience. World Digital Libraries- an International Journal, 7(1), 1-14.

http://search.proquest.com.proxy.lib.wayne.edu/docview/1562515069?pq-origsite=summon

This academic library went above and beyond to implement the use of open source software in the library environment to evoke the next-generation library. The article talks first about the repository then follows with an ILS, discovery tool, RFID, website, and mobile interface. They chose to use Dspace due to its flexibility, functionality, and requirement of not needing a lot of staff time to manage it. The key focus was to ensure the sustainability of the materials being held within the repository. This, in turn, helps to make the items searchable, able to be found, used, and preserved for others in the future to gain knowledge from.


Benjelloun, R. (2005). Archimède: A Canadian solution for institutional repository. Library Hi Tech, 23(4), 481-489. doi:10.1108/07378830510636283

http://www.emeraldinsight.com.proxy.lib.wayne.edu/doi/abs/10.1108/07378830510636283

The repository created by this institution needed to be cheap, effective, and have fast development. Instead of using an open source repository that was already created the institution used open source software to create its own that would benefit their Multilanguage, compatibility with many different technical infrastructures and index metadata and full-text simultaneously. This article brings value to the partnership that can be created between IT developers and information specialists. By working together they were able to create an internet repository for their institution that was operation on multiple operating systems and dealt really well with their duel/multi-language capabilities.


Chen, H., & Zhang, Y. (2014). Functionality analysis of an open source repository system: Current practices and implications. Journal of Academic Librarianship, 40(6), 558-564. doi:10.1016/j.acalib.2014.09.012

http://www.sciencedirect.com.proxy.lib.wayne.edu/science/article/pii/S0099133314001773

This article does a great job of digging into the functionality of Dspace and the subcomponents that the open source repository provides. This repository is used by institutions all over the world, has the largest user/developer community, and is completely customizable for any all uses. The different functions of the repository allow it to function in the way that the institution that uses it, needs it too. This article is valuable in expressing the types of functions that would be of use to the many types of organizations that wish to use this open source software. Academic, government, research center, nonprofit, personal, archive/public library, commercial are the most representative institution types using Dspace.


Groenewegen, D., & Treloar, A. (2008). The ARROW project: A consortial institutional repository solution, combining open source and proprietary software. OCLC Systems & Services, 24(1), 30. doi:10.1108/10650750810847224

http://search.proquest.com.proxy.lib.wayne.edu/docview/209776500?pq-origsite=summon

This article showcases the partnership between using an open source repository with the help of a proprietary vendor. They wanted an open source repository to allow for open access standards and ability to transfer the data in the future. To make the development of such a project to work they employed a proprietary to keep software up to date, be accessible as a helpdesk, and extend the ability of the software with new features or functions that may be installed once introduced to the repository world. Many articles focus on using only open source or proprietary access to creating and maintaining an internet repository. This brings value to the topic for its resourcefulness in getting help in the areas it needs and still being able to function in the manner that the institution sees fit.


Kelly, J. C. (2007). Creating an institutional repository at a challenged institution. OCLC Systems & Services, 23(2), 142. doi:10.1108/10650750710748441

http://search.proquest.com.proxy.lib.wayne.edu/docview/209770586?pq-origsite=summon

This article reflects upon an academic institution that felt challenged by its lack of financial and technological resources but felt that a proprietary was the best avenue for establishing their internet repository. Depending on how the institution needs to handle their items for the repository is a key decision in what avenue needs to be chosen. A proprietary can offer valuable support in regards to staff, expertise, and space to hold digitized items while open source can offer flexibility, custom-ability, and affordability. This article proves that no matter the choice you make in what software is used for an internet repository a commitment to open access and the encouragement of its use is what is important.


Namdev Dhamdhere, S., De Smet, E., & Lihitkar, R. (2014). ABCD open source software for managing ETD repositories. Library Management, 35(4/5), 387-397. doi:10.1108/LM-08-2013-0072

http://search.proquest.com.proxy.lib.wayne.edu/docview/1633971445?pq-origsite=summon

This academic institution was seeking a way to collect, maintain, and distribute the facilities electronic thesis and dissertation (ETD) publications. They found their answer using an open source software that had a “software suite” versatile enough to engage most of the components within their library. The interesting part is that it included an internet repository that benefited the group in regards to making their ETDs accessible online and it works seamlessly with their catalog to make researching that much easier in only needing to search from one place.


Pai, R. D., & Parmar, S. S. (2014). Manipal university digital repository: A study. DESIDOC Journal of Library & Information Technology, 34(4), 317-324. doi:10.14429/djlit.34.6119

http://search.proquest.com.proxy.lib.wayne.edu/docview/1561048926?pq-origsite=summon

This article studies the value of the institutions need to retain works produced by its staff and students. They considered the open source repository Eprints to develop their infrastructure. They built the internet repository to help get the digital initiative started on their campus as well as have a space dedicated to its researcher’s publications. They did find some things to work on such as getting staff to self-archive, creating a logo for easy identification of the project, and start a marketing campaign across campus. This article shows the need to get information out there to those seeking it and how open source repositories helped them get there.


Palmer, A., & Choi, N. (2014). The current state of library open source software research: A descriptive literature review and classification. Library Hi Tech, 32(1), 11-27. doi:10.1108/LHT-05-2013-0056

http://www.emeraldinsight.com.proxy.lib.wayne.edu/doi/full/10.1108/LHT-05-2013-0056

This article focuses on the research that has been compiled on the topic of open source software within the library world. Most of the studies/articles that are/have been published describe the functions and development of digital repositories. It proceeds to discuss the ideals of open source to those of the libraries interest in open access and wishes to push the publication of more articles on the topics involved to advance the study and implications it has on future library infrastructure. It helps shed light on the aspect that libraries have multiple ways to make information accessible with a little ingenuity.


Verno, A. (2013). IVDB … for free! implementing an open-source digital repository in a corporate library. Journal of Electronic Resources Librarianship, 25(2), 89-99. doi:10.1080/1941126X.2013.785286

http://www.tandfonline.com.proxy.lib.wayne.edu/doi/abs/10.1080/1941126X.2013.785286

This corporate library had the ability to let a librarian invest time into learning the backend of setting up an open source repository. The business needed to switch over to a digital information infrastructure and found that monetarily going with an open source system would be the best from them. The article walks the reader through the librarian setting up the chosen repository (Dspace) with the use of other open source softwares. They chose the Dspace system over others because of its “easy” installation, better search capabilities, and better/updated documentation of use within the repositories community. The value of this article is its detailed account of how this system was implemented and the overview of decisions made by the librarian.


Wang, F. (2011). Building an open source institutional repository at a small law school library: Is it realistic or unattainable? Information Technology and Libraries, 30(2), 81-84. doi:10.6017/ital.v30i2.3008

http://go.galegroup.com.proxy.lib.wayne.edu/ps/i.do?p=AONE&u=lom_waynesu&id=GALE%7CA258356982&v=2.1&it=r&sid=summon&authCount=1

This article weighs whether it can manage an open source repository at its small law school library or not with a lack of funding, staff, and expertise. When choosing an Internet repository, it was important that they find a program with low costs and little computer programming because of these reasons. It is useful to see the use of it in a special academic library and rationalize that even though they did not have the money/expertise they didn’t settle for finding money to purchase from a proprietary or giving up the project entirely.