Markdown Export Formatter

[LinusDietz]

I quickly implemented an export format in a specific (admittedly, opinionated) format to Markdown... I find the format useful to put on websites that uses Markdown as input format website.

For anybody who's interested, the command I use to generate the list of the website is:

jabref -n -i literature.bib --exportMatches '(author="dietz"  and (entrytype=="article" or entrytype="inProceedings" or entrytype="inCollection"))',test.md,title-md

Mandatory checks

• I own the copyright of the code submitted and I licence it under the MIT license
• Change in CHANGELOG.md described in a way that is understandable for the average user (if change is visible to the user)
• Tests created for changes (if applicable)
• Manually tested changed features in running JabRef (always required)
• / Screenshots added in PR description (for UI changes)
• Checked developer's documentation: Is the information available and up to date? If not, I outlined it in this pull request.
• Checked documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request to the documentation repository.

[calixtus]

One suggestion about Changelog, other things look ok-ish to me.
As noone asked for this feature yet, i guess you will be the only one for a long time to use it, so opinionated implementation is fine for me.
What im not sure of is a custom SaveOrder hardcoded. Opinions?

[calixtus]

Yes, preferences save order. Maybe we can make it somewhat customizable in the layout files in a follow up?

[calixtus]

Please use prefs save order. That can and should be customizable in the future by layouts.

[Siedlerchr]

You can define the export save order here:

[LinusDietz]

but... can you do it in the cli from e.g. a github action?

You can define the export save order here:

[Siedlerchr]

Currently not possible, create a preferences file (export xml) and then you can import it via cli , "-p prefs.xml"

[koppor]

Typically, CSL styles are used for it - and one can select "copy as text"

Result:

[1]O. Kopp, C. C. Snethlage, and C. Schwentker, “JabRef: BibTeX-based literature management software,” TUGboat, vol. 44, no. 3, pp. 441–447, 2023, doi: 10.47397/tb/44-3/tb138kopp-jabref.
[2]O. Kopp, “The LaTeXtemplate generator: How micro-templates reduce template maintenance effort,” TUGboat, vol. 44, no. 2, pp. 203–207, 2023, doi: 10.47397/tb/44-2/tb137kopp-microtemplates.
[3]M. Stötzner et al., “A Systematic Technology Review of General-Purpose Open-Source TOSCA Orchestrators,” in Proceedings of the IEEE/ACM 16th International Conference on Utility and Cloud Computing, in UCC ’23. ACM, Dec. 2023. doi: 10.1145/3603166.3632130.
[4]S. König et al., “BPMN4Cars: A Car-Tailored Workflow Engine,” in 2023 IEEE 21st International Conference on Industrial Informatics (INDIN), IEEE, Jul. 2023. doi: 10.1109/indin51400.2023.10218082.

With some RegEx magic, this can be transformed to:

* O. Kopp, C. C. Snethlage, and C. Schwentker, “JabRef: BibTeX-based literature management software,” TUGboat, vol. 44, no. 3, pp. 441–447, 2023, doi: 10.47397/tb/44-3/tb138kopp-jabref.
* O. Kopp, “The LaTeXtemplate generator: How micro-templates reduce template maintenance effort,” TUGboat, vol. 44, no. 2, pp. 203–207, 2023, doi: 10.47397/tb/44-2/tb137kopp-microtemplates.
* M. Stötzner et al., “A Systematic Technology Review of General-Purpose Open-Source TOSCA Orchestrators,” in Proceedings of the IEEE/ACM 16th International Conference on Utility and Cloud Computing, in UCC ’23. ACM, Dec. 2023. doi: 10.1145/3603166.3632130.
* S. König et al., “BPMN4Cars: A Car-Tailored Workflow Engine,” in 2023 IEEE 21st International Conference on Industrial Informatics (INDIN), IEEE, Jul. 2023. doi: 10.1109/indin51400.2023.10218082.

I know, the DOI is not linked. I filed a feature request upstream: michel-kraemer/citeproc-java#252