| Apache Solr has an admin interface available. It’s typically available at the solr host on port 8983. You can browse the schema as well as run queries directly.
Does you Solr instance have any errors in the logs?
Or perhaps the old schema is being loaded instead of the new schema?
-Andrew Dear Mark,
I'm a bit lost at this point. I can see the old and the new schema.xml in the solr/oai/conf/ folder. The new indeed has the field item.hasbitstream. (The newer one is called schema.xml so I guess this is the one being used.) I tried restarting the solr service, rebuilding the oai core with no luck so far. I still keep getting the same error.
Thanks, Evelin
On Mon, Jan 13, 2025 at 12:04:26PM +0000, Evelin Bányai wrote:
> We have upgraded our DSpace from 7.2 to 8.0 near the end of last year. We followed the guide on this site https://wiki.lyrasis.org/display/DSDOC8x/Upgrading+DSpace
>
> The upgrade seemed to be successful and so far we have encountered only 2 issues. One of is them running the dspace oai import script fails with an error.
>
> Our Environment information:
> DSpace version: 8.0
> Java: 17.0.13+11-Ubuntu-2ubuntu124.04
> Node: v20.18.1
> Tomcat: None. We are using the runnable JAR
>
> See the output running the following command below: dspace oai import
> Standard Commons Logging discovery in action with spring-jcl: please remove commons-logging.jar from classpath in order to avoid potential conflicts
> OAI 2.0 manager action started
> There are no indexed documents, using full import.
> Full import
> Total: 288 items
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error from server at http://10.128.120.16:8983/solr/oai: ERROR: [doc=123456789/339] unknown field 'item.hasbitstream'
>
> I can see that there is an unknown field called "item.hasbitstream'", but I'm not sure where it's missing from exactly. The item in the error is most probably the first on its list. So probably the problem is not with this item only?
It seems that the field is not defined in the Solr schema for the
'oai' core. That field was added on 2023-12-12 to support RIOXX. The
first thing I would check is whether the core's schema was completely
updated to DSpace 8.0 during the upgrade.
If you need to modify the schema, you should then rebuild the OAI
core: 'bin/dspace oai import -c'
--
Mark H. Wood
Lead Technology Analyst
University Library
Indiana University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
library.indianapolis.iu.edu
--
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/fe5daee9-f032-4cc9-a1f7-c723c6f660ebn%40googlegroups.com.
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/D60C1165-961D-4E99-894D-C07F1207D83F%40gmail.com.
|
