You might try running ./dspace index-init to blow away and rebuild the whole browse index.  In general the choice of withdraw vs delete is a question of if you want to retain the item and provide a tombstone for the item to users over the long term.  If you do want that tombstone, withdraw is best, if you just want the item gone permanently, then delete is best. The collection delete problem seems like a possible bug in browse.


On Wed, Jun 29, 2011 at 11:02 AM, Isaak, David C <David.C.Isaak@kpchr.org> wrote:

I have a specific problem and a general question regarding best practices.

Through the Admin UI, I recently deleted a collection to get rid of the collection and its constituent items and bitstreams.  The items were successfully removed, but links in the author browse index persist.  When I click on a link, I get the message "Sorry, there are no results for this browse."  I have run indexupdate, but the problem persists.  Do I need to stop Tomcat and rebuild the indexes every time an item is deleted?  That solution is less than ideal as I am a repository manager and do not have access to Tomcat.

Generally speaking, when an item is no longer needed as part of the repository, is it better to delete items or withdrawal them?

We are running DSpace 1.7.1 on a windows server.
We have Discovery turned on and the Discovery facets and filters do update correctly when an item is deleted.

Thanks in advance,

David Isaak
Digital Projects Librarian
Kaiser Permanente Center for Health Research
3800 N. Interstate Ave. Portland, OR 97227
503.335.2437 (tie-line 60-2437)
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
DSpace-tech mailing list

Mark R. Diggory
@mire - www.atmire.com
2888 Loker Avenue East - Suite 305 - Carlsbad - CA - 92010
Esperantolaan 4 - Heverlee 3001 - Belgium