![]() No wonder when the developer offers his time to strangers trying to import stuff into bookends (No offence! I really appreciate it, but speaking from experience, I see some procrastination going on here…) But looking at the progress history, I wasn’t too optimistic about when it will be released. I haven’t gotten down to testing bookends import yet (currently testing Zotero import) but I suspect that I would end up importing that Citavi XML to bookends and if I do, it’s good to know I can ask you stuff (really appreciate it) but to be honest: I just noticed (by looking at your homepage) that you’re the developer of keypoints and I’d much rather have you work on that… When I discovered it a couple of weeks ago, I was thrilled and knew immediately that this is what I want. Not sure whether it’s the same as the Citavi XML that you’re referring to but I suppose so.Īctually, bibtex might also be an option because bibtex export is heavily customizable in Citavi, but even if it goes as far as letting me include my quotes, it would then still require a custom import on the other side, so I’m not sure how much work can be saved going down that path. There is probably a good reason why the guy who wrote the Citavi to Zotero export translator is not using any of the official export formats but rather Citavi’s backup file (which is a zipped XML file. In fact, I don’t even know whether the endnote formats do. My impression is that either endnote XML or ENL are the only real options here because the others don’t support quotes/comments. Alternatively, it‘s definitively worth asking in the Citavi and/or Bookends forums about your specific issue. I could help you with this but my time is unfortunately pretty limited right now. Maybe you could try one of the standard exchange formats (like EndNote XML) first, and then only use a script to pick missing data from the Citavi XML. But one would need to write a script to import this into Bookends. This likely would be the most data-rich format. I remember that Citavi also offered its own (Citavi XML) exchange format. Otherwise, it should be possible to open the Citavi export file in a text editor and change all attachment paths to the path of the Bookends attachments folder. I’m not sure but if you copy your PDFs into the default Bookends attachments folder, Bookends may even be able to auto-match them. IIRC, the EndNote XML format should be supported well by Bookends. RIS doesn’t appear to be the best choice. I‘d try out each of the export formats supported by Citavi and see which is the most lossless. ![]() Alternatively, you could also batch-delete multiple groups via scripting. To batch delete multiple user-created groups in Bookends, select them all (via shift-click) in the source list, then hit the Delete key and press “Delete” in the displayed dialog. ![]() ![]() Bookends offers a “Find A Group…” command (available from the source list’s contextual & cog wheel menus) which will select the first matching group.Will these apps leave things to be desired? For sure! But both can be scripted to fine tune to your needs (though I think, on a Mac, AppleScript automation is easier and also works between different apps). And both apps have been (and likely will be) supported long-term (Bookends even since 1984!). Overall, and ignoring their individual idiosyncrasies, I think that both Bookends and Zotero are robust apps with sound support. So there’s often technical challenges that the user isn’t (and shouldn’t need to) be aware of. This is since Bookends is a Xojo app which, by default, only supports raw AppleEvents but not AppleScript. As an example, adding fully featured AppleScript support to Bookends (which I helped to implement/design) wasn’t easy. Also, feature requests that may seem straightforward to implement from the outside often aren’t easy at all, and may technically be very challenging to implement. For a developer, it’s often very tricky to balance individual user requirements/wishes with the overall goals of the app and its target user group. Personally, I wouldn’t dismiss an entire app based on some public support threads. However, I’ve also worked for Papers (pre ReadCube) and (as a contractor) for Bookends, and I can attest that the people behind these tools were/are very much dedicated to develop sound reference management solutions. software capabilities and quality of support (I could experience this first hand when I worked for them to bring Citavi to the Mac – the project was eventually abandoned in favour of the Citavi web version). Note that coming from Citavi sets a very high bar w.r.t.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |