Ghost Item in Community

[Donald Bynum]

I have a collection which did not have the BITSREAM_READ authorization policy associated with it (my fault, I was testing an idea - seemingly a bad one).  I attempted to create a new item and an associated bitstream.  The submission failed (of course, because of the missing policy).  However, a "ghost" item for that errant item is listed in the Community view.  It is not listed in the attempted Collection.  I'd like to get rid of this ghost item, but there seems to be no way to do that from the control panel.  If I look at the data in the database, this ITEM is not associated with any COLLECTION, but there are various metatdata which are associated with the "ghost".  I could go into the database and delete the raw data (ITEM, ITEM2BUNDLE, BUNDLE, BUNDLE2BITSTREAM, BITSTREAM and METADATAVALUE).  Any advice on this and any potential issues which I might create by doing the database delete would be much appreciated.

Regards,

Don.

[Claudia Jürgen]

Hello Donald,

with which Version and which UI did you get this behaviour?
I tried to reproduce it with 5.6 JSPUI and nothing is displayed in
community view.

There is an error and a stub item is created.
This item got no owning_collection in the item table and is not in_archive.
But it does not show up in the community view.

When you log in as admin -> Administer -> Content -> Items
you got no possibility to delete the item (due to the missing
owning_collection) only to make it private.

One possibilty with little db manipulation would be to add an
owning_collection in the item table directly and then withdraw/delete
the item via the UI.

Hope this helps

Claudia Jürgen

--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
claudia...@tu-dortmund.de
www.ub.tu-dortmund.de

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform (mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is solely intended for the recipient. If you are not the intended recipient of this e-mail please contact the sender and delete this message. Thank you. Without prejudice of e-mail correspondence, our statements are only legally binding when they are made in the conventional written form (with personal signature) or when such documents are sent by fax.

[Donald Bynum]

Sorry, forgot to note that I am running Dspace 5 with XMLUI and Oracle

--


You received this message because you are subscribed to a topic in the Google Groups "DSpace Technical Support" group.


To unsubscribe from this topic, visit https://groups.google.com/d/topic/dspace-tech/c_ZU5XneO7A/unsubscribe.


To unsubscribe from this group and all its topics, send an email to dspace-tech...@googlegroups.com.


To post to this group, send email to dspac...@googlegroups.com.


Visit this group at https://groups.google.com/group/dspace-tech.


For more options, visit https://groups.google.com/d/optout.

[Donald Bynum]

Claudia,

Thank you for the suggestion.  Unfortunately that did not work as hoped.  However, I did go ahead and execute what I had suggested in my original post (deleting the item child rows in associated tables and then deleting the ITEM row itself.  That appears to have resolved my issue.

Best regards,

Don.