Update notes for 2019-04-28

content/posts/2019-04.md

@@ -979,6 +979,7 @@ dspace=# SELECT * FROM item WHERE item_id=74648;
 (1 row)
 ```
 
+- I tried to delete the item in the web interface, and it seems successful, but I can still access the item in the admin interface, and nothing changes in PostgreSQL
 - Meet with CodeObia to see progress on AReS version 2
 - Marissa Van Epp asked me to add a few new metadata values to their Phase II Project Tags field (cg.identifier.ccafsprojectpii)
   - I created a [pull request](https://github.com/ilri/DSpace/pull/420) for it and will do it the next time I run updates on CGSpace
@@ -994,4 +995,25 @@ dspacetest=# # \copy (select distinct text_value, count(*) as count from metadat
 COPY 65752
 ```
 
+## 2019-04-28
+
+- Still trying to figure out the issue with the items that cause the REST API's `/items/find-by-metadata-value` endpoint to throw an exception
+  - I made the item private in the UI and then I see in the UI and PostgreSQL that it is no longer discoverable:
+
+```
+dspace=# SELECT * FROM item WHERE item_id=74648;
+ item_id | submitter_id | in_archive | withdrawn |       last_modified        | owning_collection | discoverable 
+---------+--------------+------------+-----------+----------------------------+-------------------+--------------
+   74648 |          113 | f          | f         | 2019-04-28 08:48:52.114-07 |                   | f
+(1 row)
+```
+
+- And I tried the `curl` command from above again, but I still get the HTTP 401 and and the same error in the DSpace log:
+
+```
+2019-04-28 08:53:07,170 ERROR org.dspace.rest.ItemsResource @ User(anonymous) has not permission to read item(id=74648)!
+```
+
+- I even tried to "expunge" the item using an [action in CSV](https://wiki.duraspace.org/display/DSDOC5x/Batch+Metadata+Editing#BatchMetadataEditing-Performing'actions'onitems), and it said "EXPUNGED!" but the item is still there...
+
 <!-- vim: set sw=2 ts=2: -->

docs/2019-04/index.html

@@ -38,7 +38,7 @@ $ ./delete-metadata-values.py -i /tmp/2019-02-21-delete-1-region.csv -db dspace
 <meta property="og:type" content="article" />
 <meta property="og:url" content="https://alanorth.github.io/cgspace-notes/2019-04/" />
 <meta property="article:published_time" content="2019-04-01T09:00:43&#43;03:00"/>
-<meta property="article:modified_time" content="2019-04-25T23:10:38&#43;03:00"/>
+<meta property="article:modified_time" content="2019-04-26T12:16:02&#43;03:00"/>
 
 <meta name="twitter:card" content="summary"/>
 <meta name="twitter:title" content="April, 2019"/>
@@ -81,9 +81,9 @@ $ ./delete-metadata-values.py -i /tmp/2019-02-21-delete-1-region.csv -db dspace
   "@type": "BlogPosting",
   "headline": "April, 2019",
   "url": "https:\/\/alanorth.github.io\/cgspace-notes\/2019-04\/",
-  "wordCount": "6364",
+  "wordCount": "6534",
   "datePublished": "2019-04-01T09:00:43\x2b03:00",
-  "dateModified": "2019-04-25T23:10:38\x2b03:00",
+  "dateModified": "2019-04-26T12:16:02\x2b03:00",
   "author": {
     "@type": "Person",
     "name": "Alan Orth"
@@ -1369,6 +1369,7 @@ $ curl -f -H &quot;rest-dspace-token: b43d41a6-5ac1-455d-b49a-616b8debc25b&quot;
 </code></pre>
 
 <ul>
+<li>I tried to delete the item in the web interface, and it seems successful, but I can still access the item in the admin interface, and nothing changes in PostgreSQL</li>
 <li>Meet with CodeObia to see progress on AReS version 2</li>
 <li>Marissa Van Epp asked me to add a few new metadata values to their Phase II Project Tags field (cg.identifier.ccafsprojectpii)
 
@@ -1389,6 +1390,34 @@ $ curl -f -H &quot;rest-dspace-token: b43d41a6-5ac1-455d-b49a-616b8debc25b&quot;
 COPY 65752
 </code></pre>
 
+<h2 id="2019-04-28">2019-04-28</h2>
+
+<ul>
+<li>Still trying to figure out the issue with the items that cause the REST API&rsquo;s <code>/items/find-by-metadata-value</code> endpoint to throw an exception
+
+<ul>
+<li>I made the item private in the UI and then I see in the UI and PostgreSQL that it is no longer discoverable:</li>
+</ul></li>
+</ul>
+
+<pre><code>dspace=# SELECT * FROM item WHERE item_id=74648;
+ item_id | submitter_id | in_archive | withdrawn |       last_modified        | owning_collection | discoverable 
+---------+--------------+------------+-----------+----------------------------+-------------------+--------------
+   74648 |          113 | f          | f         | 2019-04-28 08:48:52.114-07 |                   | f
+(1 row)
+</code></pre>
+
+<ul>
+<li>And I tried the <code>curl</code> command from above again, but I still get the HTTP 401 and and the same error in the DSpace log:</li>
+</ul>
+
+<pre><code>2019-04-28 08:53:07,170 ERROR org.dspace.rest.ItemsResource @ User(anonymous) has not permission to read item(id=74648)!
+</code></pre>
+
+<ul>
+<li>I even tried to &ldquo;expunge&rdquo; the item using an <a href="https://wiki.duraspace.org/display/DSDOC5x/Batch+Metadata+Editing#BatchMetadataEditing-Performing'actions'onitems">action in CSV</a>, and it said &ldquo;EXPUNGED!&rdquo; but the item is still there&hellip;</li>
+</ul>
+
 <!-- vim: set sw=2 ts=2: -->
 
   

docs/sitemap.xml

@@ -4,30 +4,30 @@
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/2019-04/</loc>
-    <lastmod>2019-04-25T23:10:38+03:00</lastmod>
+    <lastmod>2019-04-26T12:16:02+03:00</lastmod>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/</loc>
-    <lastmod>2019-04-26T12:13:02+03:00</lastmod>
+    <lastmod>2019-04-26T12:16:02+03:00</lastmod>
     <priority>0</priority>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/tags/notes/</loc>
-    <lastmod>2019-04-26T12:13:02+03:00</lastmod>
+    <lastmod>2019-04-26T12:16:02+03:00</lastmod>
     <priority>0</priority>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/posts/</loc>
-    <lastmod>2019-04-26T12:13:02+03:00</lastmod>
+    <lastmod>2019-04-26T12:16:02+03:00</lastmod>
     <priority>0</priority>
   </url>
   
   <url>
     <loc>https://alanorth.github.io/cgspace-notes/tags/</loc>
-    <lastmod>2019-04-26T12:13:02+03:00</lastmod>
+    <lastmod>2019-04-26T12:16:02+03:00</lastmod>
     <priority>0</priority>
   </url>