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 many
of my items had a null value. Just to note, we actually have been
using Solr on 3 without an issue with searching or discovery
(everything would show up), so if someone is going from 3 to 4, keep
this in mind!
The last error is now moot; as solr is correctly indexing for browse
and search oracle no longer needs the view tables it was having
On Thu, Jan 15, 2015 at 4:00 PM, Sean Xiao Zhao
<[log in to unmask]> wrote:
> 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 here: https://github.com/DSpace/DSpace/blob/master/dspace-api/src/main/java/org/dspace/browse/SolrBrowseCreateDAO.java#L160
> As for the last error, could you please verify that the ORA-00942 table exists?
Digital Initiatives Librarian
Library and Technology Services
415 South Street, (MS 017/P.O. Box 549110)
Waltham, MA 02454-9110
email: [log in to unmask]