Add support for biblatex-software

[koppor]

See https://www.softwareheritage.org/2020/05/26/citing-software-with-style/

biblatex-software is actually a bibliography style extension, which means that one can add support for these four software entry types to any other BibLaTeX style used in documents typeset in LaTeX, like the biblatex styles for ACM articles. It requires the Biber back end, though, so do not try it with pure BibTeX.

We should add the new types and fields in BibLaTeX mode.

[hemantgs]

Hi @koppor
Is this issue available, for me to work on ?

[koppor]

Sure, shouldn't be too hard. - The hard part is to understand the style and the idea/implementation of JabRef's pre-defined types. The code itself will be may be 10 to 50 LOC.

[hemantgs]

Cool,

The hard part is to understand the style and the idea/implementation of JabRef's pre-defined types

I was just going through the code at avery high level, figured adding the new biblatex-software entries to the StandardField enum would make it available for BibEntry.java
Am I on the right track ?

[koppor]

Does the GUI behave differently then? - This is a good first issue, because one needs to go through the code and understand, what's happening why. And why somewthing does not happen if one changes something. I assume, you know the "call hierarchy" feature etc? Ctrl+Mouse-click

[hemantgs]

Does the GUI behave differently then?

Ah it did not ,so I was wrong ! I think I am getting the hang of it , I was looking at the code , so a new entry for each of biblatex-software extension's

• software
• software versions
• software modules
• code fragments
  Need to appear in the New Entry pane , With the corresponding fields from the style documentation. An entry for Software is already there , the others need to be added to the BibLatex entry definitions along with their fields and types. The GUI renders all that is defined . I'll go ahead and add/make those changes , along with unit tests ?

This is a good first issue, because one needs to go through the code and understand,

Agreed , I am new to JabRef and oss contribution . Hopefully I am in the right path getting know the codebase.

EDIT: The Software entry that is in existence does not seem to be the same entry as in biblatex-software (the fields vary) , what do we do here

[koppor]

The "Software" might come from the IEEE style. Could you make a table showing the different fields. Column A: field name; column B field in IEEE present (exiting in jabref), column C field present in biblatex-software. Then a cross if it exists, empty else?

It would be helpful if the examples of https://packages.oth-regensburg.de/ctan/macros/latex/contrib/biblatex-contrib/biblatex-software/sample-use-sty.pdf were included in the tests. Maybe as a bib file in https://github.com/JabRef/jabref/tree/master/src/test/resources/testbib?

I think, we need a divider in the menu (as we have for IEEE, don't we?) Screenshots should be at https://docs.jabref.org/collect/add-entry-manually, but we currently don't have one.

The other alternative is to add refine the howto for customize entry types and ship a .bib file with the customization included so that each user can load it if he wants to use biblatex-software.

I find software that important so that we should ship support with JabRef as default.

If possible, could you also add an ADR containing the options "Native support in JabRef" and "Support via customized entry types"?

[hemantgs]

Comparison of the both :

Column	JabRef-Software	biblatex-software
AUTHOR/EDITOR	✔️	✔️
TITLE	✔️	✔️
DATE	✔️	✔️
SUBTITLE	✔️	✔️
TITLEADDON	✔️	❌
HOWPUBLISHED	✔️	❌
DOI	✔️	❌
EPRINT	✔️	❌
EPRINTCLASS	✔️	✔️
EPRINTTYPE	✔️	✔️
URL	✔️	✔️
URLDATE	✔️	✔️
HALID	❌	✔️
HALVERSION	❌	✔️
INSTITUTION	❌	✔️
INTRODUCEDIN	❌	✔️
LICENSE	❌	✔️
MONTH	❌	✔️
NOTE	❌	✔️
ORGANIZATION	❌	✔️
PUBLISHER	❌	✔️
RELATED	❌	✔️
RELATEDTYPE	❌	✔️
RELATEDSTRING	❌	✔️
REPOSITORY	❌	✔️
SWHID	❌	✔️

I think, we need a divider in the menu

What should be the text overlay on the divider ? BibTex has IEEETran

ship a .bib file with the customization included so that each user can load it if he wants to use biblatex-software.

Is this a current functionality(if so can you point to an example) or something that we are trying to build with this issue ? If its new , does this mean a new UI component(dropdown?) in the Customized Entry Type dialog to specify which type the new entry inherits from ?

could you also add an ADR

Yes , sure

[Siedlerchr]

Thanks to @hemantgs this issue is now resolved