Submission Preparation Checklist
As part of the submission process, authors are required to check off their submission's compliance with all of the following items, and submissions may be returned to authors that do not adhere to these guidelines.
- The submission is not a duplicate (i.e. it has not already been added by another editor).
- Permission to add the submission has been granted by the journal editors.
The data collected from registered and non-registered users of this journal falls within the scope of the standard functioning of peer-reviewed journals: it includes information that makes communication possible for the editorial process; it is used to inform readers about the authorship and editing of content; it enables the collection of aggregated data on readership behaviours, as well as tracking geopolitical and social elements of scholarly communication.
Data that will assist in developing this journal platform (Open Journal Systems – OJS) may be shared with its developer, Public Knowledge Project (PKP), in an anonymized and aggregated form. The data will not be sold by this journal or PKP, nor will it be used for purposes other than those stated here.
When an author makes a submission to this journal, they consent to any personal information that is supplied as part of the submission being stored on the University’s journal platform. Additionally, they consent to the same information being processed by the system, by the journal editors and by system administrators. It is the responsibility of the submitting author to ensure that all contributors to the submitted work have read this Privacy and Consent Policy, and consent to the same. Authors whose work is published in this journal are also responsible for any human subject data that features in their work.
When a user registers with this journal, they consent to having their personal information stored in the University’s journal platform. Additionally, they consent to the same information being processed by the system, by the journal editors and by system administrators.
- A cookie titled OJSSID is created when a user first visits a journal page. It is used to store a session ID and to facilitate logins.
- Performance cookies are created to analyse site usage, to help us measure and improve site functionality. Anonymous data about a user’s visit is collected and amalgamated with that of other visitors, so that it is not possible to personally identify a specific user from that information. Users can opt out of providing this information, with no impact on their experience of the journal website.
Users can control and/or delete cookies as you wish. For more information on this, see https://aboutcookies.org/. If a user decides to delete cookies and/or prevent them from being placed by the journal website, they may need to manually adjust some preferences every time they visit the website in future. Additionally, registered users will no longer be able to log into their accounts while cookies are blocked.
This journal seeks to comply with industry standards for data privacy, including the provision within the European Union’s General Data Protection Regulations (GDPR) for "data subject rights". These rights include:
- Breach notification – to be informed when an unauthorised entity accesses your personal information.
- Right of access – to view your personal information.
- Right to be forgotten – to have your personal information removed from the platform.
- Data portability – to request a copy of your personal information.
- Privacy by design – to be confident that technological developments on the platform are designed to ensure the continued privacy of your personal information.
The GDPR also recognises that there may be a "public interest in the availability of the data", which is particularly important for scholarly communications, when journal publishers are seeking to maintain public records for the published content with as much accuracy and integrity as possible.
If you have a user account and would like to have it deleted, please email the journal hosting service (email@example.com).