Dear Tom Desair,
Thanks for your valuable suggestion, Now we are able to fix the issue and
now it's index full data.
we have followed 2nd option
*ignore authorities for the browse index: *Add these lines to
config/modules/discovery.cfg
discovery.browse.authority.ignore-prefered.author = true
While executing following query it's shows 5712 records,
select distinct dspace_object from resourcepolicy where eperson_id is not
null
we have some collections that don't have any policy but still some records
not index.
After Tom suggestion about "enable authority control for
It's seem that error at line 72 in SolrServiceResourceRestrictionPlugin.java,
so please check the policy of these data:
select * from metadatavalue where dspace_object_id in (select distinct
dspace_object from resourcepolicy where eperson_id is not null)
and you can add READ policy for
Hi Bhavesh,
It looks like you have dc.contributor.author metadata values for which the
authority column has a value. But your dspace.cfg file doesn't contain any
valid authority configuration for dc.contributor.author.
That means you have two options:
1. *Configure authority control for
Dear Tom Desair,
We have followed the instruction as per your reply, index command was
successfully executed, but the count remain same.
we see into dspace.log file (dspace.log.2017-05-03), it's around 26 MB, so
I have taken some of the lines (that is having error while executing the
command)
DSpace 6.0 has some known memory issue so it might be that the indexing
process is stopped before it could complete. These will be fixed in DSpace
6.1.
For now, can you try this:
> $ export JAVA_OPTS="-Xmx4G -Dfile.encoding=UTF-8"
> $ bin/dspace index-discovery -bf
Do you see any errors in the
Dear Tom Desair,
Both counts are different,
SQL Query in database: 18072
Through Solr: 17058
Through Solr:
---
{
"responseHeader":{
"status":0,
"QTime":1,
"params":{
"q":"search.resourcetype:2",
"indent":"true",
"rows":"0",
Hi Bhavesh,
To check the number of items in the database that need to be indexed,
execute:
> select count(*) from item where in_archive = true or withdrawn = true;
Then compare this to the number of items that are in the discovery index:
> curl "
>
Thanks for your reply, we did it as per your suggestion but there is no
change in number.
We have cross checked in database (postgresql), in table: *metadatavalue*
we set the condition with itemtype and count, it shows the perfect number
of records but it when we index, it doesn't show all the
Please check anonymous authorization of these data and try index-discovery
-b -f
Vào 20:48:48 UTC+7 Thứ Hai, ngày 01 tháng 5 năm 2017, Bhavesh Patel đã viết:
>
> Dear all,
>
> we have upgraded DSpace 5 to DSpace 6, we have imported the database and
> assesstore but when we run index-discovery
10 matches
Mail list logo