Skip to content

OPUS4/application

Folders and files

NameName
Last commit message
Last commit date

Latest commit

30f2b68 · Apr 22, 2025
Jan 14, 2025
Dec 9, 2020
Apr 16, 2025
Jan 12, 2023
Apr 20, 2023
Apr 22, 2025
Apr 22, 2025
Mar 31, 2025
Oct 14, 2024
Apr 22, 2025
Dec 31, 2020
Feb 8, 2023
Nov 22, 2019
Apr 16, 2025
Feb 12, 2020
Feb 27, 2020
Feb 26, 2016
Apr 9, 2025
Apr 22, 2025
Apr 10, 2025
Apr 7, 2025
Apr 22, 2025
Apr 22, 2016
Feb 9, 2023
May 7, 2021
Feb 4, 2019

Repository files navigation

OPUS 4

OPUS 4 is an open source software under the GNU General Public Licence for the operation of intitutional document servers and repositories. OPUS is an acronym for Online Publikationsverbund University Stuttgart. It was originally developed at the university library in Stuttgart at the end of the 90's. OPUS 4 is a complete redevelopment that was created as part of a DFG (Deutsche Forschungsgemeinschaft) project between 2008 and 2010. Since then the development has been continued at KOBV (Kooperativer Bibliotheksverbund Berlin-Brandenburg) mostly.

OPUS 4

The current version of OPUS 4 is 4.8.0.14. It is available on the master branch and compatible with PHP 7.1 to 8.1.

Documentation : Information on setting up a repository, for users and administrators.

Developers : Information for developers.

We are in the process to moving the developer information into the GitHub Wiki. Specific information about OPUS 4 packages, might be found in the Wiki pages of their repositories.

Testing OPUS 4

You can run OPUS 4 using Vagrant. This makes it easy to create a VM running OPUS 4 for testing or even development. More information in the Wiki:

https://github.com/OPUS4/application/wiki/Vagrant

Questions & Issues

Questions should be asked through the OPUS 4 mailing list. We are sending out release announcements and other information using the mailing list.

Bugs and suggestions can be communicated to the development team as issues here on GitHub. For suggestions of new features or changes in OPUS 4 it is important to communicate the reason from a user perspective, the use case. We need to understand why to make the best decision for how to implement something new.

If you have made modifications to OPUS 4 that could be useful for the entire community feel free to submit a pull request. We won't always be able to respond immediately, but we will take a look at your changes. It is important to communicate the idea behind a modification.

More Information

Currently, we are using an internal Jira-System at KOBV to manage the tasks for the OPUS 4 development. We are starting to use GitHub more and more to communicate the development goals and progress. At the moment, the milestones here on GitHub mostly reflect larger technical debts that need to be fixed in order to continue to expand the functionality of OPUS 4 in the future. The projects are meant to show currently ongoing efforts. However, we are still experimenting and trying to figure out how to use the GitHub features in the best possible way without it taking too much time away from the developing work.