[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



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 at ecs.soton.ac.uk><mailto:eprints-tech at ecs.soton.ac.uk> [eprints-tech at ecs.soton.ac.uk<mailto:eprints-tech at ecs.soton.ac.uk>] Sent: 04 April 2019 10:39 To: Eprints-tech <eprints-tech at ecs.soton.ac.uk><mailto:eprints-tech at 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<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Forcid_zupport.pl%2F&data=01%7C01%7C%7C107b81e7d39249b6e95c08d6b8e2eae0%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=5yvX6ptrIlgi7SN9GEnjxFBZAIpY7UgleTMYLICjS%2FY%3D&reserved=0> 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/<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&data=01%7C01%7C%7C107b81e7d39249b6e95c08d6b8e2eae0%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=ARqa2OTjnZd%2BzZ6HDFv1gCgHYFYCpeLJsuQI4bMYza4%3D&reserved=0>
*** EPrints community wiki: http://wiki.eprints.org/<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.eprints.org%2F&data=01%7C01%7C%7C107b81e7d39249b6e95c08d6b8e2eae0%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=874gAzz%2BbitOOcb479tlt3%2BIAhT%2FWf1dg3CBAu4U5L8%3D&reserved=0>
*** EPrints developers Forum: http://forum.eprints.org/<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fforum.eprints.org%2F&data=01%7C01%7C%7C107b81e7d39249b6e95c08d6b8e2eae0%7C4a5378f929f44d3ebe89669d03ada9d8%7C0&sdata=pTfLP44F23c8qJII%2FCh%2BeWKd%2Bofpyjv0Uo9u1wgk%2FFk%3D&reserved=0>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/attachments/20190404/2972da0e/attachment-0001.html