Add notes for 2018-02-07

content/post/2018-02.md

@@ -130,3 +130,12 @@ Tue Feb  6 09:30:32 UTC 2018
 - Also, this will mean that when a search bot comes along and hammers the XMLUI, the REST and OAI applications will be fine
 - I'm not actually sure if the Solr web application uses the database though, so I'll have to check later and remove it if necessary
 - I deployed the changes on DSpace Test only for now, so I will monitor and make them on CGSpace later this week
+
+## 2018-02-07
+
+- Abenet wrote to ask a question about the ORCiD lookup not working for one CIAT user on CGSpace
+- I tried on DSpace Test and indeed the lookup just doesn't work!
+- The ORCiD code in DSpace appears to be using `http://pub.orcid.org/`, but when I go there in the browser it redirects me to `https://pub.orcid.org/v2.0/`
+- According to [the announcement](https://groups.google.com/forum/#!topic/orcid-api-users/qfg-HwAB1bk) the v1 API was moved from `http://pub.orcid.org/` to `https://pub.orcid.org/v1.2` until March 1st when it will be discontinued for good
+- But the old URL is hard coded in DSpace and it doesn't work anyways, because it currently redirects you to `https://pub.orcid.org/v2.0/v1.2`
+- So I guess we have to disable that shit once and for all and switch to a controlled vocabulary