A few questions regarding the UI, the entry editor and others

Hi, thanks for the reply, here’s the follow up for each answer:

1. I’ve tried to edit the “Customized preview style”. I’ve tried several modifications because the syntax didn’t look to be that cryptic, but they all failed. For example, deleting the first line and pressing save will close the preferences window without actually saving it. Doing the same thing but switching to preview first will always reset to the previous state as well. Even deleting the entire thing leaving only a blank line will still reset to a previous state. Those are my steps to reproduce it, it doesn’t really matter what I do it always resets back to its previous state. I can record a short video if you wish, because I’m not quite sure what else to tell you.

2. So it seems that I can’t get rid of the “Required fields” and “Optional fields” then. My goal was to include all of that in the "General ", as to take up less space, but that’s not such a big deal.

3. Thanks, worked as expected, not quite sure how I missed that.

4. I suppose in Windows it doesn’t have such an intrusive path, this is fairly annoying somebody else must have brought this up so far!

5. I was looking for something beyond that, as I’m currently doing research which I will use to write my master thesis (in theoretical Physics, in case somebody in the field has some tips). I know that this is heavily dependent on the work you are doing, but having some idea on the groups that people define, their commenting scheme both in Jabref and in the PDFs, their visual overlay, usage of the Jabref special groups, etc. would be great, because I’m simply replacing my folder full of PDFs to a Jabref window full of PDFs, which isn’t a major improvement, but what I feel like the first step towards a very organized library.

For 1. you should check out:
- How to customize reference style? - #4 by Siedlerchr
- Entry preview setup - JabRef
- Custom export filters - JabRef
It seems to be a little complicated, but maybe it answers the question. I agree that it is confusing why edit does not work and if it were to be intentional, maybe it would be a good idea for this to change? Would you be so kind to make an issue at github: Issues · JabRef/jabref · GitHub

Could you provide a screenshot of 4. ?

Of 4.? The location of the jabref.xml in my home directory? I can give you the contents which are inside of it, is that what you mean?

I just don’t know what that is or means. Sorry :sweat_smile:

I have seen specifically the guide on the “Entry preview setup” you have just linked in the documentation, and it doesn’t work, at all. Maybe this is a bug.
Here’s a video of me doing the steps presented in the documentation, where I copy the contents of another entry preview style, so that you know it’s valid, and it still doesn’t work:

It’s the third option for me, counting from the top:

Honestly, I have no idea what it does, I just assumed it saved my open libraries as well as window settings (size and etc.), but the latter resets every time I reboot the program.

Found it. Still not sure what it does, but it seems it is only necessary if you want to run Jabref from a pendrive and use the portable version of Jabref:

Memory stick mode, JabRef saves the preferences to an XML file in the root folder next to the installation. It is indeed intended for running JabRef from an USB stick or external hard disk.
But in practice it still has some limits because it still writes the Prefs to the preferences folder/registry (on Windows) before writing them to xml.


you can only modify the Custom Preview Style which uses JabRef’s own formatting system. This is different from the xml based CSL ones. They are incompatible.
The other citation styles are those from CSL and cannot be modified in JabRef.

So then if I disable that check marks, nothing will happen because all of the settings are saved somewhere in my system, right?

Do you think that this is a bug? It surely does look like one, since I can’t seem to change the preview no matter what. I have no problem opening up a issue down at Github, I would just like to be confident that I’m not doing anything wrong.

Still regarding the question 5., I keep finding no information regarding the usage of the check integrity method to solve said problems. I imagine that having lack of capitalization, and hence the need to surround them in curly brackets, has been something which has happened to many people before, and fixing it manually when you might have loads of entries, seems unfeasible, and something which Jabref could easily handle.

I would just like to confirm that I have successfully removed the file without any problems whatsoever, all my settings seem to be in place after a reboot, so everything is being saved somewhere else.

Apparently it is not a bug. Christoph answered this:

If anything, it would be a feature request.

With regard to capitalisation, you can modify your dataset also with cleanup actions (Quality > cleanup entries).

I would create new threads (not just one, but a few. One for each topic) for this. This one here has become quite long and the topics you mention are all very specific and a microcosmos in itself.

1 Like

Yeah, I still have something to say about these subjects, and I was planning on doing a summary at the end with the solutions for each of my questions, but this makes it harder to find and understand for somebody who is external to the conversation.
Here’s what I’ll do (or the answer) for each question:

1.: I will open up a new thread to ensure that this is in fact a bug, before reporting it to Github - link.

2.: You can’t change the order of the tabs on the Editor Tabs, only (some of) its content.

3.: The option to change the authors name order and abbreviations in the entry table, can be changed at options > preferences > entry table.

4.: Memory sticky mode is intended for portable JabRef installations and for somebody who is not running it off of an USB stick, which is probably almost everybody, it doesn’t make any difference whatsoever.

5.: I just found out that this question isn’t new here, there’s a thread from 2016 with the exact same question I had - link. This thread was marked as solved as there was a pull request which should provide that functionality, however, I’m not quite sure what it offers. Should I bump this thread or should I open a new one?
To make this clear, my goal is to turn something like “Cosmology in $F(Q)$ Gravity constrained using Standard Sirens” to be turned into “{C}osmology in ${F}({Q})$ {G}ravity constrained using {S}tandard {S}irens”, i. e. respect the capitalization of the original title, in and outside of math mode.

@undercover For the protected terms: It does exactly what you want, it’s intended (for LaTeX users) to keep the casing of the term. It’s also preferable to encapsulate a whole term instead of a single letter, e.g.
{JabRef} instaed of {J}ab{R}ef as it prevents Kerning issues

There is just missing documentation on our help.

Thanks for the information, but I would still have to apply that manually to each title, right?

And after checking that entry on the TeXFAQ, it really doesn’t make much sense to be editing the title itself in my library, when that metadata should reflect precisely the content that the entry has, so either I’ll find a way to add that filter to JabRef when exporting my library to a custom file (something which I have yet to explore entirely, as just uploading the .bib file includes lots of unwanted content) or change my bibliography type in my document.

Well, it depends on your use case. The protecting of terms also prevents JabRef’s cleanup from mangling the fields, if it encounters a term that is in a list of protected terms.

Unfortunately, there is not yet an automatic cleanup action Refs: Cannot find how to protect terms listed in "Protected terms files" (i.e. enclose between {}) - #3 by madamwest