Update notes for 2018-02-20

content/post/2018-02.md

@@ -717,3 +717,40 @@ $ cat ~/src/git/DSpace/dspace/config/controlled-vocabularies/cg-creator-id.xml O
 
 - I updated the `resolve-orcids.py` to use the "credit-name" if it exists in a profile, falling back to "given-names" + "family-name"
 - Also, I added color coded output to the debug messages and added a "quiet" mode that supresses the normal behavior of printing results to the screen
+- I'm using this as the test input for `resolve-orcids.py`:
+
+```
+$ cat orcid-test-values.txt 
+# valid identifier with 'given-names' and 'family-name'
+0000-0001-5019-1368
+
+# duplicate identifier
+0000-0001-5019-1368 
+
+# invalid identifier
+0000-0001-9634-19580
+
+# has a 'credit-name' value we should prefer
+0000-0002-1735-7458
+
+# has a blank 'credit-name' value
+0000-0001-5199-5528
+
+# has a null 'name' object
+0000-0002-1300-3636
+
+# has a null 'family-name' value
+0000-0001-9634-1958
+
+# missing ORCID identifier
+0000-0003-4221-3214
+```
+
+- Help debug issues with Altmetric badges again, it looks like Altmetric is all kinds of fucked up
+- Last week I pointed out that they were tracking Handles from our test server
+- Now, their API is responding with content that is marked as content-type JSON but is not valid JSON
+- For example, this item: https://cgspace.cgiar.org/handle/10568/83320
+- The Altmetric JavaScript builds the following API call: https://api.altmetric.com/v1/handle/10568/83320?callback=_altmetric.embed_callback&domain=cgspace.cgiar.org&key=3c130976ca2b8f2e88f8377633751ba1&cache_until=13-20
+- The response body is *not* JSON
+- To contrast, the following bare API call without query parameters is valid JSON: https://api.altmetric.com/v1/handle/10568/83320
+- I told them that it's their JavaScript that is fucked up