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

Serialization of groups in entry #629

Closed
tobiasdiez opened this issue Jan 3, 2016 · 3 comments
Closed

Serialization of groups in entry #629

tobiasdiez opened this issue Jan 3, 2016 · 3 comments
Assignees
Milestone

Comments

@tobiasdiez
Copy link
Member

Currently the manual groups are written to the bib file as a jabref comment at the end of the file. I was thinking about changing this to an inline serialization similar to the keywords fields. That is, as groups={mygroup1, mygroup2} in the entry.

This would have the following advantages:

  • One could easily see the groups an entry belongs to and could change them by hand. Related SF 868 and SF 750
  • The group information is accessible in latex (very easy with biblatex).
  • Copying an entry to different db keeps group assignment (if group exists in new db). Related SF 756
  • Allows to search for group memberships in the search bar (would solve SF 681).
  • The logic for filtering by groups can be completely replaced by the search functionality.
  • It would work also for entries without bibkey (ok not a big achievement) and there is no logic required if the bibkey is changed (but the very same code is required for group renames).

But since there were quite a few discussions recently about how to serialize the database I want to asked about your opinions before investigating time into this :).

@koppor
Copy link
Member

koppor commented Jan 3, 2016

My first thought: This contradicts #574. I always have sharing in mind. On the one hand, when sending a bibtex entry, I don't want to send internal fields such das __markedentry. On the other hand, data such as groups or keywords belong to an entry and are not external to it.

Maybe, we have to add a functionality "copy entry without personal data to the clipboard".

@koppor
Copy link
Member

koppor commented Jan 3, 2016

Refs #628

@lenhard
Copy link
Member

lenhard commented Apr 27, 2016

Implemented by #1276

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants