ORCiDs should be compiled to https rather than http when auto-generating annotations

[matentzn]

Currently, when setting ORCID to the numeric code representing your orcid, Protege will translate that value to the ORCiD IRI with http rather than https, which seems to be what is recommended:

https://orcid.org/0000-0002-7356-1779

[matentzn]

@matthewhorridge

Would be good to get this in, as this is part of our Metadata strategy for the future..

[cthoyt]

Relevant line of code to change:

protege/protege-editor-owl/src/main/java/org/protege/editor/owl/model/user/Orcid.java

Line 19 in 8cd4719

public static final String ORCID_URI_PREFIX = "http://orcid.org/";

[matentzn]

@hkir-dev could you make this PR perhaps?

[cthoyt]

I'll do it if protege accepts external PRs

[matentzn]

It does, go ahead then :) Thanks @cthoyt

[matentzn]

Tag me in PR as well

[cthoyt]

@matentzn haven't got any feedback on #1053, it looks like Protege hasn't been updated for a year... is this project dead?

[matentzn]

There are no primary funds for protege desktop anymore, but @matthewhorridge keeps it going. He will probably merge all of the open PRs and do some minor fixes (migrate to latest 4,x OWLAPI) at some point this month. See ongoing discussion in OBO slack protege channel.

[matthewhorridge]

@cthoyt the project isn't dead... @matentzn is correct in that there is no primary funding at the moment. I'll get to the PR asap.

[dickersonlj]

Is there a way to receive these updates without subscribing to the OBO Slack? Is that where most Protégé updates are posted? Thank you. From: Nico Matentzoglu ***@***.***> Sent: Wednesday, May 4, 2022 6:39 AM To: protegeproject/protege ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [protegeproject/protege] ORCiDs should be compiled to https rather than http when auto-generating annotations (Issue #1045) CAUTION EXTERNAL EMAIL: Do not click on any links or open any attachments unless you trust the sender and/or know the content is safe. If you are suspicious of the e-mail, click on the Report Suspicious Emails button. There are no primary funds for protege desktop anymore, but @matthewhorridge<https://urldefense.com/v3/__https:/github.com/matthewhorridge__;!!E4HZMw!FRXvpOD7PY-HPQgkJKSRMV1JYViPOMLcHAY3Exk6mxT3wDJYVh8rrd8nEEgWeVl5V0GVUJiPjftaq0Pl7NFaOGvFKI4$> keeps it going. He will probably merge all of the open PRs and do some minor fixes (migrate to latest 4,x OWLAPI) at some point this month. See ongoing discussion in OBO slack protege channel. — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/protegeproject/protege/issues/1045*issuecomment-1117164258__;Iw!!E4HZMw!FRXvpOD7PY-HPQgkJKSRMV1JYViPOMLcHAY3Exk6mxT3wDJYVh8rrd8nEEgWeVl5V0GVUJiPjftaq0Pl7NFa2o9oMEk$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AMK2UPXW2LUX4TTJUL33ENDVIJHURANCNFSM5OVZW7OQ__;!!E4HZMw!FRXvpOD7PY-HPQgkJKSRMV1JYViPOMLcHAY3Exk6mxT3wDJYVh8rrd8nEEgWeVl5V0GVUJiPjftaq0Pl7NFaf1Ocp9I$>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>

[matentzn]

@dickersonlj

I would not say there is a lot of updating going on in the OBO slack - its more like a support group for Protege users in our community. Unfortunately, the only way to be really sure you stay updated with everything is by subscribing to the issue tracker here! Something like a monthly digest to obo-tools or obo-discuss mailinglist (or protege mailing list!) would be great, but I doubt there is any funding right now to do such reporting - maybe I am wrong though (@matthewhorridge)