Upgrade StorageRIS-Import incomplete
Dear Zotero-Forum,
we wan’t to import our old Database (~3.500 titles) in RIS-format from "Lidos" (Vers. 7.1) into Zotero. Unlfortunatly the import is incomplete. The lines
ID –
CY –
PB –
N2 –
are missing in Zotero and have to be enter by hand. Is there a way to make sure, these informations won’t get lost while importing the .txt-files into Zotero?
2nd: our former tags are coded separately with
N1 –
or splitted by semicolon (;). When importing the files, all N1-informations are transfered automatically into seperate notes but not into tags. Is there a faster option to convert the single notes into single tags then copy&paste them by hand?
3rd.: umlauts (ä, ü, ö, ß, á, è, …) in words cannot be imported, Zotero is marking them with an ?
How do we adjust the font (Zeichensatz) into ANSI during the import-process?
Hope somebody can help us! Many thanks in advance!
Best
Anne
we wan’t to import our old Database (~3.500 titles) in RIS-format from "Lidos" (Vers. 7.1) into Zotero. Unlfortunatly the import is incomplete. The lines
ID –
CY –
PB –
N2 –
are missing in Zotero and have to be enter by hand. Is there a way to make sure, these informations won’t get lost while importing the .txt-files into Zotero?
2nd: our former tags are coded separately with
N1 –
or splitted by semicolon (;). When importing the files, all N1-informations are transfered automatically into seperate notes but not into tags. Is there a faster option to convert the single notes into single tags then copy&paste them by hand?
3rd.: umlauts (ä, ü, ö, ß, á, è, …) in words cannot be imported, Zotero is marking them with an ?
How do we adjust the font (Zeichensatz) into ANSI during the import-process?
Hope somebody can help us! Many thanks in advance!
Best
Anne
2. Keywords should be KW - not N1 - Zotero will add tags that are each delimited by KW - _or_ a single KW - delimited by commas. Semicolons won't work, I'm afraid.
3. You can try to set import character encoding to Western in the Export tab of the Zotero preferences, but auto detecting the charset should usually work, so this suggests something might be amiss. It might be better to try to find a way to properly encode the document in UTF-8 with a dedicated tool.