iThenticate is an online plagiarism detection software tool that screens documents (including among others, proposals, manuscripts, dissertations and thesis, journals, etc.) against millions of published documents available through the Internet and multiple web-based databases. UCF’s iThenticate is not a repository database and will preserve the confidentiality of the user’s information. Documents uploaded through UCF user accounts cannot be accessed by iThenticate company personnel. The iThenticate user license agreement prevents iThenticate from having access to or use of technology, ideas or proprietary data contained in the submitted documents.
ithenticate USE at ucf
UCF investigators are required to submit their proposals for review by iThenticate prior to proposal submission to the sponsoring agency, excluding proposal types which are exempt from such review as outlined on this site. The following documents define proposal review requirements by iThenticate at UCF.
Use of iThenticate at UCF is intended exclusively for the screening of:
- Proposals (under sponsored and non-sponsored research projects). iThenticate review must be conducted by the Principal Investigator, and
- Thesis and Dissertations. iThenticate review must be conducted by faculty advisors. Use of iThenticate for review of thesis/dissertations should be coordinated through a faculty advisor. [iThenticate should not be used to review student papers, exams, or book publication efforts. (Refer to Turnitin for these purposes].
- UCF grants “free-of-charge” access to iThenticate for investigators and faculty advisors.
Why is it important that investigators review their proposals through iThenticate?
- To ensure compliance with federal, state, and institutional requirements relating to the responsible and ethical conduct of research.
- To maintain public trust in the fields of science and engineering, as well as all other sponsored program activities supporting any other research discipline.
- To prevent the receipt at UCF of allegations of research misconduct by any university investigator (or research staff member, as applicable).
- Publication companies and funding agencies such as the National Science Foundation (NSF) and select DHHS agencies (among others), use iThenticateto screen submitted proposals for plagiarism immediately upon receipt.
how to access ithenticate?
There are two ways to access iThenticate at UCF:
- Automatic method:
This method involves automatic uploading of the proposal from the ORC/ARGIS Proposal Transmittal Form (PTF)/“Certs & Review” tab under question: Research Misconduct (RM) Certification. This section of the “Certs & Review” page must be completed by all investigators. However, the responsibility for choosing the method to route the proposal to is assigned to the Principal Investigator.
- Manual method:
This method involves the uploading of the proposal by the investigator directly in iThenticate via https://app.ithenticate.com/en_us/login
The manual method requires the user to have an activated iThenticate account and/or a reactivated account by an ORC/RIC authorized staff member, as applicable.
Requests for assistance with the manual method shall be submitted to email@example.com if:
- The investigator/faculty advisor is a first time user in need of a new iThenticate account for manual uploading, or
- The password to login into iThenticate has been forgotten or misplaced
instructions for using ithenticate
- DO NOT SIGN UP for an account directly in iThenticate. As a UCF user, investigators and faculty advisors are granted free-of charge access to iThenticate.
- When a new iThenticate user account is set-up and activated, and/or an existing account is reactivated by ORC/RIC, the user will receive an email from ORC/RIC confirmation completion of the pertinent action (activation of reactivation). The email will include instructions on how to access the system and how to conduct review. The user will also receive an iThenticate customer support email with instructions on where and how to login to the system and a temporary password to access the system. Such password will then be changed by the user to a password of his/her own.
- Once the user completes all instructions provided by iThenticate, the user will be able to process uploading of pertinent document(s) for review by the system. Uploaded documents must be readable files. Refer to link below (File Types and Size accepted by iThenticate) for additional details. Scanned copies are not considered readable files.
- Obtain the “Similarity Report Index” to review system results and assess such results to eliminate potential problem areas (as/if applicable).
- Complete information required on the PTF/”Certs and Review” tab, under question “Research Misconduct Certification” (name of uploaded document, date of review and RM Certification).
Quick Links to Instructions
ORC Quick Start Guide to iThenticate
Viewing a Matching Source (Source: iThenticate User Manual)
Viewing Modes (Source: iThenticate User Manual)
File Types and Size accepted by iThenticate (Source: iThenticate User Manual)
Additional information is provided on the iThenticate User Manual at:
proposals requiring ithenticate review
Investigators should utilize iThenticate when their proposal content contains attributions, citations, quoted material, facts, endnotes, footnotes, paraphrases, images, algorithms, formulas, and intellectual property from sources other than their original content.
We recommend citing your authored content from previously published works.
Is your proposal exempt from ithenticate review?
The following proposal types may be considered exempt from iThenticate review at UCF, if they meet the criteria provided in the descriptions below:
Exempt Proposal Types
Continuation Proposal - No changes to Research & Development (R&D) efforts from the original proposal (i.e. cost proposal and/or notification of personnel changes only). No revision to the approved statement of work (SOW).
Conference/Workshop - Administrative details for conference/workshop (i.e. agendas, biographical sketches, budgets) only. No SOW/training. No R&D.
Fellowship Proposal/Agreement- No SOW required by sponsor as a component of the grant application.
Intergovernmental Personnel Agreement (IPA) - Agreement permits employee to temporarily provide services to a federal, state, or local agency. Salary is covered by the agency during the IPA performance period. No R&D.
Internship Program - Work experience through a private corporation. PI does not contribute to work done by participant. Work site is determined by sponsor (i.e. college work/study programs). No R&D.
Purchase Order - Work (services or products) using existing UCF owned technology. Work does not require new efforts by the PI, Co-PI, or research team member to complete the work deliverable(s) (i.e. produced devices).
Service Administrative Analysis Program - Institutional administrative analysis project only. Statement of work is specified by the sponsor (i.e. university alliances).
Service Agreement - Specifications in the SOW are provided by the sponsor. Service is standard and does not involve R&D by the UCF PI, Co-PI, or research team member.
Sponsor Provides 100% of the Statement of Work - Applies to research and development (R&D) or training proposal where the PI, Co-PI, or research team member do not contribute to science or technical section of the proposal.
Travel Costs Account - Account created for support of costs to travel only (i.e. attendance of conference, meeting, or similar effort). No R&D.
Documentation of iThenticate Exemption in the PTF by Principal Investigator
If an exemption listed above is applicable to the proposal, the type should be documented by the PI in the Proposal Transmittal Form (PTF) by following the instructions below:
- Open the Certs & Review Tab in the PTF
- Select: “Upload proposal manually to iThenticate”
- Enter “Exempt” and list the exemption proposal type (i.e. Internship Program, Service Agreement) under Exempt Proposal Types
- Enter date when completing the certification
- Enter “Yes” to certify that the contents of the proposal have not been fabricated, falsified, or plagiarized.
For additional questions relating to exemptions, contact firstname.lastname@example.org prior to proposal submission.
Exempt Administrative Actions
(For use by ORC Research Integrity Compliance, C&G, and UCF Research Foundation administrative staff only.)
Balance Account - Internal account created for balance transfer of residual funds from project account and/or project specific balance for purposes as defined by sponsor. No R&D.
Cost Share and/or Matching Account - Account created to facilitate transfer of cost share or matching funds only. (Exemption for account is not applicable to main proposal record.)
Donation - Administered through the UCF Research Foundation (UCFRF). No SOW or deliverable submission required by PI, Co-PI, or research team member.
Florida High Tech Corridor Council (FHTTC) Proposal - Proposal submitted to FHTTC contains either the same SOW or a condensed SOW as the main proposal submitted to an outside industry partner funding source. FHTTC funding is provided as additional support for same project. (The main proposal completed iThenticate review, as required.)
Sister/Spin-off Account - Account created for financial accounting purposes only (i.e. participant support costs only project account, internal split of funding between PI/Co-PI, royalties, etc.)
Salary Cap Account - Account created for the salary amount remaining after the federal sponsor salary limit is reached.
To request the processing of an iThenticate account set-up/activation, or for the reactivation of an existing account, as well as to obtain general information about iThenticate usage by UCF investigators and/or faculty advisors, send email to: email@example.com.
For all other requests relating to iThenticate usage at UCF, please contact any of the following ORC staff members:
Primary Contact: Ms. Griselle Báez-Muñoz (Griselle.Baez-Munoz@ucf.edu
Other contacts: Ms. Paula Seigler (Paula.Seigler@ucf.edu
Mr. Douglas Backman, Director of Compliance (firstname.lastname@example.org
ORC/RIC Updated 6/2016