About ten months ago, I followed the footsteps of Frederiko’s work and created the script . I “tried” to enrich the functionality, flexibility, and DT3 compatibility of his concept. The result is probably a mix.
The earlier version of “stack” script is my first long script, and it was complexed. I am hesitated to post an updated version. It is difficult(almost impossible) to debug this sort of script when users encounter problem/s unless they have a reasonably good knowledge of AppleScript and DT3, with good patience, and probably need Script Debugger.
This is a minor update (but a major work for me) that either will work smoothly or still be problematic (please don’t use it in such case). I am posting the script even though I won’t be able to provide support because I hope that in one day, some advance user/s may see the value of the underlying workflow, and is willing to write a better and more robust version. I even “dream” about DT to provide a standard script within the next few years. From DT’s aspect, they can produce similar outcomes by adding a few steps following the “summarise highlights” function (I think…).
To me, “Stack” is a workflow of knowledge management. The script creates a linked info-container for each focal document and allows users to extract and take note on a small segment of literature by creating a “card”. All cards from the same focal document are stored in the document’s stack. As each card only contains a portion of the literature, tagging can be more precise, and more accurate tags facilitate targeted retrieval of notes. Also, a supplementary script “stacklink” can create a two-way linkage between different documents(or cards) by replicating themselves into each others’ stack.
This post shows what the scripts do. I will find some time tomorrow to explain the configuration process and the scripts themselves. Noted that there are many options available, and those options can be configured without needing to know and change the script.
(1) I highlight a segment in a paper.
(2) I activate the script. The script asks for a name (can be configured to ask for adding comment, too).
(3.1 ) A card in MD format is created (can be configured to create rtf format). The selected text is also underlined or highlighted according to the user’s configuration.
(3.2) A list of tags is shown, including (1) suggested tags based on keywords matching (if another script “Tagger” is used together with “Stack” in DT3), and (2) the tags of the source socument, and (3) a list of constrained tags groups that is chosen by the user during the setup process.
(4) I activate “openstack” script (a supplement script). All cards within the document are shown.
(5) The paper use Kraatz and Block (2008) as one of its key citation. I want to read that paper later, too. I remember I have that paper and want to link it as the key citation of this paper. I activate the “stacklink” script.
The script asks for which document to link, and I search for it (in same DT databse only).
(6) A list of possible hits and choose the one I need.
(7) I open the stack of Kodieh and Greenwood (2013) and Kraatz and Block (2008) is in its stack, I open the stack of Kraatz and Block (2008) and Kodieh and Greenwood (2013) is in its stack.
Once again, I’m sure that there are 3rd party apps that that do that. But I like DIY.