Re: [CODE4LIB] DSpace Issue

2015-01-16 Thread Maura Carbone
Hi! First, thanks for responding :-) I got a response on the DSpace tech list at the same time, as I got your response, and figured out the problem. I was checking the BI_PRIVATE table, which was correct, but wasn't checking the 'discoverable' field that was added to the items table in 3, and man

Re: [CODE4LIB] DSpace Issue

2015-01-15 Thread Sean Xiao Zhao
Hi Marking an item as private is controlled by the "discoverable" boolean column in the item table in the database. Can you please verify that the values of that column are not False or f? The solr indexing issue seems to be caused by empty aat/contributor fields in some of your items. See her

[CODE4LIB] DSpace Issue

2015-01-15 Thread Maura Carbone
(Apologies for Crossposting) Thought I'd try here and the DSpace-tech listserv since this is frustrating the heck out of me. I'm testing an upgrade from 3.2 to 4.2 of our DSpace install. However, upon upgrading to 4.2, almost all my items get marked as private in the WebUI (note that they are not