ORCID is "http://" instead of "https://"

Software Support
1

In some older installations of OJS, author ORCID identifiers may have been stored in the database using the http:// prefix instead of https://.

This value cannot be modified through the OJS interface or from the author profile, so the only way to fix it is by running an SQL query directly on the database.

Translating http to https in ORCID iDs transitioning to OJS 3.1.2.0 from 2.4.5.0
2

To detect the cases and fix it, you can follow these steps:

1. Detecting affected records

To check whether there are any ORCID entries stored with http://,

Use the following query to count coincidences per journal:

SELECT
  j.path AS journalTag,
  (
    SELECT COUNT(*)
    FROM `author_settings`
    WHERE `setting_name` = 'orcid'
      AND `setting_value` LIKE '%http://%'
  ) AS orcid_http_count
FROM journals j;

If you want to list the affected records and see the corrected values, use:

SELECT
  j.path AS journalTag,
  (
    SELECT COUNT(*)
    FROM `author_settings`
    WHERE `setting_name` = 'orcid'
      AND `setting_value` LIKE '%http://%'
  ) AS orcid_http_count
FROM journals j;

2. Applying the fix

Once you have confirmed the results, you can run the following query to update all records:

UPDATE author_settings
SET setting_value = REPLACE(setting_value, 'http://', 'https://')
WHERE setting_name = 'orcid'
  AND setting_value LIKE 'http://%';

After applying this change, all ORCID identifiers will use the standard https:// format, ensuring compatibility with current ORCID authentication and validation systems.

WARNING/DISCLAIMER

Before executing the update, make a full backup of the database. This operation is permanent and directly modifies author metadata.

Same approach can be used to modify other fields still referring http:// protocol, but please test in deeply before any change.

3 Likes