188BET靠谱吗New PDF annotations: inclusion into Zotero RDF export and import
Thank you very much for the awesome new PDF annotation features.188BET靠谱吗I have a very basic question/feature request, namely the inclusion/support of the new annotations in Zotero RDF exports/imports.188BET靠谱吗I am one of the few remaining users of Sente (long discontinued), which used the same approach as the new Zotero annotation feature.188BET靠谱吗With a Zotero RDF mapping, I could write XSLT that allows to move all data from Sente to Zotero.188BET靠谱吗Export as part of Zotero RDF, which, to my knowledge, is the most complete export format, would help in every scenario that involves moving data from Zotero to another application.
I don't know if there are any plans to add the annotations to an output format other than the API, but it'd both be a lot of work and make exports massively larger, both of which seem problematic, so I'd be surprised.
Sorry for the late reply and thank you very much for your response, which clarifies the issue somewhat.I am not sure I would completely sign up for this envisioned way of data transfer by way of embedding annotations into the PDF upon export.Let me explain why:
1.188BET靠谱吗If annotations are transferred between multiple Zotero libraries via embedding in the PDF they will not be editable in the target library as opposed to the source library.Quite commonly, however, I will want to further edit my notes with comments, tags etc.(i.e.188BET靠谱吗all the new and awesome features of the built-in Zotero viewer).
2.188BET靠谱吗There is no clean PDF in the target Zotero library for sharing with others without additional processing of the PDF.
3.188BET靠谱吗Very different from these issues is my approach of moving references into Zotero from another reference manager (Sente) by means of user-generated Zotero RDF.188BET靠谱吗If the annotations were included in Zotero RDF, I could transform the Sente XML, which does included annotations to PDF, accordingly.
2.I think dstillman has mentioned that they're thinking about ways to allow "extract & remove" for native pdf annotations, which would take care of this concern.
So
3.Is the only significant use case left, and if you're looking at a scripting solution anyway, it's not clear that going through the API vs.a static output file is actually worse.