Postscript export: Moving website title from journal to howpublished field

[niloysh]

This is not an error report or an enhancement request, I just have a question.

I am using the Better BibTex exporter and I have a reference of type webpage that I want to export to .bib and include it in my LaTex file using the IEEEtran style.

I have found the corresponding postscript snippet on the documentation page that adds access date and URL. It works as expected. It uses the @misc field and outputs the website title to the journal field. I have also turned on the export URL feature.

Now, the IEEEtran style does not actually output the contents of the journal field (which represents the content of website title} in @misc type entry.

But IEEE reference guide states that the Website title should be given as follows:

Since I am already using the URL, I want to remove URL from howpublished and move the website title to howpublished, so that it is displayed properly. So, my question is How can I modify the postscript snippet to have website title show up in the howpublished field?

So far I have tried to access it using item.websitetitle or item.websiteTitle but could not get it to work. Thanks for your help.

[label-gun]

It looks like you did not upload an debug report. The debug report is important; it gives @retorquere your current BBT settings and a copy of the problematic reference as a test case so he can best replicate your problem. Without it, @retorquere is effectively blind. Debug reports are useful for both bug analysis and enhancement requests; in the case of export enhancements, I need the copy of the references you have in mind.

This request is much more likely than not to apply to you, too, even if you think it unlikely, and even if it does not, there's no harm in sending a debug log that turns out to be unnecessary. @retorquere will more often than not just end up saying "please send a debug log first". Let's just skip over the unnecesary delay this entails. Sending a debug log is very easy:

1. If your issue relates to how BBT behaves around a specific reference(s), such as citekey generation or export, select at least one of the problematic reference(s), right-click it, and submit an BBT debug report from that popup menu. If the problem is with export, please do include a sample of what you see exported, and what you expected to see exported for these references.

2. If the issue does not relate to references and is of a more general nature, generate an debug report by restarting Zotero with debugging enabled (Help -> Debug Output Logging -> Restart with logging enabled), reproducing your problem, and selecting "Send Better BibTeX debug report..." from the help menu.

Once done, you will see a debug ID in red. Please post that debug id in the issue here.

Thank you!

[retorquere]

If you pick question from New Issue, @label-gun doesn't come into action. Anyhow, in this case I really do want a debug log as per instruction 1. from @label-gun. It will give me a copy of the item I can import into Zotero so I don't have to retype the screenshot.

[niloysh]

Sorry about that. The report ID is GW4AP6P4-apse. Thanks for your help.

[retorquere]

This should do it:

if (Translator.BetterBibTeX && item.itemType === 'webpage') {
  if (item.accessDate) reference.add({ name: 'note', value: `(accessed ${item.accessDate.replace(/\s*T?\d+:\d+:\d+.*/, '')})` })
  if (item.url) reference.add({ name: 'howpublished', bibtex: `{\\url{${reference.enc_verbatim({value: item.url})}}}` })
  if (item.publicationTitle) reference.add({ name: 'howpublished', value: item.publicationTitle })
}

If you want to know what items look like inside the postscript, you can export them as BetterBibTeX JSON.

[niloysh]

It works perfectly! The part about exporting them as BetterBibTex JSON was also very helpful. I would suggest adding this one line in the documentation in the scripting section. It would help users perform simple modifications to the example scripts given there.

Since my question has been answered, I am closing this issue. Thanks again for the wonderful software.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.