Hello,

The Solr search/browse indexes are populated from the database (for
metadata) and from the filter-media script (as it extracts plain text from
common formats and indexes that plain text). So, to answer your question,
all of those can affect the solr indexes. If the bitstreams do not exist,
they will not be found by the filter-media script and will not be in the
index.  Additionally, if there are metadata differences, that can affect
the index as well.  Finally, configuration differences can also affect the
index, if you've changed the configuration on one server to index different
fields, but didn't change the configuration on your demo server.

If you have more specific questions, or are noticing problems or errors in
your log files, I'd recommend posting them to our DSpace Tech Support
mailing list (https://groups.google.com/d/forum/dspace-tech).

- Tim

On Mon, Nov 26, 2018 at 8:00 AM Csaba Cerva <[email protected]> wrote:

> Hello
> We are using dspace 6.2 and realized, that there might be differences if
> we index our demo and our live version of dspace.
> The only difference between these two systems is the assetstore, the demo
> contains much more less uploaded content, but the
> database, the tomcat and dspace files, the source jar files, everything is
> copied from the live version into the demo - of course changing some demo
> specific variables, but they won't affect the indexing.
> So, my question is: can the assetstore, the real existence of the
> bitstreams(they are in the demo database too), or the filter-media script
> affect the solr indexes?
> thanx
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at https://groups.google.com/group/dspace-community.
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-community.
For more options, visit https://groups.google.com/d/optout.

Reply via email to