Download Eprints

[Alethia Tiell]

Informationon this website should be updated via PURE, our research management system. For issues and queries on outputs and open access, please contact the ePrints team at epr...@soton.ac.uk or view the University's Pure support pages.

ORCID Support provides basic ORCID functionality for the repository including the addition of a new ORCID metafield, ORCID rendering and validation, and basic reporting with the Generic Reporting Framework.

ORCID Support Advance builds upon the functionality of ORCID Support, and allows users to connect their repository profiles with their accounts on orcid.org. Once an account has been connected, the user may manage their orcid.org permissions, controlling how the repository reads and writes from orcid.org. If read permissions have been granted, works from orcid.org may be imported to the user's work area. If write permissions have been granted, records where the user's ORCID is present may be exported to their orcid.org profile.

ORCID Support adds a new orcid field to both the creators and editors field, as well as the adding a new stage to the edit user workflow where an ORCID may be stored. All of these fields are of type orcid, a special type of text field that validates the ORCID is of the correct format (16 digits broken into 4 groups of 4 separated by a dash, e.g. 0000-0003-1495-7122). The field also checks that the final digit of the ORCID, the checksum, is valid and a warning is displayed if the ORCID is invalid in any way.

Where space on the screen is more restricted, such as in citations, the ORCID itself is removed and only the green ORCID badge is displayed. The badge still links to the orcid.org profile and when hovered over, the ORCID is displayed in a green tooltip.

If you already have an orcid field in any of these three locations, the ORCID Support will skip creating its own. However, it will not update the existing field to the new orcid type. Therefore if one or more of the fields exist you will need to edit them manually to change their type from text to orcid after the ORCID Support plugin has been installed:

If you have pre-configured the creators' or editors' orcid sub-field, this will likely be in your archive's cfg/cfg.d/eprint_fields.pl. The user's orcid field will most likely be in your archive's cfg/cfg.d/user_fields.pl.

ORCID Support provides a function for rendering green ORCID badges which show the user's ORCID in a tooltip when hovered over. To add these in a citation, simply include the following when displaying creator or editor fields.

Before users can import or export from orcid.org, they first need to connect their repository user profiles with their orcid.org user profiles. This can be done via the Connect to ORCID link that appears in the menu area when the logged in user does not have an ORCID associated with their account.

When clicked, the user will be taken to a new screen where they may specify which permissions they grant the repository when connecting to their orcid.org profile. By default all permissions are granted unless specified otherwise, which includes allowing the repository to connect with the orcid.org profile, read restricted works from the profile, and update activities on the profile.

Once the user has specified which permissions they would like to grant the repository, clicking the Create or Connect your ORCID iD button, will take the user to the ORCID site where they may sign in to connect their existing ORCID, or may create a new ORCID if they do not already have one.

Each time the permissions are updated by clicking the Connect to ORCID button, the user will once again be asked to sign in to ORCID, as per the initial connection, so that orcid.org is aware of the permissions the user has granted to the repository.

When the Create and update publication details on your ORCID record check box is selected, the repository will try to update the user's orcid.org profile with details about their institution. By default, the institution will be added to the ORCID profile's Employment section. However the plugin's configuration may specify that certain user types should have their Education section updated instead.

When a user first connects their repository account to their ORCID account, and their ORCID is set in their user profile as a result, the repository does a search for all the eprints in the repository where that user's email is associated with one of ORCID contributor fields (i.e. creators or editors). These eprints are then recommitted, updating the ORCID contributor fields with the user's ORCID.

This screen will display all of the records from the user's orcid.org profile which the user has given permission to be read. Users can select which records they would like to appear by selecting the check boxes (all checkboxes are selected by default). If the record has been imported previously, the option to select the record for importing again will not be presented. Users can also filter which records appear by publication date, to help ensure only ORCID works from the relevant period are shown.

The Export to orcid.org will also appear on user profile screens, allowing admin users to export records from the repository to the user's orcid.org profile, on behalf of the repository's users.

Like the import screen, here the user may select which records they wish to export to their orcid.org profile using the checkboxes. The records presented are any of those where the user's ORCID is listed in one of the contributor fields (e.g. creator, editor, etc.). Items may also be filtered based on when they were last modified.

With ORCID Support Advance installed, the Users with an ORCID reports has been updated to include the permissions the user has granted for the repository to interact with their orcid.org profile, as well as the ORCID token expiry date.

To use the plugin, a client_id and client_secret will need to be provided. ORCID members may acquired these credentials by registering the repository as a client application at -client-application-production-trusted-party.

For non-members, a sandbox API is also provided which only gives access to ORCID details stored in the ORCID Sandbox. The Sandbox is a test website, which only sends emails to @mailinator email addresses and does not contain the records found in the Production Registry (for more info please see the Sandbox FAQ).

With the ORCID Support Advance plugin installed, the only way ORCIDs can be added to the creators table is via an automatic lookup of the user's repository profile, where their authenticated ORCID should be stored following a successful connection to orcid.org.

Similarly, when a user first connects their user profile to orcid.org and the ORCID is added to their repository user account, a user commit trigger is called which will attempt to find all of the eprint records where that user is listed as a creator, and then commit those eprints so the new ORCID is pulled through. This trigger is also found in z_orcid_support_advance.pl and will need updating to ensure the lookup for a user's eprints, based on creators_id, is using the correct field.

A new ORCID log dataset is added to the repository to store details of communications between the repository and orcid.org when users first connect their accounts. The main purpose of this dataset is twofold:

Think of a world where creativity meets process and eprints will appear, our passion for capturing memorable moments with evolving creativity is only equaled by our desire to create order and deliver a hassle free experience throughout our interaction with both the Schools and Parents we come into contact with.

The collection contains a range of research outputs including journal articles, conference contributions, working papers and higher degree theses and dissertations. Most records include a link to the published version and/or an open access full-text file. This ensures the widest possible dissemination and impact the research outputs and contributes to the growing body of research literature that is now freely available online. Find out more about Open Access for QUT Research Outputs (Including Theses) Policy.

Except where additional re-use rights are specified via the application of a Creative Commons Licence, readers may print and save electronic copies of whole papers for personal use. As with printed books and journals, attribution of authorship is essential. Any excerpts, quotations or paraphrasing should be fully referenced. The text may not be disseminated or published (in print or electronic form) without permission of the copyright owner.

QUT ePrints is running on GNU EPrints software. Anyone can access the metadata free of charge. The metadata can be harvested (via ) for purposes related to the discovery or analysis of the repository's contents. The metadata may be re-used in any medium without prior permission for not-for-profit purposes.

If you are an author, creator or copyright owner and you believe that a work that is currently available via QUT ePrints should not be in open access, please send details to epr...@qut.edu.au. The QUT Copyright Officer will review all takedown requests. If there is prima facie evidence of copyright violation then the research paper/work in question will immediately be removed from public view.

QUT ePrints is managed in accordance with the Intellectual Property Policy and Australian Copyright Law. All reasonable care is taken to avoid copyright infringements. Formal notifications in relation to copyright infringements on the QUT network should be directed to the university's designated representative in writing.

The QUT Intellectual Property Policy states that higher degree research students own the intellectual property and retain copyright in their thesis. Students grant QUT a perpetual, worldwide, royalty-free, non-exclusive licence to communicate their submitted thesis via QUT ePrints. For more information, see QUT Copyright Guide: Publishing.

3a8082e126