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

Group names are matched wrong #1873

Closed
michael-siebers opened this issue Aug 27, 2016 · 3 comments
Closed

Group names are matched wrong #1873

michael-siebers opened this issue Aug 27, 2016 · 3 comments
Labels
bug Confirmed bugs or reports that are very likely to be bugs groups

Comments

@michael-siebers
Copy link

JabRef version 3.6 (also 3.5) on Ubuntu 14.04

Group membership of entries is stored in the groups-field. Groups are identified by their name. Multiple groups are separated by commas. It seems that during matching (for marking group memberships in the groups interface), group names are split at commas and spaces. These facts lead to the following undesired behaviours:

  1. If an entry's group field contains 'a b' it is considered a member the groups 'a', 'b', and 'a b'.
  2. If an entry's group field contains 'a' it is considered a member of the groups 'something'/'a' and 'anything'/'a'.
  3. If an entry's group field contains 'a b', you can remove it from group 'a'. Resulting in the entry being considered a member of 'b' (in combination with 2., possibly in some other branch of the group tree).

This behaviour might completely break the group-entry relations.

Steps to reproduce:

  1. download and open jabref_bug.bib.txt
  2. Add the entry 'demo' to the group 'some rating'/'very good'
  3. Observe, that the entry now belongs to all four (leaf) groups
  4. Remove the entry from group 'some rating'/'good'
  5. Observe that the entry now only belongs to group 'other rating'/'very'
@michael-siebers
Copy link
Author

Possible duplicate of #1495.

@matthiasgeiger
Copy link
Member

Hi Michael!
Thanks for your report. I can confirm the behavior - and yes, you are right this a quite serious problem (and also related to #1495 but not exactly a duplicate).

Regards
Matthias

@matthiasgeiger matthiasgeiger added the bug Confirmed bugs or reports that are very likely to be bugs label Aug 29, 2016
@koppor koppor closed this as completed in cf5224b Dec 11, 2016
@koppor
Copy link
Member

koppor commented Dec 11, 2016

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/master and report back if it works for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs groups
Projects
None yet
Development

No branches or pull requests

4 participants