We hereby provide the clarification below:
Charles University, Central Library does not plan for any future migration from DSpace 6.x to DSpace 7.x, at least not in a short-term horizon (at least 2 to 3 years from now). Charles Univesity, Central Library currently handles both technical administration (technical infrastructure, server + SW administration and updates for newer version v DSpace 6.x) and content administration by itself or in cooperation with the Computer Science Center of the Charles University.
Any contract focused on a migration from DSpace 6.x to DSpace 7.x and / or additional services, such as long-term provision of DSpace as SaaS, long-term contract for any future customizations, etc., would be (and has to be) subject of a separate Tender. No such Tender was conducted in the past, nor it is underway right now. All Tenders centered around CU Digital Repository (DSpace 6.x) were focused on development of custom functionality which was subsequently deployed to the production environment by the Charles University employees.
With that said, Charles University, Central Library is for now only interested in the provision of the programming services by the Supplier that would result in development of the functionality described in the Invitation to Tender and its Annexes.
Resulting functionality should be based on the current CU Digital Repository code, based on the DSpace 6.3 code. If the Supplier within this tender wants to get access to the CU Digital Repository code, Charles University, Central Library can provided the access to its GitHub repository for a single account per supplier for the duration of this Tender. In case you are interested in getting access to the CU Digital Repository Github repository, please contact us and provide a valid GitHub account that could be provided with a Read access to our repository.
When the winning Suplier is choosen, access to the GitHub repository (for the purpose of developing the functionality needed) will be provided only to the winner of the Tender. Charles University, Central Library suggests that the development will be conducted on top of the current `master` branch of the CU Digital Repository code. The new funtionality should be preferrably submitted to the CU Digital Repository GitHub repository in a separate branch.