Hi Jose,

When DSpace is still indexing content, site behavior with regards to 
permissions may have unexpected results.  So, it's really hard to debug any 
issues until the indexer completes.  It's possible the behavior you are seeing 
is either because the indexer hasn't completed, or it could be cached results.  
So, honestly, I wouldn't get worried about odd behaviors unless you still seem 
them after the indexing is completed (and you've cleared your cache if you are 
using XMLUI).

If you stop DSpace while it's indexing, then (IIRC) the indexer should restart 
(from the beginning) the next time you restart DSpace.  However, if for some 
reason it does not, you can always run the indexer manually.  In any case, 
stopping the indexer while it is running is OK, but you would need to start it 
over to ensure it has a full index of all your content.

Tim
________________________________
From: [email protected] <[email protected]> on behalf of 
Jose Blanco <[email protected]>
Sent: Thursday, July 30, 2020 12:29 PM
To: DSpace Technical Support <[email protected]>
Subject: [dspace-tech] release question.

I'm in the middle of releasing to production and I'm running the full index.

I can see that if I am not logged in as myself ( admin ), the number of items 
keeps increasing as expected when I do a title browse.

But if I login, I get no items, or if I go to the home page there are no items 
after login in.  I'm assuming  this is because I'm an admin, but am not sure 
what is happening.  I had a user who has no roles in the system login, and he 
is seeing the same thing as when not logged in ( which is expected ).  Is this 
what I should expect for admins? Is this because the indexer has not completed?

Also, I see I have to make a code change, for some other bug I just discovered. 
What will happen to the indexer if I do a release while the indexing is going 
on?  Any suggestions?

Thank you.  Jose

--
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 Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
[email protected]<mailto:[email protected]>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-u%2B09_LMkGxX9Kg39agDmtKFO2%3DpXeMLs9VzJXfL1oPLw%40mail.gmail.com<https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-u%2B09_LMkGxX9Kg39agDmtKFO2%3DpXeMLs9VzJXfL1oPLw%40mail.gmail.com?utm_medium=email&utm_source=footer>.

-- 
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 Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/DM5PR2201MB114844131A5A9CA0E0B05D8DED710%40DM5PR2201MB1148.namprd22.prod.outlook.com.

Reply via email to