Rector's Directive No. 24/2018 ****************************************************************************************** * ****************************************************************************************** ****************************************************************************************** * Registration of Creative Activities at Charles University ****************************************************************************************** Date of effect: 1 October 2018 ****************************************************************************************** * Part I - Introductory Provisions ****************************************************************************************** *========================================================================================= * Article 1 *========================================================================================= 1. This directive governs the rules and procedures for registering, collecting, managing, following data at Charles University (the “University”): a) data on the employees and students who are involved (or are to become involved) in crea (“authors”) ; b) data on grants, projects, and other sources of funding, in particular in the area of cr and innovation (“register of activities”); and c) data on creative outputs (“register of outputs”). 2. This directive is based, in particular, on the applicable Czech legislation, guidelines the Government’s Research, Development, and Innovation Council (“RVVI”), and internal regu University, in particular the following acts: a) Act No. 130/2002 Sb., on the support of research and development (the “Act”); b) Act No. 111/1998 Sb., to regulate higher education institutions; c) Act No. 215/2004 Sb., to amend certain relationships within the area of state aid, and on the support of research and development; d) Government Decree No. 397/2009 Sb., on an information system for research, experimental innovation (the “Government Decree”); e) Government Decree No. 274/2016 Sb., to regulate accreditation standards in higher educa f) Government Decree No. 275/2016 Sb., on areas of study in higher education; g) Government Resolution No. 8 of 13 January 2016, to approve the Conception of the Inform Research, Experimental Development and Innovation for the Period 2016-2020; h) Guidelines for the Evaluation of Outputs of Research Organisations and Outputs of Compl issued under section 35 of the Act (the “evaluation guidelines”); i) Article 14 (3) and Article 46 (2) of the Constitution of the University; j) Code of Procedure for the Internal Evaluation Board of the University; and a) Rules for the System of Internal Evaluation and Quality Assurance of Charles University 3. The records kept in accordance with this directive serve, in particular, for the follow a) to document creative activities of the authors and the outputs thereof; b) to compile output data sets for the Information System for Research, Experimental Devel Innovation in accordance with section 32 (3) of the Act and section 4 of the Government De VaVaI”); c) to create overviews and analyses for annual activity reports of the University, the fac other units, and for the needs of the management of the University, individual faculties, including for evaluation, and as a basis for the distribution of revenue of the University with Article 49 (1) of the Constitution; d) to provide background materials for internal evaluation and quality assurance at the Un including background materials necessary for accreditation under Government Decrees No. 27 regulate accreditation standards in higher education, and No. 275/2016 Sb., on areas of st education, and in accordance with internal regulations and other regulations of the Univer e) to acquire full texts of selected outputs for the institutional repository of the Unive accordance with the rules stipulated in a special Rector’s directive; f) to make available selected data; and g) for other purposes and projects in which the University engages. 4. Registration is done using the modules of the centralised information system for regist evaluating creative activities at Charles University (“IS Věda”) managed via the Informati the University (“University IS”) by the Computer Science Centre of the University (the “Co Centre”). *========================================================================================= * Article 2 *========================================================================================= Internal Classification of Academic Fields at the University 1. The registers under this directive and for the purposes of internal quality evaluation adhere to the internal classification of academic fields at the University (“internal clas comprising four levels: a) Panel – in accordance with the evaluation guidelines and the Code of Procedure for the Evaluation Board, internal classification is organised into four panels: i. arts and humanities (“HUM”); ii. social sciences (“SOC”); iii. natural sciences (“SCI”); and iv. medical and health sciences (“MED”). b) Research area – for the purposes of internal quality evaluation at the University, rese been established within panels, listing academic fields under letter c) of this paragraph the following criteria: i. relatedness/closeness of the fields; ii. possibility to use uniform evaluation tools across the research area; and iii. uniform evaluation parameters. c) Academic field – academic fields are basic units of internal classification; academic f be specified for grants, projects, outputs, and authors in accordance with the rules set o directive. d) Subfield – where it is necessary to subdivide an academic field in order to further dif relatedness/closeness among a greater number of programmes of study, subfields are establi be stipulated whether it is mandatory to indicate a particular subfield when classifying a outputs. 2. In addition, internal classification includes relations to other systems of structuring categorisation by field, in particular the following: a) a loose relation implying relatedness/closeness between an academic field and the categ Web of Science and Scopus databases; b) a loose relation implying relatedness/closeness between an academic field or, where rel subfield, and a programme of study offered at the University; c) a loose relation implying relatedness/closeness between an academic field or, where rel subfield, and a field for the associate professorship appointment procedure or a field for professorship appointment procedure offered at the University; d) a loose relation implying relatedness between an academic field and an area of study; a e) a close relation between an academic field and one and only field in the code list of I 3. Furthermore, internal classification includes information on the types and sub-types of in the respective research areas. 4. The form and content of internal classification have been determined on the basis of ac discussions across the University, and are managed by the Research Support Office, under t the competent Vice-Rector who, usually annually, launches a feedback survey for the submis regarding any updates to internal classification. 5. The internal classification currently in force is available in electronic form in the O Evaluation of IS Věda karlos.cernoch@post.cz (“Hodnocení systému IS Věda”). ****************************************************************************************** * Part II - Register of Authors ****************************************************************************************** *========================================================================================= * Article 3 *========================================================================================= Authors are primarily registered in the WhoIs personnel system and in the Student Informat data on authors entered in these systems are further used, in accordance with this directi Věda system, and are complemented, via this system, by the additional data referred to in *========================================================================================= * Article 4 *========================================================================================= Assignment of Persons to Academic Fields of Internal Classification 1. For the purposes of internal quality evaluation, it is necessary to assign authors to t fields of internal classification. 2. Authors are required to enter assignment details provided that during the evaluation pe satisfied the following criteria: a) their involvement rate within their employment relationship, with a pay band stipulated implementing regulation on internal evaluation under Article 7 (19) of the Rules for the S Evaluation and Quality Assurance (the “Implementing Regulation”), or with an employment co an agreed contractual pay and an ensuing right to membership in the academic community, is respect to a faculty or other unit, equal to (or higher than) the so-called minimum involv core staff, as determined by the Implementing Regulation on internal evaluation; or b) they are or were doctoral students and had, for at least one day in a given period, the student under the Higher Education Act; or c) they are or were internal authors of an output registered in the register of outputs; o d) they are or were internal investigators in a grant/project registered in the register o 3. The assignment of other employees or students who are expected to participate in the cr of a faculty or other unit can be done on a voluntary basis. 4. The coordinator for the internal quality evaluation of creative activities for the whol other unit, or a person designated by the coordinator for a basic unit of a faculty, recor in IS Věda, within the deadline stipulated by the competent Vice-Rector. 5. An author must be assigned to at least one and no more than three academic fields. If a qualifies for assignment at several faculties, this limitation applies to each faculty ind the author may be assigned to the same or different academic fields at the respective facu on the actual situation. *========================================================================================= * Article 5 *========================================================================================= Personal Identifiers for Researchers 1. In order to ensure unique identification of the author of a published output, the follo identifiers (“identifiers”) are used in addition to the personal number assigned by the Un a) ORCID ID; b) ResearcherID of the Web of Science database; and c) Scopus Author ID of the Scopus database. 2. The identifiers are registered via IS Věda. 3. The guidelines issued under Article 13 (4) (a) or Article 13 (6) (c) of this directive, Rector’s directive may stipulate the tasks which require the use of an identifier in the r authors. ****************************************************************************************** * Part III - Register of Activities ****************************************************************************************** *========================================================================================= * Article 6 *========================================================================================= 1. Activities are registered in the GAP module of IS Věda (“GAP module”). 2. The GAP module is the central site for the registration of all operations referred to i except for the projects of the Grant Agency of the University covered by the operations un (c) of this directive. Such projects are primarily registered in a separate application of of the University, which automatically feeds selected data into the GAP module, where they for reading only. *========================================================================================= * Article 7 *========================================================================================= Content and Formalities of the Register of Activities 1. The register encompasses the following operations : a) projects funded from the special-purpose support under section 3 (2) (a), (b), and (d) b) internal projects of the University funded from the special-purpose support for specifi research under section 3 (2) (c) of the Act; c) internal projects, programmes, and other internal instruments of the University for the science and research activities from the institutional support under section 3 (3) (a) of d) foreign and international grants, including projects being funded as per section 3 (3) e) projects implemented within RDI operational programmes; f) projects of contractual and collaborative research; g) any other grants and projects to support science, research, and other creative activiti h) any “de minimis” aid; i) participation in research infrastructures and other similar research groups; and j) licence agreements (both acquired and provided) to industrial property. 2. The register includes the following: a) projects under paragraph 1 (a) and (b) commenced in 2010 or later; b) projects, programmes, and other instruments under paragraph 1 (c) commenced in 2010 or c) projects under paragraph 1 (d) carried out since 2012; d) projects under paragraph 1 (e) and (g) carried out since 2015; e) projects under paragraph 1 (f) carried out since 2011; f) aid under paragraph 1 (h) received since 2013; g) research infrastructures under paragraph 1 (i) involving the faculties and other units from 2017 onwards; h) agreements under paragraph 1 (j) effective since 2015; and i) basic information on project applications (for both approved and rejected projects) in paragraph 1 (a), (d), (e), and (g) submitted from 2019 onwards. 3. The basic mandatory data to be registered include the following: a) identification number (number of the project, grant, contract, etc.) and text identific summary of the subject-matter); b) start date and end date of the implementation (or effective period of the contract); c) name of the principal investigator (or person in charge); d) name of the faculty or other unit involved in the implementation; e) a list of all foreign organisations involved in the project, including the country; f) basic identification details of the support provider, or of the contracting party; g) identification of the grant programme ; h) basic financial details (usually the total amount of the grant or project, or the total contract, and the proportion of funding for the faculty or other unit); and i) a list of envisaged clinical studies involving human subjects undertaken as part of the information on the registration status in the respective register. 4. The records on operations under paragraph 1 (a) to (g) include classification into acad accordance with internal classification under the following conditions: a) assignment to one academic field is always mandatory. If there are any overlaps among f possible to record assignment to several academic fields; b) if assignment is made to academic fields which have subfields, it is possible to record three subfields for a particular academic field. If a subfield is required for a particula at least one subfield must be selected; c) in the case of projects registered in IS VaVaI, the faculty (or other unit where approp required to ensure, in cooperation with the principal investigator, that the assignment to VaVaI is consistent with the assignment of the project within internal classification and the conversion rules for academic fields at the University and the IS VaVaI code list of a as set out for internal classification. 5. The guidelines issued under Article 13 (4) (a) of this directive set out other mandator mandatory, and optional data that are registered within the respective operational areas. 6. When entering records, priority is given to the code lists of IS Věda; other values are necessary value is not included in the code list. When entering the data on investigators or students of the University, it is mandatory to use the persons code list, into which th the central personnel register of the University are automatically fed. 7. Access to and management of records are governed by the following basic rules: a) the records can be accessed solely by the designated persons of a faculty or other unit b) where several faculties or other units are involved in grants and projects, the respect other units each make a separate record. 8. A Rector’s directive or guidelines issued under Article 13 (4) (a) of this directive ma certain operations or parts thereof, different rules on access and management. ****************************************************************************************** * Part IV - Register of Outputs ****************************************************************************************** *========================================================================================= * Article 8 *========================================================================================= 1. Outputs are registered in the module OBD of IS Věda (“OBD module”). 2. The OBD module is a primary source of data on the outputs of the University. 3. Data are collected continuously throughout the year. The records on outputs entered aft collection deadline announced by the University coordinator for a particular year are not data set prepared for IS VaVaI for the year. Such records are included in the data set for year. *========================================================================================= * Article 9 *========================================================================================= Content and Formalities of the Register of Outputs 1. It is mandatory to collect data on all kinds of outputs as defined in the valid evaluat with the structuring specified in the guidelines issued under Article 13 (6) (c) of this d 2. The extent of the data on individual outputs is set out in the guidelines issued under (6) (c) of this directive, in particular on the basis of the requirements set out in secti Government Decree, the guidelines, and other instructions given by the RVVI, and any other University. 3. Access to, entering, and management of records are governed in particular by the follow a) One record only corresponds to any output in the OBD module. b) A record must be entered within three months of the publication of the output (or of ma available to the public), but no later than by the data collection deadline announced for c) Every output may be registered only with respect to such employment or study relationsh that is linked to his or her studies and/or creative activities at the University, and on which the output was created. d) When entering records, priority is given to the code lists of IS Věda; other values are necessary value is not included in the code list. When entering the data on authors who ar students of the University, it is mandatory to use the persons code list, into which the r central personnel register of the University are automatically fed. e) Every registered output is assigned to academic fields in accordance with internal clas the following rules: i. Assignment to one academic field is mandatory. Based on such primary assignment, the ou included in the data set for IS VaVaI, shown in the corresponding field according to the c VaVaI and assigned to a corresponding research area for the purposes of internal quality e University. ii. It is possible to assign the output to two more fields. Such secondary assignment is u conjunction with the primary assignment, to establish relatedness/closeness between the ou programmes of study, as well as for other purposes not requiring solely a close relation. iii. If the assignment is made to academic fields which have subfields, it is possible to to no more than three subfields of an academic field. If a subfield is required for a part field, at least one subfield must be selected. f) A record is always managed at one workplace (usually the basic unit of the author who e record); if the recorded output involves authors from several faculties or other units, th data processing officer and coordinator for the register of outputs are required to cooper processing officers and coordinators for the register of outputs from other faculties or o employees or students have co-authored the output, in order to synergise the production of complete records. g) A record can be edited by the owner and the superordinate managers to the extent corres record approval stage (i.e., based on the record status). The records approved on the resp are marked as having a particular status, with a view to achieving the final status as soo Records with the final status can be edited only by users with the rights of a coordinator h) All records are available for reading to all users who have signed in. The records with status are published (without attached files) on the public interface of IS Věda. 4. If it is necessary, for the internal needs of a faculty or other unit of the University co-authorship share with respect to outputs, the dean or director of other unit can stipul called “intellectual share” will be used internally, in accordance with the following rule a) An intellectual share is defined as a co-authorship share in a particular output, expre percentage for each author who is an employee or student of the University; the sum of int of all authors, including authors outside the University, is 100% for a particular record. are not employees or students of the University, an intellectual share is determined colle of them. b) If the authors from a faculty or other unit which uses intellectual shares on the basis of the dean or director are named in a record managed by another faculty or unit, such fac allow them to enter details in the record about their respective intellectual shares. 5. For the purposes of internal quality evaluation of creative activities, if authors from faculty or unit participated in the creation of outputs, the share of a faculty or other u determined on the basis of the proportionate number of participating authors from individu deducting the share of external authors; the so-called “intellectual shares” under paragra taken into account. Guidance for the calculation of a share of external authors will be se Implementing Regulation on internal quality evaluation of creative activities. 6. For the purposes of internal and national quality evaluation of creative activities, in outputs registered in the Web of Science or Scopus databases, it is necessary to register identifier of the record from such database. 7. In addition, the OBD module is used to store full texts of selected outputs, in particu following purposes: a) to check the records entered; b) to allow for evaluation of creative activities; and c) to fulfil the conditions stipulated by the provider of funding for the project within w was created. 8. The full text files will be made available solely to designated persons and solely to t by the access rights set for each respective file. The Rector will make provisions, in a s for other uses of uploaded full texts of outputs and any publication thereof in the digita the University managed by the Central Library. 9. Based on a decision made by a dean or director of other unit, the full texts of selecte uploaded in the OBD module can be also uploaded to the interuniversity database of outputs with the texts of other outputs. The results of such comparison are always made available of the outputs and coordinators from the faculties and other units of the University where are employed or pursue their studies. The interuniversity database of outputs is not inten publication of or for otherwise making available the full texts of outputs. If copyright i could occur, the coordinator can remove the full text of an output from the export for the database of outputs, upon the author’s request. ****************************************************************************************** * Part V ****************************************************************************************** Organisational Arrangements for Registration of Creative Activities *========================================================================================= * Article 10 *========================================================================================= Organisational Arrangements at Faculties and Other Units 1. In order to ensure registration of creative activities at individual faculties and othe deans and directors make the following arrangements: a) they appoint a coordinator for the register of identifiers; b) they appoint a coordinator for the register of activities and, where appropriate, resea charge of specific operations within the register of activities; c) they appoint a coordinator for the register of outputs; d) they designate a circle of persons authorised to inspect all records in the register of faculty or other unit; e) they decide whether the records in the register of activities will be made available to investigators of projects (or to persons in charge) and other members of investigation tea f) they duly ensure that attributes of the appointed coordinators are updated in the perso the University. 2. It is possible to merge the coordinators’ posts referred to in paragraph 1 (a) to (c) a other unit where appropriate; however, such posts are always entrusted to persons employed other unit. 3. In order to ensure registration of outputs, the heads of basic units of a faculty to wh or students involved in the creative activities are attached, appoint a data processing of the register of outputs, and they inform the faculty coordinator for the register of outpu appointment or changes to such appointment. *========================================================================================= * Article 11 *========================================================================================= Responsibilities of Authors 1. For the purposes of the register of identifiers under Article 5 of this directive, the required to enter their identifiers in the register in IS Věda, either themselves or with a coordinator of the faculty or other unit, on the date they enter their first output in t of outputs, but in the case of employees and doctoral students no later than within two mo commencement of their employment or study at the University. 2. The responsibility for the recording of the output in the OBD module rests with the aut output; if the record is in the storage for pre-imported records, the author always uses a pre-imported version of the record. The author can discharge this duty himself/herself or be represented by another employee of the same basic unit of a faculty or other unit of th or by another person according to the rules set out by the dean or director. In the case o of authors, this responsibility rests with the first author among those who are employees the University, in the same order in which the authors are named in the output. The facult can further modify this rule in the case of outputs with no involvement of authors from ot other units of the University. 3. In addition, the author of an output has in particular the following responsibilities: a) responsibility for the completeness, correctness, and accuracy of the record on the out constitutes a complete bibliographical description of the output and indicate the link of source of funding and a field in accordance with internal classification; b) to upload the full text of the output if: i. the output was created while investigating a project funded within a programme which pr publication of outputs in the open access mode; ii. the output is to be presented for a peer review evaluation; or iii. such duty has been prescribed at the faculty or other unit by the dean or director fo internal checks of the records entered; c) to provide the data processing officer or coordinator at a faculty or other unit with a confirming the accuracy and completeness of a record if there are doubts about certain typ which cannot be traced in the basic databases used by the RVVI when checking the records; d) to present an output for check on request, in accordance with sections 12 and 13 of the e) to ensure that the text of the output intended for publication which was created in the employment or studies of the author at the University includes affiliation to the Universi other unit, in accordance with the format set out in Appendix 1 to this directive; f) to continuously rank the principal outputs over the past monitored period in the OBD mo to preparing accreditation documents and selecting outputs for the internal and national e creative activities. 4. If the check under paragraph 3 (c) or (d) is carried out at a time when the author is n employee or student of the University, the respective duty of the author is assumed by the officer for the register of outputs referred to in Article 10 (3) of this directive. 5. Persons responsible for the investigation of projects and grants (in particular princip and for the preparation and discharge of obligations arising from the registered contracts cooperate as necessary with the workers engaging in the registration of activities. *========================================================================================= * Article 12 *========================================================================================= Responsibilities of Designated Persons at Faculties and Other Units 1. The coordinator for the register of identifiers has in particular the following respons a) to provide advice and guidance to the authors on how to manage profiles and use persona b) to continuously check that the identifiers have been entered in the register and if not cooperation with the authors, that they are entered; c) to inform the authors of the duty to enter, for all their publications, primarily the E the affiliation as set out in the Appendix to this directive, as well as the English name in accordance with the applicable dean’s directive if such directive exists; d) to cooperate with coordinators for other registers; and e) to cooperate as necessary with coordinators and other stakeholders involved in internal evaluation at the University. 2. The coordinator for the register of activities has in particular the following responsi a) he or she has access to all records in the GAP module at a faculty or other unit; b) he or she has the responsibility for due registration of activities at a faculty or oth whole; c) if no research officer has been appointed at a faculty for specific operations, to ensu for such operations are entered in a timely and due manner; d) to provide training and advice for research officers in charge of specific operations o and use records in the GAP module; e) to deal with technical problems, in cooperation with the University coordinator, which registration; f) to ensure, in cooperation with the University coordinator, user access for other users other unit; g) to ensure, in cooperation with the University coordinator, suitable conditions for the the decision of a dean or director under Article 10 (1) (d) and (e) of this directive; h) to ensure data imports in operational areas where such imports are possible; i) to prepare overviews and analyses for the needs of a faculty or other unit; j) to cooperate with other workplaces at a faculty or other unit in discharging the tasks specific monitored operations, in particular when collecting data for the register of outp k) if no research officer has been appointed at a faculty or other unit for specific opera that records for such operations are entered in a timely and due manner; l) to cooperate with coordinators for other registers; m) to communicate with the University coordinator and University research officers, and to training and methodology meetings; and n) to cooperate as necessary with coordinators and other stakeholders involved in internal evaluation at the University. 3. The research officer in charge of specific operations within the register of activities records for such operations are entered in a timely and due manner. 4. The data processing officer for the register of outputs has in particular the following responsibilities: a) to provide consultations for individual authors on how to enter records in the OBD modu b) to carry out data imports from external sources into the storage for pre-imported recor c) to check the records entered by authors who are employees or students at a basic unit o d) to check whether the records entered by the authors correspond to the outputs published they comply with the guidelines and other guidance from the RVVI, including the responsibi an output in a specific type in accordance with the guidelines; e) to ensure, in cooperation with the authors, that the full text of the output is uploade other additional details and annexes, in the completed record if the output has been selec review evaluation; f) to decide whether the records on outputs will be included in the data set for IS VaVaI year; and g) to cooperate as necessary with coordinators and other stakeholders involved in internal evaluation at the University. 5. The coordinator for the register of outputs has in particular the following responsibil a) to ensure training for data processing officers and other users of the OBD module in th evaluation guidelines, other guidance from the RVVI, and in the University-wide guidelines Article 13 (6) (c) of this directive; b) to provide advice to the data processing officers on how to enter and use records in th c) to ensure, in cooperation with the authors and data processing officers, that the full output is subsequently uploaded, as well as any other additional details and annexes, in t record if the output has been selected for a peer review evaluation; d) to set access rights for data processing officers; e) he or she is responsible for the formal inclusion of outputs in the data set for IS VaV particular year; f) to set a deadline for authors and data processing officers to finish the collection of particular year; g) to prepare data sets for IS VaVaI for a particular year within the deadlines set by the coordinator; h) to prepare overviews and analyses for the needs of a faculty or other unit of the Unive i) to carry out random checks on selected outputs; j) to cooperate with the coordinators for other registers; k) to communicate with the University coordinator for the register and to participate in t methodology meetings organised by the University coordinator; l) in collaboration with the University coordinator, to deal with technical problems which registration; m) to cooperate as necessary with coordinators and other stakeholders involved in internal evaluation at the University; and n) to discharge also the duties of a data processing officer at theological faculties and the University. 6. If a data processing officer or coordinator for the register of outputs identifies mist irregularities in a record on output entered in the OBD module, he or she will return it t for correction. If there is a risk of delay, the coordinator or data processing officer wi the record himself/herself. The changes made are automatically recorded in the history of which is accessible to the user who had entered the record, as well as to the data process coordinator. 7. For the purposes of checks and verifications as to whether the records on outputs are a particular in the light of the guidelines and other guidance from the RVVI, the coordinato or other unit and the University coordinator may, at any time during the data collection s the comparison of the records entered in the OBD module with the records on outputs contai interuniversity database of outputs; and based on such a comparison, they can ask the auth processing officers (or the University coordinator can ask the coordinators at faculties a to correct the data on outputs entered in the OBD module. 8. The responsibility for the accuracy of the data entered and any damage caused by the en data or by failure to enter the records rests with the faculty or other unit which had ent required to enter, the record in the respective register. *========================================================================================= * Article 13 *========================================================================================= Organisational Arrangements at the University Level 1. At the University level, the Research Support Office serves as the methodology and coor the registers under this directive; the head of the department appoints the following pers a) the University coordinator for the register of activities; b) the University research officers in charge of specific operations within the register o except for the operations under Article 7 (1) (f), (h), and (j) of this directive; c) the University coordinator for the register of outputs; and d) the University coordinator for the register of identifiers. 2. With respect to the register of activities, the necessary background documents for guid guidance are prepared by the following bodies, by their own University research officers: a) The Finance Department of the Rectorate for the operations under Article 7 (1) (h) of t and b) The Centre for Knowledge and Technology Transfer for the operations under Article 7 (1) this directive. 3. With respect to the register of outputs, the Central Library of the University provides background documents for guidelines and development of the system to facilitate publicatio mode. 4. The University coordinator for the register of activities has in particular the followi responsibilities: a) to prepare University-wide guidelines and binding recommendations concerning the regist b) to provide training and advice on how to carry out registration and operate the GAP mod coordinators of the register at faculties and other units, and to deal with their requests c) to prepare overviews and analyses for the whole University for the needs of the managem University; d) to adjust the settings and content of the respective code lists of the GAP module; e) to cooperate as necessary with the Computer Science Centre in the specification of tech to be made to the register and in finding solutions to technical problems; and f) to cooperate as necessary with coordinators and other stakeholders involved in internal evaluation of creative activities at the University. 5. The University research officers in charge of the register of activities have in partic following responsibilities: a) to provide guidance to the coordinators for the register and to the research officers i specific operations at the faculties and other units; b) to communicate with the providers within the specific operations in order to acquire in for the purposes of registration; c) to cooperate as necessary with the Computer Science Centre in the specification of tech to be made to the register and in finding solutions to technical problems; and d) to cooperate as necessary with coordinators and other stakeholders involved in internal evaluation at the University. 6. The University coordinator for the register of outputs has in particular the following a) to communicate with the RVVI and individual providers, including to transmit the Univer for IS VaVaI to individual providers within the deadlines stipulated by these providers; b) to announce binding deadlines for faculties and other units of the University by which IS VaVaI are to be transmitted; c) to prepare University-wide guidelines and recommendations concerning data collection, i recording of the outputs in IS VaVaI, with due regard to the legislative developments in t to the evaluation guidelines, updates to other guidelines of the RVVI, and to the needs of d) to provide training and advice on how to carry out registration and operate the OBD mod coordinators of the register at faculties and other units, and to deal with their requests e) to inform the coordinators of the register at faculties and other units of any updates procedures and to other guidelines of the RVVI for a particular year; f) to manage and update a website which provides information on data collection and the re outputs in IS VaVaI; g) to manage the setting and content of the respective code lists of the OBD module; h) to prepare overviews and analyses for the whole University as required by the managemen University; i) to cooperate as necessary with the Computer Science Centre in the specification of tech to be made to the register and in finding solutions to technical problems; and j) to cooperate as necessary with coordinators and other stakeholders involved in internal evaluation at the University. 7. The University coordinator for the register of identifiers has in particular the follow responsibilities: a) to provide training and advice on how to carry out registration and operate the relevan Věda for the coordinators of the register at faculties and other units; b) to manage and update a website which provides information on how to create and register c) to cooperate as necessary with the Computer Science Centre in the specification of tech to be made to the register and in finding solutions to technical problems; and d) to cooperate as necessary with coordinators and other stakeholders involved in internal evaluation at the University. *========================================================================================= * Article 14 *========================================================================================= Technical Support and Assistance 1. The Computer Science Centre is responsible for the technical side of the operation of I the preparation of technical documentation and user documentation; furthermore, the Comput provides training on the operation of the respective modules of the system, as well as tec (including built-in tools for user support), for the following persons: a) University coordinators; b) University research officers; and c) coordinators at faculties and other units. 2. With respect to user support, all users of the registers use, by way of priority, the H user support tool) which is part of IS Věda. ****************************************************************************************** * Part VI ****************************************************************************************** *========================================================================================= * Article 15 *========================================================================================= Repeal 1. Upon entry into effect of this directive, the following Rector’s directives are repeale a) No. 28/2016 – Introduction of Personal Identifiers for Unique Identification of Authors Outputs at Charles University; b) No. 53/2017 – Central Register of Grants, Projects, De Minimis Aid, and Other Sources o Particular in the Area of Research, Development, and Innovation; and c) No. 31/2017 – Register of Outputs of Creative Activities. *========================================================================================= * Article 16 Final Provisions *========================================================================================= 1. The appendix to this directive sets out a list of official affiliations of the Universi 2. This directive becomes effective on 1 October 2018. In Prague on 21 June 2018 Prof. MUDr. Tomáš Zima, DrSc., MBA ? Appendix Official Affiliations of Charles University 1. With respect to all outputs created in the course of employment or studies at Universit are required to state the official institutional affiliation in the language of the output of University, name of faculty/unit, for example: “Univerzita Karlova, 3. lékařská fakulta University, Third Faculty of Medicine”. 2. The form of the affiliation is set out in Appen Constitution of Charles University. If it is necessary to shorten the affiliation in order the publisher’s rules or for other reasons, the following Czech or English abbreviations w Czech name Czech abbreviation English ab Univerzita Karlova  Katolická teologická fakulta  Evangelická teologická fakulta  Husitská teologická fakulta  Právnická fakulta  1. lékařská fakulta  2. lékařská fakulta  3. lékařská fakulta  Lékařská fakulta v Plzni  Lékařská fakulta v Hradci Králové Farmaceutická fakulta v Hradci Králové Filozofická fakulta  Přírodovědecká fakulta  Matematicko-fyzikální fakulta  Pedagogická fakulta  Fakulta sociálních věd  Fakulta tělesné výchovy a sportu Fakulta humanitních studií  Ústav dějin Univerzity Karlovy a archiv Univerzity Karlovy Centrum pro otázky životního prostředí Centrum pro teoretická studia  Centrum pro ekonomický výzkum a doktorské studium