EPrints Technical Mailing List Archive

Message: #07774


< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] Bazaar Update Gone Wrong - ORCID Support


> but it checks for a pre-existing field!".

This could be an issue of file-order.

EPrints will load the configuration fields alphabetically - which is why most plugins come with z_ prefixed fileds.

 

If the 'does a user orcid field exist' check happens in orcid_support.pl, at that point, there might not be an ORCID field.

If an alphabetically-later file (e.g. user_fields.pl) also defines the user orcid field, it may be this definition of the field that is actually generating the warning!

 

NB I haven't checked the above explanation - but thought it might help understanding.

 

Cheers,

John

 

 

From: eprints-tech-bounces@ecs.soton.ac.uk [mailto:eprints-tech-bounces@ecs.soton.ac.uk] On Behalf Of James Kerwin via Eprints-tech
Sent: 04 April 2019 11:04
To: eprints-tech@ecs.soton.ac.uk; Will Fyson <R.W.Fyson@soton.ac.uk>
Subject: Re: [EP-tech] Bazaar Update Gone Wrong - ORCID Support

 

Hi Will,

 

Thanks so much for the quick reply.

 

I've temporarily disabled the plugin for now. I'll stay behind this evening to make your suggested changes. That way I won't disturb our repository team any more than I already have with my ham-fisted attempts at "improving" things.

 

I managed to keep calm long enough to get the repository back up and running and then quickly ran outside for some nicotine while I pondered the problem, although I did read the section you refer to earlier on which is what had me thinking "but it checks for a pre-existing field!".

 

Anyway, thank you for your help,

James

 

On Thu, Apr 4, 2019 at 10:50 AM Will Fyson via Eprints-tech <eprints-tech@ecs.soton.ac.uk> wrote:

Hi James,

The "Duplicate field name encountered: user.orcid" error will occur if you have an ORCID field defined for your user dataset elsewhere. The ORCID Plugin attempts to add one as well, operating under the assumption that the repository doesn't yet have fields for storing ORCIDs in. It makes some attempt to try and work out if such a field is already present, but it looks like this is not as sophisticated as it needs to be.

Therefore to fix this problem rather than simply disable orcid_support.pl completely I'd recommend just commenting out the lines where it tries to add the ORCID field to the user dataset, i.e. the lines between #---Users---# (line 26) and #---Eprints---# (line 47) and then perhaps run an epadmin test (which should highlight issues such as duplicate field definitions) to see if it is ok to restart the server again.

I can't see why the "Undefined subroutine &EPrints::ORCID::Utils::get_normalised_orcid called at (eval 222) line 9." error should appear as the Bazaar plugin appears to have this file and this function. Re-enabling z_orcid_support.pl may well fix this however, once the previous fix is in place.

Many thanks,

Will

 


From: James Kerwin Via Eprints-tech <eprints-tech@ecs.soton.ac.uk> [eprints-tech@ecs.soton.ac.uk] Sent: 04 April 2019 10:39 To: Eprints-tech <eprints-tech@ecs.soton.ac.uk> Subject: [EP-tech] Bazaar Update Gone Wrong - ORCID Support

Hello again,

 

I have a follow-up question to me earlier one.

 

I attempted to upgrade the orcid support plugin to V1.7. I got an error page saying:

 

Duplicate field name encountered: user.orcid

 

After restarting the server the repository went down. I changed all the following in the orcid_zupport.pl script to:

 

#Enable the plugin!

$c->{plugins}{"Orcid"}{params}{disable} = 1;

$c->{plugins}{"Screen::Report::Orcid::UserOrcid"}{params}{disable} = 1;

$c->{plugins}{"Screen::Report::Orcid::AllUsersOrcid"}{params}{disable} = 1;

$c->{plugins}{"Screen::Report::Orcid::CreatorsOrcid"}{params}{disable} = 1;

$c->{plugins}{"Export::Report::CSV::CreatorsOrcid"}{params}{disable} = 1;

 

In order to disable the plugin. Still no signs of life from the server. Changed the name of the script to end in .".pl.broken". Restarted the server and got life, but on the staff view of an eprint I get an error:

 

Undefined subroutine &EPrints::ORCID::Utils::get_normalised_orcid called at (eval 222) line 9.

 

Does anybody know what caused this and how I fix it?

 

Thanks,

James 

 

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/
*** EPrints developers Forum: http://forum.eprints.org/

 

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: http://www.eprints.org/tech.php/
*** EPrints community wiki: http://wiki.eprints.org/
*** EPrints developers Forum: http://forum.eprints.org/