diff --git a/content/post/2017-03.md b/content/post/2017-03.md index 1c9c512ee..98b0704c9 100644 --- a/content/post/2017-03.md +++ b/content/post/2017-03.md @@ -59,6 +59,12 @@ $ identify -format '%r\n' Africa\ group\ of\ negotiators.pdf\[0\] DirectClass sRGB Alpha ``` +## 2017-03-04 + +- Spent more time looking at the ImageMagick CMYK issue +- The `default_cmyk.icc` and `default_rgb.icc` files are both part of the Ghostscript GPL distribution, but according to DSpace's `LICENSES_THIRD_PARTY` file, DSpace doesn't allow distribution of dependencies that are licensed solely under the GPL +- So this issue is kinda pointless now, as the ICC profiles are absolutely necessary to make a meaningful CMYK→sRGB conversion + ## 2017-03-05 - Look into helping developers from landportal.info with a query for items related to LAND on the REST API @@ -70,3 +76,42 @@ $ curl -s -H "accept: application/json" -H "Content-Type: application/json" -X P ``` - But there are hundreds of combinations of fields and values (like `dc.subject` and all the center subjects), and we can't use wildcards in REST! +- Reading about enabling multiple handle prefixes in DSpace +- There is a mailing list thread from 2011 about it: http://dspace.2283337.n4.nabble.com/Multiple-handle-prefixes-merged-DSpace-instances-td3427192.html +- And a comment from Atmire's Bram about it on the DSpace wiki: https://wiki.duraspace.org/display/DSDOC5x/Installing+DSpace?focusedCommentId=78163296#comment-78163296 +- Bram mentions an undocumented configuration option `handle.plugin.checknameauthority`, but I noticed another one in `dspace.cfg`: + +``` +# List any additional prefixes that need to be managed by this handle server +# (as for examle handle prefix coming from old dspace repository merged in +# that repository) +# handle.additional.prefixes = prefix1[, prefix2] +``` + +- Because of this I noticed that our Handle server's `config.dct` was potentially misconfigured! +- We had some default values still present: + +``` +"300:0.NA/YOUR_NAMING_AUTHORITY" +``` + +- I've changed them to the following and restarted the handle server: + +``` +"300:0.NA/10568" +``` + +- In looking at all the configs I just noticed that we are not providing a DOI in the Google-specific metadata crosswalk +- From `dspace/config/crosswalks/google-metadata.properties`: + +``` +google.citation_doi = cg.identifier.doi +``` + +- This works, and makes DSpace output the following metadata on the item view page: + +``` + +``` + +- Submitted and merged pull request for this: https://github.com/ilri/DSpace/pull/305 diff --git a/public/2017-03/index.html b/public/2017-03/index.html index 00a6c2ab9..605f047a9 100644 --- a/public/2017-03/index.html +++ b/public/2017-03/index.html @@ -37,7 +37,7 @@ $ identify ~/Desktop/alc_contrastes_desafios.jpg - + @@ -94,13 +94,13 @@ $ identify ~/Desktop/alc_contrastes_desafios.jpg "headline": "March, 2017", "url": "https://alanorth.github.io/cgspace-notes/2017-03/", - "wordCount": "465", + "wordCount": "692", "datePublished": "2017-03-01T17:08:52+02:00", - "dateModified": "2017-03-04T01:15:47+02:00", + "dateModified": "2017-03-05T12:39:09+02:00", "author": { @@ -232,6 +232,14 @@ $ identify -format '%r\n' Africa\ group\ of\ negotiators.pdf\[0\] DirectClass sRGB Alpha +

2017-03-04

+ + +

2017-03-05