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: -->