- #Link to specific node in docear from a document word Offline#
- #Link to specific node in docear from a document word series#
What makes me nervous is that the "cut" portion of the use case happens outside FP.
#Link to specific node in docear from a document word Offline#
Super ideally, the user would also be able to capture an image of the webpage for offline or historical use (in case the webpage "goes away" or morphs over time). Ideally, image capture and paste would be supported as well. The user selects one of the choices (or creates a new one, if needed) and Freeplane "pastes" the data into the appropriate container, creating any necessary new attributes if not already there. As these cuts are made (either in turn or at the conclusion of the capture session, whichever is easier to implement), FP would offer the user a choice of where to paste the cut information (node, associated URL, details, notes or existing/new attribute) similar to the way filter chooser currently works.
#Link to specific node in docear from a document word series#
Use case would work something like this: User would capture data while at a web page in a series of "cuts" into a system clipboard similar to the way the utility Ditto works. I'm interested in expert opinion about how difficult it would be to incorporate some sort of universal data gathering tools into regular implementations of Freeplane.
"Published Date," etc.) Also it's tedious: cut in browser, navigate back over to FP, open appropriate node, create attribute, paste, go back over to web for more information on the same topic. It's hard to remember which attributes I've established already ("Publication date" vs.
Typically I store this sort of data in a combination of standard node containers and associated attributes for later search and retrieval.īut capturing individual bits of information and shoving them into one or more potentially large number of attributes is unwieldy. Obviously a Title, perhaps a description, the URL, the date of the material, the date captured, type of material (webpage, video, picture, article, review, etc) as well as any notes I might want to include, keywords, etc. But I'm finding that I often want to capture more about the information than just the "target" pieces. Certainly I can cut data from a web page and paste it into a node container relatively simply. Given that reality, it seems to me that there is a natural use case associated with gathering and storing data quickly, similar to the way we capture information for a bibliographic exercise in the academic world but without the complexity associated with Docear. Much (if not all) of modern research is done digitally. And, it's a separate platform, evolving at different pace than the larger body of Freeplane development. The complexity keeps people from using it for any data gathering short of a doctoral thesis. It represents a steep learning curve for the person that is interested in researching options for a new motorbike. Many of the tools are arcane to anybody outside academic research. I know that DOCEAR does much of this, but I've always been confused about the fork there. At the end of it all, I often will need to document my conclusions with what looks like a simple bibliography. The process is always the same: Gather data, sort it into some sort of reasonable pattern that will move those details into a pattern of knowledge (converting it to information), all the while, analysing what has been collected for fit and determining where there are still gaps that require additional research. Doesn't matter if it is for a potential publication that I'm going to write or the development of a list of camping equipment. One of my primary uses for Freeplane is the combination of research and organization of information.
0 kommentar(er)
