About This Repository
Table of Contents
Do you need any advice?
If you need advice on any of the above steps, do not hesitate to contact the open access coordinator at your unit. For legal questions, contact the lawyer of the Open Science Support Centre. All contact information can be found on the web pages of the Open Science Support Centre.
Charles University’s repository of publishing activities is a place to store and make available the full texts of the results of science and research of authors at Charles University. The repository is operated in the DSpace system.
Employees and students of Charles University can store their results in the repository. Storing and making the result available (auto-archiving) in the CU Repository of Publishing Activities is voluntary for CU employees and students. The process of auto-archiving results in the repository is established in Rector's Directive no. 40/2021, Records of creative activity, projects, and employee mobility at Charles University..
Auto-archiving of results in the repository takes place via the OBD IS Věda module. The results are then automatically transferred to this repository after being checked by the faculty open access coordinators.
Result types accepted in the repository and their accessibility
Full texts of selected types of results may be stored in the repository. A list of result types accepted in the repository is provided on the web pages Research outputs typology..
Full text results can be made available in the repository in any of the following accessibility modes:
|open access||The full text may be accessed online in the repository by all repository visitors under the selected licence.|
|open access with an embargo||The full text may be accessed online in the repository by all repository visitors under the selected licence, but only after a certain date (the date for ending the access embargo).|
|restricted access||The full text may be accessed in the repository by all users at Charles University who are logged in.|
Versions of full texts accepted in the repository
Full text results are accepted in the repository in any of the following versions: draft, preprint (submitted version), postprint (accepted version), published version, and updated version. A brief description of the full-text versions is provided in the table below.
|version of fulltext||description|
|Draft||Working version of the result.|
|Preprint (submitted version)||A version of the result finalized by the author and submitted for the review process.|
|Postprint (accepted version)||A version of the result after the review process with changes made by the author that is prepared for publication but that has not yet been formatted for print/for the journal layout.|
|Published version||A version of the result produced by the publisher with the final formatting and layout of the journal.|
|Updated version||A version of the result that was updated after being published.|
Licensing of full texts stored and made available in the repository
The licence specified for the stored full text of the result determines the extent to which visitors can use the repository. If a licensing agreement was concluded with a publisher, the choice of licence primarily depends on the terms of the licensing agreement.
One of the following licensing options can be used for full-text results intended to be stored and published in the repository:
|No licence||If the publisher allows autoarchiving in an institutional repository and the fulltext does not subject to any specific license, you can choose the "without license" licensing option. The fulltext is then published in the repository as read-only, i.e. in gratis open access mode. Repository visitors are entitled to download and print the fulltext published without a licence for their personal use only (in accordance with § 30 of Act No. 121/2000 Coll., the Copyright Act).|
|Creative Commons licence||The full text will be openly accessible. The extent to which users will be able to use your text depends on the specific licence. Rights and obligations arising from Creative Commons licences are defined by four licensing elements (BY, SA, ND, NC). These elements and their combinations make up the six licensing types. After selecting a specific Creative Commons licence in the respective version from the drop-down menu, a URL linking to the full text of the selected licence located on the Czech Creative Commons website is automatically generated.|
|Other licence||The terms of a licensing agreement concluded with a publisher impose the obligation to license the full text under a licence other than a Creative Commons licence. Select the other license option. You can choose this option even if no licensing agreement has been concluded, and you are entitled to make all decisions on the options for licensing the work.|
You can find more detailed information on the types of Creative Commons licences on the web pages CC Licences.
Mandatory, conditionally mandatory, and optional descriptive data of the result
In order to store and make a text available in the CU repository of publishing activities, we require a set of mandatory and conditionally mandatory descriptive data. Both types of descriptive data are mandatory, but when filling in conditionally mandatory data (and subsequently checking them), you can take into account whether the data can be found or obtained for the specific form of the result or for the current stage of publication of the result.
In addition to mandatory and conditionally mandatory descriptive data, you may fill in other optional descriptive data in the OBD IS Věda module in relation to storage and access in the repository. Completing these optional data and the accuracy of these data are not checked before the result is accepted in the repository.
However, filling in optional data allows you to do the following:
- display additional information in the preview of the result record in the repository;
- increase the probability of finding the relevant result in the repository;
- generate bibliographic citations for the results stored in the repository;
- ensure the collection of additional statistical information on the result stored in the repository.
You can find more detailed information on mandatory and conditionally mandatory descriptive data on the web pages Required metadata.
Acknowledgment of declarations required to store and make available the full text in the repository
A necessary step for storing and making available the full text of the result is also confirmation that all co-authors agree to storing and making available the respective version of the full text in the repository and conformation that this does not infringe the rights of the publisher or any other third party. You can confirm these facts by checking the respective box in the record of the result in the OBD IS Věda module.
Checking the declaration of consent of the co-authors to store and make available the full text in the repository is required even if the text has only one author (this is a necessary technical condition for uploading a text to the repository).
The complete texts for both declarations are as follows:
|Confirmation of consent of co-authors||I hereby declare that I have the consent of all co-authors to store and make available the attached full text of the work in the CU repository of publishing activities.|
|Confirmation of non-infringement of the rights of the publisher or another third party||I hereby declare that, by storing and making the file available in the CU repository of publishing activities, the rights of the publisher or other third parties are not infringed.|
If the declarations are not confirmed, the result will not be stored and made available in the repository and will remain stored only in the OBD IS Věda module. Detailed advice relating to the above confirmations are available on the web page Disclaimer.
Procedures for storing and making the result available in the repository
The steps can be summarized as follows:
|step order||step description|
|Step 1||Check to make sure the result type can be stored and made available in the repository. See the list of result types accepted in the repository.|
|Step 2||Check the licensing agreement with the publisher (provided the result is already published or its publication is planned in the future) and make sure that the result can be stored and made available in the repository and under what terms.|
|Step 3||If you are the author, arrange for the consent of any co-authors of the result to storing and making available the full text in the repository, or verify that the author has these consents. If needed, you can use sample form, prepared for you by the CU Open Science Support Centre.|
|Step 4||Log in to the OBD IS Věda module and create a new record or edit an existing record.|
|Step 5||Fill in all mandatory and relevant conditionally mandatory metadata of the result or, if they already exist, check that they are up-to-date and accurate.|
|Step 6||Enter the fulltext that you would like to store and make available in the repository in the respective part of the form for the result record in OBD.|
|Step 7||Select the version of the fulltext file and select its availability mode in the repository.|
|Step 8||(OPTIONAL) Enter any other files in the respective part of the form for the result record in OBD (e.g. the licensing agreement concluded with the publisher).|
Confirm by checking the relevant boxes in the result record in OBD next to the entered full text that:
|Step 10||Save the result record.|
After completing the above steps, the result record, including the attached fulltext, is checked by the open access coordinator. After approval by the open access coordinator, the result, including the attached fulltext, is automatically transferred from the OBD IS Věda module to this repository.
The approved and successfully uploaded result will have a separate record created in the repository for each of the versions of the attached full text.
You can make reference to the result record in the repository using a permanent link specified in the field Permanent link of the result record in the repository. The repository system uses the service HANDLE Resolver to create and maintain permanent links, and each of the results is assigned a unique HANDLE identifier, which is part of the permanent link. This identifier is assigned to the result when it is first transferred to the repository and remains valid even when updating the record.