Upgrade StoragePapercuts
This is an old discussion that has not been active in a long time. Before commenting here, you should strongly consider starting a new discussion instead. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
1) Check for alt modifier in the drop event and if it makes sense to copy (e.g. when you are moving an attachment to a new item it can be copied or moved), then copy instead of move
2) Disable changing the mouse cursor with alt altogether
I would vote for a wiki page for keeping track of issues.
Please note that I have edited my post about importing from the clipboard directly into a collection.
I would not only vote for a wiki to keep track of requests but I volunteer to assist with monitoring it and organizing topics.
Would it be helpful to add to the github issue tracker using a "Papercut" label? Or would you rather not?
If the cord devs like the idea, I think an issue tracker is preferable to a wiki. I believe anyone with a github account can open issues - the only thing devs would have to do is to create the label.
If devs don't want to use the issue tracker for this, I figure the wiki is going to be mostly for people making suggestions to have a list that's easier to oversee than this thread - I'd still consider that useful.
In either case, this thread should remain the main place for raising new papercut issues, so there's room for discussion (as in "can't be done," "won't be done," "maybe shouldn't be done," "is already done" etc.). For the list to be useful, all issues on it should be uncontroversial.
https://github.com/zotero/zotero/issues
It looks like regular users can't add labels to issues - we can just use [papercut] in the issue name and one of the people with admin privileges can add the label from time to time.
I created an issue from number 27
href="https://github.com/zotero/zotero/issues?sort=created&direction=desc&state=open&page=1
@DWL-SDCA : I understand your issue, and I agree that importing to a selected collection instead of creating a new collection is a good idea. However, the problem with this approach would be that import behavior would be inconsistent. So I would prefer to have a preference option whether you could choose if all imports are done as new collections or not. Please start a new thread and link to that, if you want to discuss this issue further.
Someone over on dev is working on 14)
http://groups.google.com/group/zotero-dev/browse_frm/thread/397c92dc143f9297
As for 26) - this is clearly generally desirable, but as mronkko's comments suggest the details of how to implement may require more thought - I suggest DWL opens a thread on that.
http://forums.zotero.org/discussion/20545/csl-style-error-reference-with-no-printed-form/
It's a small glitch that can be overcome by selecting another style, then switching back. Experienced users hardly think of the extra clicks, but users typically encounter it for the first time when they have found something broken, have asked for help, and may have a deadline coming up.
If just clicking "Refresh" were sufficient, it would relieve stress in that situation.
This would help troubleshooting citing the same item from multiple libraries.
https://github.com/zotero/zotero/issues/26
(Right now at least on Windows 7/FF8 the UI "feels" unresponsive. There is no submit button and the cursor keeps blinking after hitting Enter, meaning there is no feedback whatsoever that you have even submitted the identifier let alone that it is now being processed.)
(Crossposting from here.)
(Done now.)
Already on github and in a separate thread, but not mentioned here yet. The perfect papercut in terms of the number of times this issue has been raised in the forums.
It is confusing because (1) attachments are visually presented as files (with icons); (2) anything dragged and dropped already behaves in the suggested way, it's just attachments added by the translator that get this special treatment; (3) there is already a field for translator in the right pane so it is redundant information and the file name is arguably more important.
References: Old thread with proposal (2008); recent example of a user who got confused by the distinction.
/edit: reworded in response to mronkko.
For example one of my items has the following files
Nunnally1978_Bibliography_and_Indexes_OCR.pdf
Nunnally1978_Ch1_Intro_OCR.pdf
(about 15 more files would follow)
Autorenaming would have no way of knowing which chapter is which and this information would be lost.
It is really striking how often this comes up in the forums (it was the topic of my first posting here back in 2007 and it came up for a brand new user yesterday — and we know that the people coming to the forums are only the tip of the iceberg!).
The "select multiple items and drag on tag in tag selector" is just plain unintuitive and should be supplemented by something better.
* "Add Tags...", which would open a popup window "Add Tag(s)" with an entry field with autocomplete of existing tags (the tags could be shown similar to citations in the new citation entry window used for the word processor plugins, which would also allow for comma-delimited entry of multiple tags).
* "Remove All Tags"
https://github.com/zotero/zotero/issues/24
40) Allow dragging an item to a library even if it exists in the trash of that library
Example where 40 would be useful
- Drag any item from group library A to group library B
- Remove that item from group library B
- Drag the same item from group library A to group library B. This does not succeed because the item is already in trash. This is not consistent how trash works in any other software that I use.
https://github.com/zotero/zotero/issues/25
https://github.com/zotero/zotero/issues/23
Seems that many papercuts have not been added to GitHub because the issue number there is much smaller than the numbering of paper cuts here.
38 for example has been implemented a little while ago.
Also, one of mark's pet issues - the progress bar for add-by-identifier was just committed to the 3.0 branch by Simon - I thought this was among the papercuts, but don't see it here.
Could I perhaps suggest that someone more Github-savvy occassionally trail this thread and add suggested items to Github? Shouldn't take too much time, and if that gives devs better ways to respond that would be great. I could then edit my posts in this thread and mark things "done" as needed to prevent confusion.
I just did this with #31. I have the feeling that #34 might also be implemented already, can someone confirm?