deleting entry removes the entry label from the other entries that crossref it

[ilippert]

JabRef 5.2--2020-10-26--3fe34a0
Linux 5.8.16-200.fc32.x86_64 amd64
Java 15.0.1

Steps to reproduce the behavior:

1. generate entry with label/key AAA
2. generate entry B that cross-references AAA
3. delete entry AAA from table

Result: Entry B misses the AAA cross-ref. It should be preserved.

[Siedlerchr]

Thinking about it, I see the behaviour of JabRef correct, as the label is an (internal) reference to the entry. When the entry no longer exists, to what should it refer? It would be inconsistent.

[ilippert]

I like to offer a friendly disagreement. Your argument seems to miss temporality. Only because now no referenced entry exists, it does not mean it will not exist in future. JabRef does and cannot know about the future. But JabRef could ask the user about their future intentions (and of course a default might follow your reasoning).
I see two options

• add this to the preferences world or
• ask the user (what do you want delete/do not delete /always keep/always delete [though still a preference option to change an "always" would be needed])

What do you think?

[koobs]

@Siedlerchr No longer waiting for feedback (OP responded)

[ruanych]

I also found another problem, different articles can have the same Citationkey. I am not sure if this is the expected behavior.

I don’t really understand how crossref works, in other words, how does it work with Citationkey.
I only found crossref in BibTeX source.
When I add A to the crossref in B and modify A, the content preview of B does not update.
A can be added to B's crossref twice.

[ilippert]

I also found another problem, different articles can have the same Citationkey. I am not sure if this is the expected behavior.

this sounds like a familiar problem. Worth checking this indeed.

I don’t really understand how crossref works, in other words, how does it work with Citationkey.
I only found crossref in BibTeX source.
When I add A to the crossref in B and modify A, the content preview of B does not update.
A can be added to B's crossref twice.

Sorry, I am not sure I understand the issue you are formulating here. Would you rephrase, please?

[ruanych]

Create First (the Citationkey of First is First) and Next, before add First to Next's corssref:

After added First to Next's corssref:
The Year of First seems to be previewable in Next.

Change the Year of First from 2020 to 2021, the Year in Next in the preview is still 2020.

I only found crossref in BibTeX source, I don’t really understand how crossref works.

[ilippert]

Thank you a lot, this helps.

you have successfully identified a bug: the year date should be updated immediately. I suggest you create a new bug report and reference the discussion here.

[k3KAW8Pnf7mkmdSMPHz27]

@ilippert you are referring to that the content of the crossref field disappear? (e.g., crossref = {CiteMe3} will disappear if the entry with citation key "CiteMe3" is deleted)

@ryyyc

I also found another problem, different articles can have the same Citationkey. I am not sure if this is the expected behavior.

Just because you can, doesn't mean that you should 😛
Citation keys are supposed to be unique, and if they are not they might lead to problems with other features as well, not just crossref.
If a user is using the generate citation keys feature, if two entries get the same citation key, JabRef will append a letter to the citation key to maintain uniqueness.

I don’t really understand how crossref works, in other words, how does it work with Citationkey.
I only found crossref in BibTeX source.

Are you referring to the need of pressing enter after typing the citation key? Otherwise I can recommend The biblatex Package for looking up information (unless you really need to use BibTeX). § 2.4.1 (page 41) is about cross referencing. biblatex/biber is often better documented

[ilippert]

@ilippert you are referring to that the content of the crossref field disappear? (e.g., crossref = {CiteMe3} will disappear if the entry with citation key "CiteMe3" is deleted)

Yes. The problem is indeed that if crossref = {CiteMe3} is deleted, then the entry with citation key "CiteMe3" gets deleted.

[ilippert]

I suggest to consider the issue here in relation to the issue/feature request proposed at #6404

[koppor]

Refs #6294