Hi, and thank you for this feedback! For easily checking this, could
you send me an example file? Or does it happen with any entry exported
from ISI?
> Today I gave a workshop on JabRef. One problem that appeared was the import
> of BibTeX-files generated by Thomson Reuters' "Web of Knwoledge"
> (webofknowledge.com).
>
> When I tried to import the files (see attachment), the status bar gave only
> the message "Importing from unknown format ..."
> 1) It would be nice to get a message like "Unknown format - unable to import
> datasets" (the "..." suggest that still something is going on. Participants
> of the workshop said "It can't last so long, its only a single dataset.")
It is supposed to give such a message if none of the import filters
match. If it doesn't, the process has probably crashed at some point.
If you open Help -> Show Error Console after trying to import, and
look at the "Exceptions" tab, you can see if there is a stack trace -
if so, it will probably be helpful in pinpointing the bug.
> 2) I also realized that you can't choose the BibTeX import filter. Probably
> because one should use "File / Append Database" :-D . Pesonally I preferr
> having less menu-entries, among which I have to choose.
If none of the import filters match, it does try to read it as BibTeX.
But again, in your case, the process has probably crashed for some
reason before reaching that point.
> When I entered the file content into the BibTeX source tab (or started the
> "import" via "File / Append Database"), i got an error message that finally
> showed me that the field " Web of Science-Category" conatins spaces.
> 3) I don't know if BibTeX allows spaces in field names. Even if it doesn't,
> wouldn't it be obliging to the user to ignore the inability of the
> WebOfKnowledge to create valid BibTeX files?
Spaces in field names are not allowed by BibTeX. I agree with the idea
of accomodating malformed files as much as possible, but the only way
I could see allowing spaces in field names would be if we could remove
the spaces or replace them with a different character.
> Most field values are given in double braces {{value}}. Only one of them is
> removed when importing the value, ruesulting in "{value}" beeing shown
> instead of "value".
> 4) Again I'm not sure if the BibTeX-format alows this. Anyway, it might save
> time for the users to remove both braces, unless there is a special reason
> for double braces.
This is allowed by the BibTeX format, and actually has significance
for some fields. A normal field given with single braces may be
converted to title case or lower case. Extra braces can be used to
preserve the case of e.g. names or acronyms. Adding extra braces to an
entire field preserves the case of the entire field.
JabRef has options under Options -> Preferences -> File both for
automatically removing double braces when loading, and for
automatically adding extra braces to a set of fields (added when
saving, removed when loading).
--
Morten
------------------------------------------------------------------------------
uberSVN's rich system and user administration capabilities and model
configuration take the hassle out of deploying and managing Subversion and
the tools developers use with it. Learn more about uberSVN and get a free
download at: http://p.sf.net/sfu/wandisco-dev2dev
_______________________________________________
Jabref-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jabref-users
