is it possible to mark items as readonly?
It is quite easy for a mistake with the mouse to cause major changes in cited items, e.g. making a book into a journal article. I wonder whether there is a way to lock items, making them readonly unless the lock is removed? This is a feature of most operating systems, and I think it would be very handy to have in zotero, also. I wonder if this already exists and, if not, I wonder whether other users might consider this a useful addition.
As always, thanks for zotero, which is a wonderful tool.
As always, thanks for zotero, which is a wonderful tool.
(The feature also causes no end of grief on operating systems. On these forums alone there are upwards of 100 threads with problems caused by read-only files. It's probably worthwhile there since you can otherwise mess up your whole system, but not sure we'd want to emulate that...)
Actually, this is not a huge issue for me, because I have daemons that backup my database on regular intervals. I know, I'm supposed to trust "time machine" on my mac, but I am an old unix guy and I prefer to set up my own insurance schemes. That oldness probably also explains my uncomfortable relationship with the mouse.
Many thanks for the rapid and informative response.
Several times a day, when I am quickly moving my mouse to place my cursor into the title field to edit, I instead accidentally click in the item type field. This opens the drop-down type menu. This is so frequent that I find that I automatically / reflexively position a finger above the escape key to kill the drop-down as I move to position the cursor for the edit. I use a Mac and I find that this happens less frequently after I changed from the Magic Mouse to a more conventional Logitec mouse. This is a minor UI issue for me but I suspect that it is not uncommon among Zotero users.
Locking parts of records would seem to me to add an impossible level of complexity to the UI. I agree that you can accidentally click on the wrong field in the right-hand pane, but that action is trivially easy to correct (use esc, tab, or click somewhere else), so isn't particularly costly. I don't see a solution to this that doesn't involve significantly more clicks.
I haven't used any *ux environment.