![]() ![]() Question 1: How to fill “creatιondate” of old library entries with their “Timestamp” value massively? (or vice versa: fill “timestamp” of new entries with the value of “creationdate” field? ![]() I did not realize that “creationdate” is a new field. I was confused because I was expecting the “Timestamp” field to be created as in older versions. & 3) Indeed “creationdate” field IS generated for new entries. Will also try importing xmp pdf, thanks for this suggestion! Entries for all pdfs are created.Įven if entries miss information, most of the times the DOI field is ok, so then it is easy to proceed specific entries one by one. Thanks Christoph & ThiloteE for your help. Sorry for posting multiple issues in a single post. In Jabref 5.5, when selecting multiple entries>right click>Change entry type, only the first entry changes. In previous Jabref versions we could change “EntryType” for multiple entries at once. If I ignore it and press OK, then a timestamp is added to the next entry and the popup appears again and so on… Use “Menu>Edit>Manage field names & content” to manually add the timestamps: A timestamp is added to the first entry only and an error message pops up with an exception. When a new entry is created from DOI, the timestamp is successfully created but only with date information (no time info as in previous versions). Is this an expected behavior? I think that since an entry is created even by parsing a pdf, it should be timestamped. “Add timestamp to new entries (field creationdate)” is ticked. No timestamp is created for the created entries. A workaround is to add files one by one but it takes more time. I cannot identify which file forces the entry creation to stop. Same behavior with Shift F7 and with different group of files. Nothing happens for the rest of the files, no warning message appears. Only some of the expected entries are created. Working scenario: I drag n drop several pdf files (let’s say 5-10) in the user interface in order to import them and automatically create the corresponding entries. I noticed a couple of issues in Jabref 5.5 portable (win10/64bit) and I need your help to identify whether these are bugs or expected behavior. ![]()
0 Comments
Leave a Reply. |