Markdown was born as a text-to-html tool. Finally DT's ability to encrypt your data and share it with another DT installation on another is invaluable for having all your zettels on all your machines, even iOS.Īs an aside, I'm not on the markdown bandwagon. DT OCRs pictures which means that notes scanned in are also searchable. Entering notes is dead easy and so is getting you information out should you decide to move it elsewhere. You can however, follow note links and just move from note to note. It also speeds up linking.ĭT's search is phenomenal and this alone is great for a ZettelKasten. This is great when you write a title and realise you already have a note with that name because it turns into a link. If you use rich text you can set DT to automatically link to notes of the same title as your text. DT functionality is actually focused on rich text. Create a template for your zettels so you maintain consistency By that I mean to use and to replicate to other computers you need the data on.ģ. I've used a number of systems over the years, but DT is probably the easiest. This satisfactory emotion may not be the best of guides, though. In short, I think the feature of semantic search is always interesting because it's surprising and non-deterministic (for us). It's the Zettelkasten's effect of surprise, but sooner, because the algorithm does its job in its own way automatically, all the time, while the manual approach produces more surprise if you put in more work. Even if you have a knack for backwards-engineering an algorithm to find out which are its triggers, "semantic search" will always be ahead of your ability to foresee the results. The thing with any artificial intelligence is that it's sufficiently complex to be opaque to humans (at first), and thus becomes an interesting puzzle. if this is actually producing better results. In any case, the semantic search suggestions were interesting inasmuch as they were different from the search results nvALT brought up, but I didn't have a project back then and couldn't evaluate if this difference was making a difference (pardon the Bateson pun ), i.e. I don't know if that limitation is still in effect. Which, of course, is a bad sign in terms of "have I processed this PDF file fully?" But not all work is about processing files I'm not a historian, but historians using DT seem to put tons of stuff into their databases at lightning speed to build a reference file.īack in the day, DT could index an external folder but then could not keep up with the changes automatically. If you need to search the full-text much later. Using DT as a more sophisticated literature and reference manager sounds like a beneficial use to find files in large collections again. Seriously, though, I'm asking Marko (author of the DEVONthink review) to chime in with some info. Well, No, Jeremy, you don't need DevonTHINK just read the documents, take notes on them, put those notes, processed appropriately with citations, into a Zettelkasten and find links and add tags manually. What I'd really love to hear, of course, is something along the lines of: 'No, Jeremy, you don't need DevonTHINK just read the documents, take notes on them, put those notes, processed appropriately with citations, into a Zettelkasten and find links and add tags manually. Does anyone else have any experience of using DevonTHINK with a Zettelkasten (the latter stored separately), or any views on how it might work (or not work)? Christian has already raised the issue of DevonTHINK's 'smart' search features being a replacement for manual, 'hands on' searching and link-making, with all that this entails for automation dangers and so on (forgive me if I'm misrepresenting your view here, Christian). I'm thinking in terms of using the former for document storage and archiving, and the latter for notes. I'm just wondering about the ways in which DevonTHINK and a plain-text Zettelkasten via nvALT/The Archive might work together.
0 Comments
Leave a Reply. |