URL not exported from 'Software' type citation

[SamuelMarks]

Zotero version: 5.0.96.3

BBT version: 6.1.2

Support log ID: ABNKJZ9P-euc

Exporter used: Better BiBTeX

Expected behavior:

@misc{marksCddpython2021,
  title = {Cdd-Python},
  author = {Marks, Samuel},
  year = {2021},
  url = {https://github.com/offscale/cdd-python}
}

Actual behavior:

@misc{marksCddpython2021,
  title = {Cdd-Python},
  author = {Marks, Samuel},
  year = {2021}
}

---

Here's what it looks like from Zotero:

not a support log ID

[github-actions[bot]]

It looks like you did not upload an support log. The support log 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. Support logs are useful for both analysis and for enhancement requests; in the case of export enhancements, @retorquere needs the copy of the references you have in mind.

If you did try to submit a support log, but the ID looked like D<number>, that is a Zotero debug report, which @retorquere cannot access. Please re-submit a BBT debug log by one of the methods below. BBT support log IDs end in -apse or -euc. Support logs that include sample references will end in -refs-apse or -refs-euc; these are the type @retorquere needs for export or citekey issues.

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 usually 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, depending on your situation, follow one of these procedures:

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 support log 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, either by pasting it in a comment here (if it is small) or attaching it as a .txt file (if it's large). These logs will have an ID that ends in -refs-apse or -refs-euc.

2. If the issue does not relate to references and is of a more general nature, generate an support log 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 support log ID in red. Please post that support log id in an issue comment here.

Thank you!

[retorquere]

please send a debug log ID

[SamuelMarks]

ABNKJZ9P-euc

[retorquere]

I need a debug log ID as described in point 1 above.

[SamuelMarks]

not a support log id

``` (3)(+0000000): Better BibTeX: 199 (3)(+0000000): BibTeX: 200 (3)(+0000000): COinS: 310 (3)(+0000000): Better CSL YAML: 800 (3)(+0000048): BBT: loading ExportOptions (3)(+0000276): BBT: ExportOptions loaded (3)(+0006170): {better-bibtex} +19754 export overrides: {"postscript":null,"preferences":null,"strings":null} (3)(+0000000): {better-bibtex} +0 worker translation: true (3)(+0000001): {better-bibtex} +1 worker context: version=5.0.96.3&platform=mac&translator=Better%20BibTeX&output=%2FExported%20Items.bib&localeDateOrder=mdy&debugEnabled=true&worker=1 (3)(+0000006): {better-bibtex} +3 export scope: {"items":[{"key":"I6LR2EN4","version":1616,"itemType":"computerProgram","title":"cdd-python","date":"2021","url":"https://github.com/offscale/cdd-python","accessDate":"2021-12-28","creators":[{"firstName":"Samuel","lastName":"Marks","creatorType":"programmer"}],"tags":[],"collections":["HW4RUC4X"],"relations":{},"dateAdded":"2021-12-28T20:52:22Z","dateModified":"2021-12-28T20:56:22Z"}],"type":"items"} (3)(+0000001): {better-bibtex} +3 cache-rate: starting prep (3)(+0000008): {better-bibtex} +9 cache-rate: prep done (3)(+0000000): {better-bibtex} +0 cache-rate: load cache? true (3)(+0000000): {better-bibtex} +0 cache-rate: load item cache (3)(+0000005): {better-bibtex} +5 cache-rate: cache loaded (3)(+0000001): {better-bibtex} +1 worker: kicking off, config is 3497 (3)(+0000000): {better-bibtex} +0 worker: post-kickoff, config now 0 (3)(+0000365): {better-bibtex Better BibTeX (worker 1)} +null worker: received {"isTrusted":true,"kind":"start"} (3)(+0000000): {better-bibtex Better BibTeX (worker 1)} +1 worker: starting (5)(+0000004): Translate: Running handler 0 for itemDone (5)(+0000000): Translate: Running handler 0 for itemDone (3)(+0000027): {better-bibtex} +396 worker translation done, result: false (3)(+0000001): Translate: Translation successful ```

[retorquere]

please read point 1. I need a debug log ID with -refs in it.

[SamuelMarks]

So looks like it does appear in the RDF export:

RDF, still not a support log ID

```xml computerProgram Marks Samuel cdd-python 2021 https://github.com/offscale/cdd-python 2021-12-28 ```

Also the CSL JSON (also works with 'Better CSL JSON'):

CSL-JSON, still not a support log ID

```json [ { "id": "marksCddpython2021", "type": "book", "title": "cdd-python", "URL": "https://github.com/offscale/cdd-python", "author": [ { "family": "Marks", "given": "Samuel" } ], "accessed": { "date-parts": [ [ "2021", 12, 28 ] ] }, "issued": { "date-parts": [ [ "2021" ] ] }, "citation-key": "marksCddpython2021" } ] ```

Even 'Better BiBLaTeX' works:

@software{marksCddpython2021,
  title = {Cdd-Python},
  author = {Marks, Samuel},
  date = {2021},
  url = {https://github.com/offscale/cdd-python},
  urldate = {2021-12-28}
}

But 'Better BiBTeX' gives:

@misc{marksCddpython2021,
  title = {Cdd-Python},
  author = {Marks, Samuel},
  year = {2021}
}

[retorquere]

Can you please just get me a support log ID with -refs in it. See point 1.

[retorquere]

A support log ID gives me a copy of the item in your database, plus your current BBT settings. Without it I'm left to guessing what your current situation is.

bibtex does not support URL fields, but there are various workarounds you can enable in BBT.

[retorquere]

closing for inactivity.

[SamuelMarks]

@retorquere I thought you gave the answer:

bibtex does not support URL fields, but there are various workarounds you can enable in BBT.

So you can add the tag 'expected result' or whatever

[retorquere]

I generally don't close issues until I have confirmation that the user has a working situation. That it's the expected result is not always helpful, so I generally stick around to find workarounds when needed.