-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[6574] Added support for biblatex-software #6747
Conversation
Hi @hemantgs , I also was thinking about abstraction of this feature in the mid to far future, maybe something to decide on JabCon2020, so don't think of it in this PR: One could activate native support for biblatex-software or IEEE or for music or other biblatex drivers as an additional feature in the preferences. |
Yep codewise looks already good! |
@calixtus @Siedlerchr Cool 👍 |
Yes, I think that makes sense and to have a nice newer screenshot for here and the entry id manually |
Added change to changelog md checkstyle fixed checkstyle fixed
2ccfd10
to
7f8df6b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, looks good to me!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for working on it. I have some refinemenets to the adr.
|
||
## Context and Problem Statement | ||
|
||
JabRef does not right now have support for Biblatex-Software out of the box , users have to add custome entry type. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
JabRef does not right now have support for Biblatex-Software out of the box , users have to add custome entry type. | |
JabRef does not right now have support for Biblatex-Software out of the box, users have to add custome entry type. |
## Context and Problem Statement | ||
|
||
JabRef does not right now have support for Biblatex-Software out of the box , users have to add custome entry type. | ||
With citing software becoming fairly comen , native support would be helpful. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With citing software becoming fairly comen , native support would be helpful. | |
With citing software becoming fairly common, native support is helpful. |
|
||
## Decision Drivers | ||
|
||
* The new entry types definitions should be added to the Select Entry Pane and be separated by a divider |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think, this line should be removed. It is not a "global driver", but one implementation option.
The other point is OK. - Even if it is a single one.
|
||
## Considered Options | ||
|
||
* Adding the new entry types to the existing biblatex types , but it conflicted with an already existing type(software) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* Adding the new entry types to the existing biblatex types , but it conflicted with an already existing type(software) | |
* Add the new entry types to the existing biblatex types |
|
||
### Adding the new entry types to the existing biblatex types | ||
|
||
* Good, since ther is no need for a new category in the add entry pane |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* Good, since ther is no need for a new category in the add entry pane | |
* Good, because there is no need for a new category in the add entry pane | |
* Bad, because it conflicts with an already existing type (software) |
note = {First Scilab version. It was distributed by anonymous ftp.}, | ||
crossref = {delebecque:hal-02090402} | ||
} | ||
@software {cgal, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add an empty line before
introducedin = {cgal:3-1}, | ||
url = {https://doc.cgal.org/5.0.2/Manual/packages.html#PkgVoronoiDiagram2}, | ||
} | ||
@softwaremodule{cgal:lp-gi-20a-condensed, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add an empty line before
origin=https://github.com/CGAL/cgal/}, | ||
url = {https://doc.cgal.org/5.0.2/Manual/packages.html#PkgVoronoiDiagram2}, | ||
} | ||
@software {parmap, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add an empty line before
## Considered Options | ||
|
||
* Adding the new entry types to the existing biblatex types , but it conflicted with an already existing type(software) | ||
* Add a divider with label Biblatex-Software underwhich the new entries are listed : Native support for Biblatex-Software |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* Add a divider with label Biblatex-Software underwhich the new entries are listed : Native support for Biblatex-Software | |
* Add a divider with label Biblatex-Software under which the new entries are listed: Native support for Biblatex-Software |
|
||
## Decision Outcome | ||
|
||
Chosen option: Yet to be decided. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Chosen option: Yet to be decided. | |
Chosen option: Add a new devider, because comes out best (see below). |
Hi @koppor I have updated the ADR per the review comments , please do have a look |
Thank you very much for your contribution and for creating an ADR! |
markdown-lint is already fixed in master 🎉 |
Not sure why the other PR complained ther: https://github.com/JabRef/jabref/runs/1016112813?check_suite_focus=true |
Markdown was fixed. I overlooked the unit test probably because of the failing architecture thing. |
Fixed by @calixtus |
Test fixed at #6780. |
Looks like I overlooked the unit test , apologies guys |
We did so too, no need to apologize. 😉 |
Added change to changelog
Fixes #6574
This PR is in reference to #6574
Added the new biblatex software entries under a new divider like the below image