Do we really want to urlencode() DOIs?

Are you responsible for making OJS work -- installing, upgrading, migrating or troubleshooting? Do you think you've found a bug? Post in this forum.

Moderators: jmacgreg, btbell, michael, bdgregg, barbarah, asmecher

Forum rules
The Public Knowledge Project Support Forum is moving to

This forum will be maintained permanently as an archived historical resource, but all new questions should be added to the new forum. Questions will no longer be monitored on this old forum after March 30, 2015.
Posts: 111
Joined: Wed Jul 25, 2012 2:56 pm
Location: Munich, Germany

Do we really want to urlencode() DOIs?

Postby springday » Mon Mar 25, 2013 9:10 am

Every DOI contains a slash, separating the prefix (e.g. 10.2378) from the suffix (arbitrarily assigned by the publisher). The DOI pubID-plugin's getResolvingURL()-function uses urlencode() on all DOIs, resulting in string like this one:

Code: Select all

For links that doesn't matter, they'll certainly resolve that way. However, I'm also using this string for display and that just doesn't look right. It should be

Code: Select all

Is there any disadvantage to change the's line #240 into:

Code: Select all

      return ''.$pubId;

Best regards,
Kai Weber

Posts: 4191
Joined: Tue Feb 14, 2006 10:50 am

Re: Do we really want to urlencode() DOIs?

Postby jmacgreg » Tue Apr 09, 2013 12:53 pm

Hi Kai,

I just encountered this issue myself and reported it: Please feel free to CC yourself to that report for future updates. The developers should have a quick response.


Return to “OJS Technical Support”

Who is online

Users browsing this forum: No registered users and 1 guest