You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While seeing that diff, I thought, something is really wrong:
The semicolon on position 1 indicates that multiple meta data items are can be written into @Comment. This was clear to me today (and not in 2016 #960). This would be great as this would minimize the number of @Comment entries. However, the saveActions also use ; as delimiter (position 2).
The "feature" of non-merging the meta fields is long time present. See e.g., an old issue report #250.
Thus, a straight-forward merge is most probably not possible.
Code hint: Separation according to ; is done at org.jabref.logic.importer.util.MetaDataParser#getNextUnit
Bad, because the parsing logic needs to be written for the content inside
JSON at the end of the file
New entries always start with @. Anything outside the “argument” of a “command” starting
with an @ is considered as a comment. This gives an easy way to comment a given entry: just
remove the initial @. As usual when a language allows comments, don’t hesitate to use them so
that you have a clean, ordered, and easy-to-maintain database. Conversely, anything starting
with an @ is considered as being a new entry
@Article{demo,
note={just an example article to illustrate the **previous** entry}
}
// jabref-meta-0.1.0
{
"saveActions" : {
"state": true,
"date": ["normalize_date", "action2"],
"pages" : ["normalize_page_numbers"],
"month" : ["normalize_month"]
}
}
The text was updated successfully, but these errors were encountered:
koppor
changed the title
jabref-meta storage in bib file should be improved
jabref-meta storage in bib file should be improved (by switching to embedded JSON)
Jul 3, 2024
Context
While seeing that diff, I thought, something is really wrong:
The semicolon on position 1 indicates that multiple meta data items are can be written into
@Comment
. This was clear to me today (and not in 2016 #960). This would be great as this would minimize the number of@Comment
entries. However, thesaveActions
also use;
as delimiter (position 2).The "feature" of non-merging the meta fields is long time present. See e.g., an old issue report #250.
Thus, a straight-forward merge is most probably not possible.
Code hint: Separation according to
;
is done at org.jabref.logic.importer.util.MetaDataParser#getNextUnitCall for new metadata storage
Single JSON in @comment field
Example:
Content:
Decision outcome: Use "Single JSON in @comment field"
Migration path:
After this is implemented, we can work on #8701
ADR
Single JSON in @comment field
@Comment
element is enoughMultiple JSON
Each preference could have a separate JSON nesting.
BibTeX
Example (From koppor#232)
old:
new:
normalize_date, action2
) is a custom format.@comment and then nested
JabRef v5.9 (and before) used that format.
JSON at the end of the file
New entries always start with @. Anything outside the “argument” of a “command” starting
with an @ is considered as a comment. This gives an easy way to comment a given entry: just
remove the initial @. As usual when a language allows comments, don’t hesitate to use them so
that you have a clean, ordered, and easy-to-maintain database. Conversely, anything starting
with an @ is considered as being a new entry
The text was updated successfully, but these errors were encountered: