mirror of
https://github.com/alanorth/cgspace-notes.git
synced 2024-11-22 14:45:03 +01:00
Add notes for 2017-03-05
This commit is contained in:
parent
032d72cd05
commit
22f2d07eca
GPG Key ID:
0FB860CC9C45B1B9
@ -58,3 +58,15 @@ DirectClass CMYK
|
||||
$ identify -format '%r\n' Africa\ group\ of\ negotiators.pdf\[0\]
|
||||
DirectClass sRGB Alpha
|
||||
```
|
||||
|
||||
## 2017-03-05
|
||||
|
||||
- Look into helping developers from landportal.info with a query for items related to LAND on the REST API
|
||||
- They want something like the items that are returned by the general "LAND" query in the search interface, but we cannot do that
|
||||
- We can only return specific results for metadata fields, like:
|
||||
|
||||
```
|
||||
$ curl -s -H "accept: application/json" -H "Content-Type: application/json" -X POST "https://dspacetest.cgiar.org/rest/items/find-by-metadata-field" -d '{"key": "cg.subject.ilri","value": "LAND REFORM", "language": null}' | json_pp
|
||||
```
|
||||
|
||||
- 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!
|
||||
|
||||
@ -37,7 +37,7 @@ $ identify ~/Desktop/alc_contrastes_desafios.jpg
|
||||
|
||||
|
||||
<meta property="article:published_time" content="2017-03-01T17:08:52+02:00"/>
|
||||
<meta property="article:modified_time" content="2017-03-03T18:40:38+02:00"/>
|
||||
<meta property="article:modified_time" content="2017-03-04T01:15:47+02:00"/>
|
||||
|
||||
|
||||
|
||||
@ -94,13 +94,13 @@ $ identify ~/Desktop/alc_contrastes_desafios.jpg
|
||||
|
||||
"headline": "March, 2017",
|
||||
"url": "https://alanorth.github.io/cgspace-notes/2017-03/",
|
||||
"wordCount": "368",
|
||||
"wordCount": "465",
|
||||
|
||||
|
||||
"datePublished": "2017-03-01T17:08:52+02:00",
|
||||
|
||||
|
||||
"dateModified": "2017-03-03T18:40:38+02:00",
|
||||
"dateModified": "2017-03-04T01:15:47+02:00",
|
||||
|
||||
|
||||
"author": {
|
||||
@ -232,6 +232,21 @@ $ identify -format '%r\n' Africa\ group\ of\ negotiators.pdf\[0\]
|
||||
DirectClass sRGB Alpha
|
||||
</code></pre>
|
||||
|
||||
<h2 id="2017-03-05">2017-03-05</h2>
|
||||
|
||||
<ul>
|
||||
<li>Look into helping developers from landportal.info with a query for items related to LAND on the REST API</li>
|
||||
<li>They want something like the items that are returned by the general “LAND” query in the search interface, but we cannot do that</li>
|
||||
<li>We can only return specific results for metadata fields, like:</li>
|
||||
</ul>
|
||||
|
||||
<pre><code>$ curl -s -H "accept: application/json" -H "Content-Type: application/json" -X POST "https://dspacetest.cgiar.org/rest/items/find-by-metadata-field" -d '{"key": "cg.subject.ilri","value": "LAND REFORM", "language": null}' | json_pp
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>But there are hundreds of combinations of fields and values (like <code>dc.subject</code> and all the center subjects), and we can’t use wildcards in REST!</li>
|
||||
</ul>
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
@ -76,7 +76,22 @@
|
||||
DirectClass CMYK
|
||||
$ identify -format '%r\n' Africa\ group\ of\ negotiators.pdf\[0\]
|
||||
DirectClass sRGB Alpha
|
||||
</code></pre></description>
|
||||
</code></pre>
|
||||
|
||||
<h2 id="2017-03-05">2017-03-05</h2>
|
||||
|
||||
<ul>
|
||||
<li>Look into helping developers from landportal.info with a query for items related to LAND on the REST API</li>
|
||||
<li>They want something like the items that are returned by the general &ldquo;LAND&rdquo; query in the search interface, but we cannot do that</li>
|
||||
<li>We can only return specific results for metadata fields, like:</li>
|
||||
</ul>
|
||||
|
||||
<pre><code>$ curl -s -H &quot;accept: application/json&quot; -H &quot;Content-Type: application/json&quot; -X POST &quot;https://dspacetest.cgiar.org/rest/items/find-by-metadata-field&quot; -d '{&quot;key&quot;: &quot;cg.subject.ilri&quot;,&quot;value&quot;: &quot;LAND REFORM&quot;, &quot;language&quot;: null}' | json_pp
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>But there are hundreds of combinations of fields and values (like <code>dc.subject</code> and all the center subjects), and we can&rsquo;t use wildcards in REST!</li>
|
||||
</ul></description>
|
||||
</item>
|
||||
|
||||
<item>
|
||||
|
||||
@ -76,7 +76,22 @@
|
||||
DirectClass CMYK
|
||||
$ identify -format '%r\n' Africa\ group\ of\ negotiators.pdf\[0\]
|
||||
DirectClass sRGB Alpha
|
||||
</code></pre></description>
|
||||
</code></pre>
|
||||
|
||||
<h2 id="2017-03-05">2017-03-05</h2>
|
||||
|
||||
<ul>
|
||||
<li>Look into helping developers from landportal.info with a query for items related to LAND on the REST API</li>
|
||||
<li>They want something like the items that are returned by the general &ldquo;LAND&rdquo; query in the search interface, but we cannot do that</li>
|
||||
<li>We can only return specific results for metadata fields, like:</li>
|
||||
</ul>
|
||||
|
||||
<pre><code>$ curl -s -H &quot;accept: application/json&quot; -H &quot;Content-Type: application/json&quot; -X POST &quot;https://dspacetest.cgiar.org/rest/items/find-by-metadata-field&quot; -d '{&quot;key&quot;: &quot;cg.subject.ilri&quot;,&quot;value&quot;: &quot;LAND REFORM&quot;, &quot;language&quot;: null}' | json_pp
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>But there are hundreds of combinations of fields and values (like <code>dc.subject</code> and all the center subjects), and we can&rsquo;t use wildcards in REST!</li>
|
||||
</ul></description>
|
||||
</item>
|
||||
|
||||
<item>
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
|
||||
<url>
|
||||
<loc>https://alanorth.github.io/cgspace-notes/2017-03/</loc>
|
||||
<lastmod>2017-03-03T18:40:38+02:00</lastmod>
|
||||
<lastmod>2017-03-04T01:15:47+02:00</lastmod>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
@ -88,19 +88,19 @@
|
||||
|
||||
<url>
|
||||
<loc>https://alanorth.github.io/cgspace-notes/</loc>
|
||||
<lastmod>2017-03-03T18:40:38+02:00</lastmod>
|
||||
<lastmod>2017-03-04T01:15:47+02:00</lastmod>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
|
||||
<lastmod>2017-03-03T18:40:38+02:00</lastmod>
|
||||
<lastmod>2017-03-04T01:15:47+02:00</lastmod>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
<url>
|
||||
<loc>https://alanorth.github.io/cgspace-notes/post/</loc>
|
||||
<lastmod>2017-03-03T18:40:38+02:00</lastmod>
|
||||
<lastmod>2017-03-04T01:15:47+02:00</lastmod>
|
||||
<priority>0</priority>
|
||||
</url>
|
||||
|
||||
|
||||
@ -75,7 +75,22 @@
|
||||
DirectClass CMYK
|
||||
$ identify -format '%r\n' Africa\ group\ of\ negotiators.pdf\[0\]
|
||||
DirectClass sRGB Alpha
|
||||
</code></pre></description>
|
||||
</code></pre>
|
||||
|
||||
<h2 id="2017-03-05">2017-03-05</h2>
|
||||
|
||||
<ul>
|
||||
<li>Look into helping developers from landportal.info with a query for items related to LAND on the REST API</li>
|
||||
<li>They want something like the items that are returned by the general &ldquo;LAND&rdquo; query in the search interface, but we cannot do that</li>
|
||||
<li>We can only return specific results for metadata fields, like:</li>
|
||||
</ul>
|
||||
|
||||
<pre><code>$ curl -s -H &quot;accept: application/json&quot; -H &quot;Content-Type: application/json&quot; -X POST &quot;https://dspacetest.cgiar.org/rest/items/find-by-metadata-field&quot; -d '{&quot;key&quot;: &quot;cg.subject.ilri&quot;,&quot;value&quot;: &quot;LAND REFORM&quot;, &quot;language&quot;: null}' | json_pp
|
||||
</code></pre>
|
||||
|
||||
<ul>
|
||||
<li>But there are hundreds of combinations of fields and values (like <code>dc.subject</code> and all the center subjects), and we can&rsquo;t use wildcards in REST!</li>
|
||||
</ul></description>
|
||||
</item>
|
||||
|
||||
<item>
|
||||
|
||||
Loading…
Reference in New Issue
Block a user