From: Michael M. <mic...@ma...> - 2004-01-08 00:18:43
|
Hi - did I already reply to this email? I forget... Anyway, I agree that the way it handles editing is poor. It's definitely a first stab at doing it the right way, and certainly the right way is what you said you expected... What puzzles me is that with a year or so of perspective, I feel like it should have been easier to backup and replace! Why did I do it the other way? We may never know... cheers, and let us know how the other work goes! If you decide to start a weblog about it (which I am a big proponent of, since it lets me keep track of things, as well as helping students keep track of progress and share knowledge) let us know. -mike On Dec 26, 2003, at 7:17 AM, Brian Helenbrook wrote: > Mike & James & others, > > I'll keep you posted about the students progress with bibliographic > data. I've tried to do this myself, and its definitely not trivial. > Thanks for the info about it. Don't get your hopes up too much, but > maybe they'll make some good progress. > > One more suggestion for BibDesk: > > When a .bib file gets corrupted and BibDesk asks you if you want to > fix it, it automatically creates a new .bib file. I didn't know this > and went on working like I was still using the old one. Then I quit > and reopened and was a little surprised to see all my changes gone. > It took me a while to figure out what had happened. I think BibDesk > should backup the old one under a new name and then replace the > current one. > > Brian > > >> Wicked. Please check out my blog where I've been struggling through >> this with similar intentions and not enough skill or time this >> semester. >> >> http://shangorilla.syr.edu/themp >> >> Also you'll no doubt be interested in the research behind >> citeseer---is that what you had in mind? >> >> http://www.neci.nec.com/~lawrence/pub-ri.html >> >> I would love to be in the loop on this one. > > > Dr. Brian T. Helenbrook > Clarkson University > MAE Dept. Box 5725 > Potsdam, NY 13699 > 315-268-2204 > > <Brian Helenbrook.vcf> |