arxiv and eprinttype

[thecaligarmo]

Is your suggestion for improvement related to a problem? Please describe.
When you import from arxiv (Using "New Entry" -> ID type = Arxiv -> Arxiv id) everything works magically =D But, there's a tiny thing that could be better. Right now, when you import it does not create a "eprinttype = {arxiv}" part in bibtex. What this means is that when you then try and access the url link for "eprint", it fails because it doesn't have eprinttype set.

Describe the solution you'd like
When creating a new entry, if the new entry is an arxiv entry, then set the eprinttype to "arxiv"

[GuSheldom]

Hi, I would like to work on this issue, would you mind assign it to me, please? Thanks!

[github-actions]

As a general advice for newcomers: check out Contributing for a start. Also, guidelines for setting up a local workspace is worth having a look at.

Feel free to ask here at GitHub, if you have any issue related questions. If you have questions about how to setup your workspace use JabRef's Gitter chat. Try to open a (draft) pull-request early on, so that people can see you are working on the issue and so that they can see the direction the pull request is heading towards. This way, you will likely receive valuable feedback.

[GuSheldom]

Hi, I find a bug but I cannot explain why, when I try to import a entry with arxiv ID, it will return me 'archiveprefix = {arXiv}', which should be 'eprinttype = {arXiv}' if it is correct.

However, when I debugging the code, I find the ArXivFetcher should run correct,

Is that caused by the 'ArXivIdentifier' which return me the wrong identifier, or other reason, that change the eprinttype to archiveprefix?

[GuSheldom]

Or it is caused by the EntryConverter

[Siedlerchr]

Maybe in the post cleanup actions?

[GuSheldom]

I have fix the issue, but I think it is not an enhancement but a bug

[ThiloteE]

Sometimes fixing a bug is like adding a feature and sometimes introducing a feature is like adding a bug. ;-)

[Siedlerchr]

@thecaligarmo Thanks to @GuSheldom this issue is now fixed in the latest developer version:

Thank you for reporting this issue. We think, that is already fixed in our development version and consequently the change will be included in the next release.

We would like to ask you to use a development build from https://builds.jabref.org/main and report back if it works for you. Please remember to make a backup of your library before trying-out this version.