Cool, I was just checking out JabRef. I just wish it had some sort of internet lookup feature, where I could type in a book's ISBN, and it would look up the rest of the information so I don't have to type it all in. Just getting lazydyeu wrote:I use Jabref, for the nice GUI and features. It can import entries from CiteSeer, and also from PubMed if you're doing medical research.
that's a great idea; maybe I'll just do that instead of trying to get along with RefBase.dyeu wrote: It is a desktop app, not a web-based one. But I just use NFS, SVN or other means to synchronise my bibtex files between my machines.
Yeah, I was looking at using Kile or one of the other tex/latex frontends. I really don't want to spend a lot of time learning codes, although I really almost killed myself last time I attempted to put together my graduate research project using MS Office. That's something I'll never do again!dyeu wrote: Alternately, vi does the trickI just can't stand to write a research paper or bibliography with OpenOffice or MS Office.

Then by all means, if you're not already very comfortable with OpenOffice, avoid it.warthog wrote:Yeah, I was looking at using Kile or one of the other tex/latex frontends. ... I really almost killed myself last time I attempted to put together my graduate research project using MS Office. That's something I'll never do again!dyeu wrote:Alternately, vi does the trickI just can't stand to write a research paper or bibliography with OpenOffice or MS Office.
I use (and contribute both code and money to) refbase as a central web-based system. I also use various desktop clients, depending on what I'm using to author papers. I particularly like Zotero (a new plugin for firefox 2), Jabref, and bibus. I also use the in-build manager for OO.o & manage some bibtex by hand.warthog wrote:What are people using these days?
I didn't make that ebuild, but I've suggested fixes for it. Is there anything, in particular, that you don't like? refbase-0.9.0 will be released very soon & you're welcome to try the release candidate:I've been experimenting with web-based RefBase (since there is an e-build for it), but I'm not real happy with it.
As for the actual document creation process, I author in whichever format the journal prefers. This is usually either MS Word DOC (bleh!) or LaTeX (yea!). Some will only accept a single format. Also check what your colleagues use. I have colleagues who will only edit documents which can be read by Word. If you are using LaTeX or some other format, you may have to convert to RTF and/or DOC. This can be done (see, especially, latex2rtf and tex4ht), but results aren't "perfect" & you may have to explain that it will be prettier when the reviewers get PDFs and when it appears in print.warthog wrote:I am also not sure if I should use openoffice. I've used openoffice writer for small documents, but never for anything significant. Additionally, I'm not sure how well it imports bibtex databases. Although I've done some searching, and it does appear that it's possible. I'm also looking at lyx, which I have used before for math papers, but I'm not sure if I'd want to use if for a more general paper.
I didn't know about Zotero; it looks promising. At the moment I'm leaning towards Jabref. It seems to do a pretty good job for me. I'm also using OO.o's bibliographic database for small assignments. But every time I use OO.o, I find I'm more concerned with how the material looks, and I'm therefore not having as much time to spend on the content.karnesky wrote:I use (and contribute both code and money to) refbase as a central web-based system. I also use various desktop clients, depending on what I'm using to author papers. I particularly like Zotero (a new plugin for firefox 2), Jabref, and bibus. I also use the in-build manager for OO.o & manage some bibtex by hand.
I didn't appear to have any problems installing refbase, and I haven't spent a lot of time evaluating it, but my initial impressions are that it is probably overkill for what I'm trying to do, and some of the features of 0.80 are not working for me, but it could be that I didn't perform the installation correctly. In any case, the features that are not working are (1) bibtex exprort gives me a blank screen, and (2) uploading PDFs fail (I think that's related to directory permissions related to my install), and (3) I haven't found a way to produce the APA-style "cite", although that's not as important. Lastly, the italics are very difficult for me to read! I'm sure there must be some setting to turn off the italics, but I haven't found it yet. I'm sure some if not all of my problems are related to my install. I may go ahead and give your release candidate a try. Are there any installation instructions provided with the RC? I haven't looked at the tgz yet.I didn't make that [refbase] ebuild, but I've suggested fixes for it. Is there anything, in particular, that you don't like? refbase-0.9.0 will be released very soon & you're welcome to try the release candidate:
http://arc.nucapt.northwestern.edu/~kar ... rc1.tar.gz
This adds MUCH better import of references & also adds some nice features like export to OO.o and embedded metadata for use by extensions like Zotero or LibX.
You can check wherever you log your php errors (or set error_reporting = E_ALL, display_errors = On in php.ini). The most common cause of this is using the wrong path to bibutils when you installed refbase. This is improved ih 0.9.0: install.php will now search your path and auto-fill the correct path for your system. Also, if you have 'safe_mode' on in php.ini, then you'll need to put the Bibutils programs within the directory that's specified in 'safe_mode_exec_dir'.In any case, the features that are not working are (1) bibtex exprort gives me a blank screen
Again, check your error log. It can also be because of php.ini settings (file_uploads On, reasonable values for post_max_size and upload_max_filesize.uploading PDFs fail (I think that's related to directory permissions related to my install)
Right--The lead developer has a bias towards polar and marine biology & the styles match the journals they use. Customizing styles isn't that hard & the J. Glacial style is pretty close to APA. We probably should include some of these "universal" styles, though.I haven't found a way to produce the APA-style "cite", although that's not as important.
This can be controlled with the CSS. The italics aren't intentional & are most likely cause by a different font family. You can see the screenshots to see the intended style. You can also look at my installation, which uses the monobook skin from mediawiki (used by wikipedia). I agree that italics isn't desirable (and they're probably not intended), so will mention it on the dev list.Lastly, the italics are very difficult for me to read! I'm sure there must be some setting to turn off the italics, but I haven't found it yet.
Yes--the README will direct you to the important files (INSTALL and/or UPDATE). I'm sure you could get any additional help in the forums on sourceforge.I may go ahead and give your release candidate a try. Are there any installation instructions provided with the RC? I haven't looked at the tgz yet.
Well, thanks for trying it & for your feedback. I hope that it can work for you or at least that your experience can improve it for other people. I also hope that whichever tools you finally decide to use work out wel for you.BTW, thanks for replying to my post. I really appreciate the suggestions, and thanks for putting effort into refbase. I can definitely see that it's a very useful tool even if it doesn't work out for me.
Yep, that was my problem. I yanked all ocurrences of 'garamond' from the css file, and it now looks much better. I also installed 0.9.0, but I'm having some php problems when I try to add a record. I need to turn on php error logging and do some additional investigation when I get time.karnesky wrote:The problem with italics appears to be because some gentoo installs only have Garamond Italic installed. I have no idea why. A work-around is to remove the occurrences of "garamond" from the css file. The fix is probably to either remove garamond italic or to install the normal font.
See also this post.

I committed a APA style file to the refbase subversion repository.karnesky wrote:Right--The lead developer has a bias towards polar and marine biology & the styles match the journals they use. Customizing styles isn't that hard & the J. Glacial style is pretty close to APA. We probably should include some of these "universal" styles, though.warthog wrote:I haven't found a way to produce the APA-style "cite", although that's not as important.