BibTeX keywords export glitch
Hello everyone -
When exporting citations from Zotero using the BibTeX format, the keywords get formatted improperly:
keywords = {{ABILITY,Character-based} {trust,DETERMINANTS,EMPLOYEES} – Attitudes,facet {theory,FAIRNESS,GROUP} {process,INTEGRITY,INTERPERSONAL} {relations,LEADERSHIP,ORGANIZATIONAL} change,smallest space analysis},
this should have been
keywords = {ABILITY,Character-based trust, DETERMINANTS, EMPLOYEES – Attitudes, facet theory, FAIRNESS, GROUP process, INTEGRITY, INTERPERSONAL relations, LEADERSHIP, ORGANIZATIONAL change,smallest space analysis},
Is there any way to modify the export translator file to tell it not to include any extra curly braces and just put commas and spaces in between?
Thank you!
When exporting citations from Zotero using the BibTeX format, the keywords get formatted improperly:
keywords = {{ABILITY,Character-based} {trust,DETERMINANTS,EMPLOYEES} – Attitudes,facet {theory,FAIRNESS,GROUP} {process,INTEGRITY,INTERPERSONAL} {relations,LEADERSHIP,ORGANIZATIONAL} change,smallest space analysis},
this should have been
keywords = {ABILITY,Character-based trust, DETERMINANTS, EMPLOYEES – Attitudes, facet theory, FAIRNESS, GROUP process, INTEGRITY, INTERPERSONAL relations, LEADERSHIP, ORGANIZATIONAL change,smallest space analysis},
Is there any way to modify the export translator file to tell it not to include any extra curly braces and just put commas and spaces in between?
Thank you!
This is an old discussion that has not been active in a long time. Instead of commenting here, you should start a new discussion. If you think the content of this discussion is still relevant, you can link to it from your new discussion.
Upgrade Storage
I do agree that keywords should probably be delimited by a comma and a space, though. This would be a trivial change to the translator.
I agree that is definitely not the "proper" thing; but that is the thing I need :)
The reason being is that the resulting BibTeX file is later getting imported into our installation of WIKINDX, and with curly braces all over the place it is a nightmare. WIKINDX wants keywords without curly braces around them, just separated by commas and a space.
Is that trivial change you talk about something I could do myself using Scaffold?
As a workaround to apparent limitations with both Zotero export and wikindx import, could you import some other format (such as Refer or RIS) into wikindx instead? Sure (assuming you're using a version where Scaffold still works). Line 1996 in BibTeX.js reads:
tagString += ","+tag.tag;and you should be able to replace "," with ", ".wikindx also doesn't support RIS imports as far as I know. I tried to cross process RIS using EndNote and then feed EndNote BibTeX into wikindx - still a mess.
Can killing braces also be done with Scaffold?
if(!isMacro) value = value.replace(/([^\s]+[A-Z][^\s]*)/g, "{$1}");Either comment it out or add another conditional to make it to this for fewer fields.RIS imports may very well be supported by wikindx - I probably just don't know how to do it. I have been using BibTeX for everything and got used to it so I didn't investigate the other options much.
For the two custom edits (killing braces and adding spaces) that I should do locally (I agree that it is not something everyone would benefit from) - how do I go about doing that? That might sound like a stupid question but all this stuff is new to me - I didn't know about Scaffold until this morning. Do I edit the BibTeX.js file manually? If so, where is it located?
Edited the file in Dreamweaver - works like a charm!
Thank you for your help!!
In 1.0, there was not a separate BibTeX.js file (all translators were in scrapers.sql, which you could either edit directly (prior to opening firefox) or by using scaffold).
http://www.zotero.org/support/dev/modifying_zotero_files
as guidance and it didn't work
That's good to know because I have to do this for our entire research team and this way they don't have to upgrade to a beta version (some of them might be unwilling to do that)
http://www.zotero.org/support/dev/creating_translators_for_sites
might be more pertinent to translators (rather than general changes to the code), but you might have to wade through it just a bit if you wanted to make a simple change like this.