Anti-plagiarism Software PlagAware
JLU Giessen has been using the anti-plagiarism software from the German provider PlagAware since 2022.
Since March 16, 2022, the new anti-plagiarism software PlagAware has been activated for use by JLU Giessen employees.
On this page you will find a summary of all information and an FAQ on switching providers . We will update it continuously and keep you informed of any new developments.
On this page you will find helpful links to instructions on how to use PlagAware.
First steps
On the following manufacturer page you will find the detailed and helpful article on "Getting started with PlagAware - A guide to checking for plagiarism."
https://www.plagaware.com/de/anleitung-plagiatspruefung
Running a plagiarism check
You can find a more detailed article on the topic of 'Requesting a new plagiarism check' on the following page.
https://www.plagaware.com/de/plagiatspruefung-starten
Evaluating a plagiarism check
https://www.plagaware.com/de/ratgeber/plagiatspruefung-bewertung
Resetting a plagiarism check
https://www.plagaware.com/de/plagiatspruefung-zuruecksetzen
Frequently asked questions
Frequently asked questions about the use of PlagAware are answered on the following page:
There are area administrators for many JLU faculties and centers. They act as the first points of contact for access to PlagAware.
Please note: We are currently revising this structure, which means that there are still some gaps. If no area administrator is currently appointed for your area, please address your request directly to the HRZ. ( software-manage ).
Area | Name | |
---|---|---|
FB01 | Volker Stiebig | Volker.Stiebig@recht.uni-giessen.de |
FB02 | Jessica Bogenhard | Jessica.Bogenhard@wirtschaft.uni-giessen.de |
FB03 | Monika Carle and Ferdinand Diedam | it-support@fb03.uni-giessen.de |
FB04 | Anette Mag and Stefan Brenne | prometheus@fb04.uni-giessen.de |
FB05 | Katja Wenderoth | Katja.Wenderoth@romanistik.uni-giessen.de |
FB06 | Patricia Probst and Liane Umsonst | dekanat@fb06.uni-giessen.de |
FB07 | currently unknown | |
FB08 | currently unknown | |
FB09 | Karl Wettich | karl.wettich@agrar.uni-giessen.de |
FB10 | Michele Klymiuk | Michele.Klymiuk@vetmed.uni-giessen.de |
FB11 | Laurenz Wöstmann | laurenz.woestmann@dekanat.med.uni-giessen.de |
GCSC | Isabella Kalte | Isabella.Kalte@gcsc.uni-giessen.de |
GiZo | currently unknown | |
GGL | currently unknown | |
ZfbK | currently unknown |
1. Data protection information
- When setting up accounts (e.g. by department admins) via the PlagAware portal, personal data of the account holder, which is necessary for setting up the account, is transmitted to PlagAware. This includes last name, first name, e-mail address, and departmental affiliation (department, center, etc.).
- When logging into the PlagAware portal, passwords are transmitted in encrypted form.
- Submitted works are transmitted in encrypted form for verification.
- Additional data protection information from the provider PlagAware can be found at the following links:
- If you have any queries regarding the processing of your personal data in connection with the use of the PlagAware anti-plagiarism software, please contact datenschutz .
- Data processing via PlagAware takes place on the basis of an order processing contract in accordance with Art. 28 GDPR, taking into account and complying with applicable data protection regulations.
2. Guidelines for use
Personal and other sensitive data must be treated with the utmost care. Their use must be limited to what is absolutely necessary.
- At JLU, only departmental adminstrators and, of course, teaching staff—but not students—have direct access to PlagAware.
- All personal data must be removed before submitting the work for review. This is usually unproblematic, as the pages concerned (title page, statement on drafting, etc.) are not usually the subject of the content to be reviewed.
- Once the review has been completed, the reviewed work and reports must be deleted from the portal.
On this page you will find a collection of answers to frequently asked questions.
Question overview
Click on the question to go to the answer.
- Who is PlagAware?
- Why did JLU switch from Turnitin to PlagAware?
- How can I get an account?
- Can students also use PlagAware?
- What support services will be available?
- Who bears the license costs for the anti-plagiarism software?
Is your question not included or has it not been answered sufficiently?
Then please send an
e-mail to HRZ Licence Management.
1. Who is PlagAware?
PlagAware is a German company that has been active in the field of anti-plagiarism software for around 15 years. The server locations are located exclusively in Germany and are therefore subject to GDPR controls. PlagAware can point to numerous references in the university sector.
2. Why did JLU switch from Turnitin to PlagAware?
After around 8 years of using Turnitin, the executive board decided to evaluate its use. After an intensive review based on economic, technical, and data protection aspects, the evaluation revealed that Turnitin no longer offered the best overall package in terms of suitability for JLU's requirements. PlagAware achieved the best overall rating in this process. PlagAware was activated for users on March 16, 2022.
3. How can I get an account?
All JLU employees have the opportunity to obtain a PlagAware account for plagiarism checks. As in the past, area admins are available as points of contact. You can find this list here . In case of doubt, please contact the HRZ service address software-manage .
4. Can students also use PlagAware?
Students are still unable to carry out self-checks and in this case must contact the people in the faculties and centers who supervise their term paper, thesis, etc. It is then up to the subject-specific supervisors to decide whether they can check the work on their behalf.
5. What support and guidance is available?
https://www.uni-giessen.de/en/faculties/svc/it/it-service-centre/services/plagaware/intro
6. Who bears the license costs for the anti-plagiarism software?
As previously with Turnitin, the annual license costs will continue to be borne from central funds.