Skip to content
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

Command line export does not create an output bib file #9581

Closed
2 tasks done
guillaumeparent opened this issue Jan 25, 2023 · 7 comments · Fixed by #9610
Closed
2 tasks done

Command line export does not create an output bib file #9581

guillaumeparent opened this issue Jan 25, 2023 · 7 comments · Fixed by #9610
Labels
component: bib(la)tex component: export-or-save FirstTimeCodeContribution Triggers GitHub Greeter Workflow good first issue An issue intended for project-newcomers. Varies in difficulty.

Comments

@guillaumeparent
Copy link

guillaumeparent commented Jan 25, 2023

JabRef version

5.9 (latest release)

Operating system

MacOS

Details on version and operating system

MacOS Ventura 13.0.1 (22A400)

Checked with the latest development build

  • I made a backup of my libraries before testing the latest development version.
  • I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

I am trying to create sub-databases (one database by author) from a global .bib file using the filtering features of the command line tool. Here is the commande I use to filter only AuthorOneName related papers from the global Input_bib.bib file:

JabRef --exportMatches Author=AuthorOneName,Output_bib.bib,bib -i Input_bib.bib -n

I do not receive any error message, everything seems to be ok, including the filtering. Nevertheless, no output file is created.
Important information: it fails when using bib format as output, but it works for other formats such as bibtexml, endnote, html for instance.

Am I doing something wrong or is it a bug related to the bib format ?

Appendix

Input_bib.bib
@article{AutOne2022,
author = 	 {AuthorOneName, AuthorOneFirstName and AuthorTwoName, AuthorTwoFirstName},
title = 	 {An interesting paper},
journal = 	 {Mickey Mouse Magazine},
year = 	 {2023}
}

@article{AutTwo2023,
author = 	 {AuthorOneName, AuthorOneFirstName and AuthorTwoName, AuthorTwoFirstName},
title = 	 {Another interesting paper},
journal = 	 {Donald Duck Magazine},
year = 	 {2023}
}

@Article{AutThree,
  author  = {AuthorThreeName, AuthorThree3FirstName and AuthorTwoName, AuthorTwoFirstName},
  journal = {I love datahseets magazine},
  title   = {Look at this one},
  year    = {2021},
}

@Comment{jabref-meta: databaseType:bibtex;}
@guillaumeparent
Copy link
Author

Sorry, OS was not good in the the description.

@Siedlerchr
Copy link
Member

I could reproduce this. I found out that the "bib" format seems to match the EmbeddedBibTexExporter which will embed bib files into a pdf.
And second, I found out there is no BibTexExporter that could be used with the matcher option...
So I think you stumbled across an edge case that no one thought about before...
Will flag this as enhancement

@guillaumeparent
Copy link
Author

guillaumeparent commented Jan 26, 2023

Thank you for the answer.

But are you sure the issue is related to the matcher option ?
I tried to convert a .ris file into a .bib file, without filtering as follows and it did not create any output file either.
JabRef -o Output_bib.bib,bib -i Input_bib.ris -n

On another hand, I tried the same command but this time with a bibtexml as an output and it worked perfectly well.
abRef -o Output_bib.xml,bibtexml -i Input_bib.ris -n

So couldn't the issue be related to exporting a .bib file ?

I add the .ris file for reproduction purpose:

TY - JOUR
AU - AuthorOneName, AuthorOneFirstName
AU - AuthorTwoName, AuthorTwoFirstName
T1 - An interesting paper
JO - Mickey Mouse Magazine
Y1 - 2023
ER -
TY - JOUR
AU - AuthorOneName, AuthorOneFirstName
AU - AuthorTwoName, AuthorTwoFirstName
T1 - Another interesting paper
JO - Donald Duck Magazine
Y1 - 2023
ER -

@Siedlerchr
Copy link
Member

From what I saw when you don't specify the output formant in the export command, it will use bibtex as default

@Shubhra0310
Copy link

i want to work on this issue

@Siedlerchr Siedlerchr added the FirstTimeCodeContribution Triggers GitHub Greeter Workflow label Jan 28, 2023
@github-actions
Copy link
Contributor

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.

@github-project-automation github-project-automation bot moved this from Normal priority to Done in Features & Enhancements Feb 13, 2023
@github-project-automation github-project-automation bot moved this from Free to take to Done in Good First Issues Feb 13, 2023
@guillaumeparent
Copy link
Author

Problem solved in the latest build. Thank you very much, it works like a charm.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: bib(la)tex component: export-or-save FirstTimeCodeContribution Triggers GitHub Greeter Workflow good first issue An issue intended for project-newcomers. Varies in difficulty.
Projects
Archived in project
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants