Back to the main page.
Bug 2236 - update publication list with 2013
| Status | CLOSED FIXED |
| Reported | 2013-08-08 16:46:00 +0200 |
| Modified | 2013-09-18 13:19:12 +0200 |
| Product: | FieldTrip |
| Component: | documentation |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Windows |
| Importance: | P3 normal |
| Assigned to: | Robert Oostenveld |
| URL: | http://fieldtrip.fcdonders.nl/publications |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Stephen Whitmarsh - 2013-08-08 16:46:44 +0200
Robert Oostenveld - 2013-08-08 16:54:33 +0200
I have a bibtex application that can merge two bib files (BibDesk). I used it in the past as follows. I made two *.bib files, one from our wiki and one (using a text editor using the "import into bibtex" option on http://scholar.google.com/scholar?as_ylo=2013&hl=en&as_sdt=2005&sciodt=0,5&cites=3328911510682538425&scipsc= read them in BibDesk and merge them. Within BibDesk it is doable to deal with conflicting versions of the same paper by sorting them on title. PS I suspect that the 2nd half of 2012 also still needs to be included.
Robert Oostenveld - 2013-08-08 16:57:42 +0200
I just opened BibDesk (note: it is an apple-only application) and it is ridiculously simple to import from google scholar.
Robert Oostenveld - 2013-08-08 17:08:22 +0200
after downloading about 200 most recent entries from scholar, google started complaining and blocked my access :-(
Robert Oostenveld - 2013-08-08 17:08:59 +0200
Created attachment 503 bibtex file, 2013 up to now
Robert Oostenveld - 2013-08-08 17:09:28 +0200
Created attachment 504 bibtex file, 2012 partial
Robert Oostenveld - 2013-08-08 17:11:10 +0200
Created attachment 505 all entries from the current publication list
Robert Oostenveld - 2013-08-08 17:25:58 +0200
Created attachment 506 merged bibtex file, duplicates have been removed
Robert Oostenveld - 2013-08-08 17:48:17 +0200
The merged file did not display correctly. After replacing @phdthesis and @inproceedings with @article, it displays and sorts correctly. This is apparently a limitation of the inlinebib plugin. I also used VIM to fix some uppercase problems. It would still be possible to improve on the references, but that requires a lot of manual labor.