Yes, the troubleshooting instructions had those very helpful links -- and I should give credit where it's due! But they still advise OOo users to switch to LO, when the problem seems to be with Java.

I should remember cleaning it regularly...

yes, I essentially use jabref to do some 'cleaning up' on the Zotero-produced file - I started doing that when there wasn't an option to exclude notes from bibtex export (and the resultant gigantic bi

just cleaning up some old threads - this has been fixed in the meantime.

worth further exploration. However, because this cleaning step occurs before we search for a DOI, it probably explains why we sometimes fail to capture DOIs even when they exist. I've corrected this.

my suggestion was to use the filename, after cleaning it up with s/[^a-z0-9]/ /g or similar so that search engines have a cleaner search string. Zotero may even allow the user to edit the search stri

This is quite enough! One can even make temporary collections just for the purpose, if needed. And the resulting files may be joined for cleaning up and then split again in the same places. Sounds nic

no, there is still no solution apart from cleaning up journal names manually. This will be somewhat easier to deal with once batch-editing has been introduced, which is one of the top two priorities f

I've found the OCR recognition in Adobe Professional so awful on the old historical documents that it's never safe to highlight the text. Cleaning it up would take ten times longer than retyping it. (

So automatic cleaning would be much better.

Before you put any effort into cleaning this up, you should ask over at zotero-dev whether this would be likely to get accepted as a patch. For my taste it's a bit more of a hack than I would like. Th

One point I would mention here is that for some journals I have different full names in my library (I think you are aware of this possibility). Cleaning up my library would be probably the best soluti

I'm just spring cleaning my computer and tightening up my backup plan. In my Zotero folder on my HD I have the following files/folders:

There is no easy way to do this. Zotero has duplicate detection, but that is manual on a per-item basis - I don't think you'll get around cleaning your duplicates up semi-manually.

As for cleaning up references - I was referring to URLs, which should be removed from items where they don't belong. That's the only way to prevent erroneous citations.

I think scripting a CMoS variant will be *much* more efficient than cleaning up these fields, at least for the sort of sources I deal with.

Rosatto, I think it's time to start looking at cleaning up styles, rather than catching these problems in the processor. I've done this for five legal styles already in the CitationStylist project. I

But what do you mean "it just runs?" It downloads as a compressed file with no instructions I could find. Granted I had just finished cleaning and reinstalling the computer in question so was not in t

Thanks a lot for your input and cleaning up the script. It seems to be working fine on my data, except for the screened characters. As far as they go, I do not think it is necessary to screen them, si

LaTeX would give me a very clean print of the final document with consistent styles, something I can trust. I need to do some cleaning up of the styles in odt files, which will require a lot of work a