Hide material from collection fromthe library
As soon as you have a few collections, your library quickly becomes so large as to be useless for independent references. If something is put in a sub-collection directly, it does not appear in the parent collection unless copy-pasted there.
Those are entirely opposite behaviors that should be easy to adjust with a "show in parent" option on each collection. Tags can theoretically perform that duty, but it's pointless to add an extra layer of data for something that represent a different organisation.
Those are entirely opposite behaviors that should be easy to adjust with a "show in parent" option on each collection. Tags can theoretically perform that duty, but it's pointless to add an extra layer of data for something that represent a different organisation.
There's no way to hide items from the Library, and there likely won't ever be. (For a similar system, see iTunes.)
Hitting Delete on an item in the Library pops up a delete confirmation dialog and then, if the action is confirmed, deletes the item from the Library.
You can delete from the Library from within a collection with Ctrl/Cmd-Delete or by right-clicking and choosing "Delete Selected Item from Library".
You can hold down a modifier key (ctrl on linux/windowd; option on mac) to see what collections an item belongs to. If you've expanded your collection hierarchy & can see all collections & also see that none are highlighted in yellow, you know the item doesn't belong to a collection.
(I know I could just export them, and put the exported files in directory to 'import someday'. or even create another firefox profile with my archive as the Zotero library. Both of these are a little unwieldy, but I'll do them if I need to.)
Didn't know that. *adds that to the list of undocumented features*
"Everything is in the library (and can optionally be in one or more collections), so nothing is ever incorrectly in the library."
My bad. I meant "is only in the library instead of being, as planned, in a collection"
For the record, a prime reason for this issue is that when you delete a record from a collection, you should probably be asked whether you also want to delete it from the library, since the records otherwise continue to cramp up the library even though it originally looks as if it was deleted.