The concepts above will be handled by the following packages. Storage Not actually part of the workflow in the same way, since it will be handled at the system level, it is worth nothing, that in this workflow Zotero is used to export a master bib file and keeps it updated, while the notes themselves are version controlled 5. Backlinks In particular, by backlinks at this point we are referring to the ability to link to a pdf or a website with a unique key such that notes can be added or removed at will. In particular, it would be nice to be able to visualize the flow of ideas, each represented by a note. Contextual Representation This aspect of the workflow deals with representations, which should transcend the usage of tags or categories. The search interface must then simply allow us to narrow down our candidates in a meaningful manner. It is assumed that there will be many notes, and that they will have a wide variety of content. This then requires a separate system forĮach which is described by: Search Engine The search engine is key, both in terms of accessibility and scalability. The idea is to be able to create notes for all kinds of content. Zotero This is what I personally use and recommend. The fact that it is Java based was a major issue for me. Jabref This is fun, but really more of a per-project management system, but it works well for that. Sadly, the price tiers aren’t very friendly so I have to give it a hard pass. The options most commonly seen are: Mendeley This is a great option, and the most mobile friendly of the bunch. Reference management is one of the main reasons to consider a plain-text setup, and mine is no different. So the basics of the ideology are listed below. Workflow I want, and then implement it, instead of relying on the cannedĪpproaches of each package. While working through ideas, it actually was more useful to describe the
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |