EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #09387

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

AW: [EP-tech] ORCID Support Advance: encoding

CAUTION: This e-mail originated outside the University of Southampton.

Hi Ed,

 

thanks for taking care of this issue.

 

All the best

Volker

 

Von: eprints-tech-request@ecs.soton.ac.uk <eprints-tech-request@ecs.soton.ac.uk> Im Auftrag von Edward Oakley
Gesendet: Montag, 4. September 2023 16:18
An: 'eprints-tech@ecs.soton.ac.uk' <eprints-tech@ecs.soton.ac.uk>
Betreff: Re: [EP-tech] ORCID Support Advance: encoding

 

Hi Volker,

 

Thanks for reporting this issue. A github issue has been created to track the problem... https://github.com/eprints/orcid_support_advance/issues/74

 

A quick fix is to encode the config file as utf8 and remove the encoding within the util file, as seen here... https://github.com/eprints/orcid_support_advance/commit/8da658a11d0662fed5222a78ed43cd99dd64fba7

 

However, this is not a good solution for all customers. We will be looking into the correct way to deal with this.

 

You can remove the incorrect 

 

Kind Regards, 

Ed

 

From: eprints-tech-request@ecs.soton.ac.uk <eprints-tech-request@ecs.soton.ac.uk> on behalf of Schallehn, Volker <volker.schallehn@ub.uni-muenchen.de>
Sent: 24 August 2023 11:54
To: 'eprints-tech@ecs.soton.ac.uk' <eprints-tech@ecs.soton.ac.uk>
Subject: [EP-tech] ORCID Support Advance: encoding

 

CAUTION: This e-mail originated outside the University of Southampton.

CAUTION: This e-mail originated outside the University of Southampton.

Hi all,

 

we have just installed he latest version of “orcid support advance” from github. It works so far, however the umlauts in the name of the institution defined in the z_orcid_support_advance.pl file under $c->{"plugins"}->{"Event::OrcidSync"}->{"params"}->{"affiliation"} are not correctly transferred to the Employment section of ORCID. The umlauts are correctly represented in ORCID only if the z_orcid_support_advance.pl file is saved in ANSI format. Is this a bug or a feature? We would be glad to receive any hints about this behaviour.

 

Thanks in advance

Volker Schallehn