風Feng_Yijing_Dao

In the double-chain notes, my new and old card note processing flow#

Demo Archive - 2021-11-10 || [[✍Notes_Lv Jiangtao's Efficient Information Management Art in 20xx]]#

My old card note flow#

• Inspiration + Other Card Boxes
  • #Fleeting and ZKCards, use both tags together
  • Try to convert individual #Fleeting content to #toProject or deprecate it [[Deprecation]]
  • Convert what I have learned to #ZK or the independent aggregation tag ZKCards #Fleeting
• Permanent note card box ❌
  • No dedicated design, directly use the #ZK tag, and treat the content with the #🧩REF tag as a permanent card
• Overall structure
  • Excerpted block quotes
    • Question + various tags
      • Answer
      • Examples (may or may not exist)
      • Pointing to other notes (may or may not exist)
    • ❓Q: What is digital literacy? #ZK
      • In the era of information explosion on the Internet, it refers to the ability to handle and produce overload information, which is the ability of information management.
  • ❓Q: When capturing information, what is the process of using projects to enhance sensitivity? ZKCards
    • In most fields, it is a process from not understanding at all, to gradually perceiving some changes, to finally being able to control the core part and promote the development of things. This process is called sensitivity to projects, which means finding the feeling.
    • [[🌰]] It's like I've been learning the UE engine recently. Although I'm not changing careers, I used to develop 2D mobile games. But the difference brought by the tools is very big, the language and mechanism are different, but by playing with it, learning it, I gradually began to find the feeling.
    • [[🌰]] It's like learning to play basketball. At first, I played blindly, but later I found the feeling and my shooting percentage increased significantly.

The problem for me in the old card note flow is: too much information display, fuzzy edges, and increased cognitive burden.#

• There is no dedicated permanent note card box, and the judgment standard is not clear and convenient based on whether there is a #🧩REF tag.
  • There is no problem after making it, but judgment is required, which is not intuitive enough.
    • sm standardization, some #🧩REFs are not filled in, and some do not have references.
  • It will be cumbersome to make.
• Although ZKCards and #Fleeting are differentiated by color, it is not clear enough when there are many of them, and I want to improve it further.
• When clicking on a reference, I can see the original text and the specific content pointed to by the #🧩REF, but what I care about is only the original text, which is the source of information, and other information is disturbing items for me when viewing card notes.
• If I review and modify cards in RR, instead of using spaced repetition software such as Neuracache, Anki, and SuperMemo, there is too much information displayed for me. I only want to see the question and answer cards, without the need for contextual environment, to ensure that my cards adhere to the principle of minimal information.
  • When I see the original text and the question and answer cards displayed at the same time, I may think that I already understand it, and subconsciously think that the card is already simplified to the minimum, and I will only read it briefly and skip the modification, unable to further refine it.
  • This is the disadvantage of abusing the benefits and convenience brought by double-chain notes to my further thinking. Because this is handing over the judgment power to my own will at that time, rather than forcing it with a process.
    • Question-driven card notes, when I see a question, if I don't have an answer, I will instinctively answer it.
• In my tag design, keywords for projects, articles, and books are capitalized words, such as themes and domains, starting with capital letters, and keywords for specific tasks and card notes are lowercase words, such as usage scenarios and associations, starting with lowercase letters.
  • When I make #🧩REF tags directly through block quotes, I can directly see the specific scenarios, but I lack a summary view like the big words that summarize the themes.

New card note flow V1.0 under design#

• Solve the problems in the old card note flow
  • Although ZKCards and #Fleeting are differentiated by color, it is not clear enough when there are many of them, and I want to improve it further.
    • Solution: Visual processing: add breathing or blinking animation to give me the feeling of thinking, and link it with #Fleeting.
  • There is no dedicated permanent note card box, and the judgment standard is not clear and convenient based on whether there is a #🧩REF tag.
    • Solution: Add an Evergreen card box.
  • If I review and modify cards in RR, instead of using spaced repetition software such as Neuracache, Anki, and SuperMemo, there is too much information displayed for me. I only want to see the question and answer cards, without the need for contextual environment, to ensure that my cards adhere to the principle of minimal information.
    • Solution: Segment the usage scenarios, and see different levels of information in different views, see the design below for details.
  • In my tag design, keywords for projects, articles, and books are capitalized words, such as themes and domains, starting with capital letters, and keywords for specific tasks and card notes are lowercase words, such as usage scenarios and associations, starting with lowercase letters.
    • Solution: Elevate blocks to pages, establish links between the two, and decouple them.
  • When clicking on a reference, I can see the original text and the specific content pointed to by the #🧩REF, but what I care about is only the original text, which is the source of information, and other information is disturbing items for me when viewing card notes.
    • Solution: [[[[EVD]] - Block quotes in RR will not appear in reverse links, and further clicking is required for querying]]
    • 1. Technically, add filtering function to references ❌ (troublesome, requires writing JavaScript code, affects performance, and I don't need it elsewhere)
    • 2. Upgrade block quotes to page quotes ✅ (simple, try to implement it using native methods)

• Separate the processes of standardized storage and card note processing artificially#

  • In the old design, there is no clear boundary between the two, and they belong to a fuzzy category, with a large amount of mutual penetration.
  • The problem is that standardized storage is a series of procedural data, and it is a good thing to have backups and redundant data. Card note processing should reduce the cognitive burden as much as possible, and all influencing factors should be hidden.
  • ==What I want to achieve is decoupling, unable to directly modify the original function (explained in computer terms)==
  • Standardized storage: Clear and visible source, clear at a glance, easy to trace the source
  • Card note processing: Convenient for judging whether the card meets the standard for being placed in the permanent card box

• Segment the usage scenarios for card note processing and artificially create different views, the core idea is to trouble myself in different scenarios and add one or two more steps of operation#

  • When making the initial card#

  • Card refinement & simplified review#

  • Create permanent notes and put them in the card box#

• Comparison of the current old and new card note flows#

  • Views (I call visually intuitive usage scenarios views)#

    • Overall notes view for projects, books, etc.
      • Block quote cohesion, excerpt and question and answer
    • Excerpt view
    • Card view ZKCards
      • Add, delete, and modify cards
    • Evergreen card box view [[🧩REF]]

Future ideas#

• Bind themes and numbers tightly through naming rules and the characteristics of double chains
• ==If the bug in the discourse graph has been fixed to a usable level, start using it to complete the refactoring==
  • Places where the ideas align with mine
    • Naming philosophy
    • Block quotes ➡️ Page quotes
    • Managing links
  • Better aspects
    • Automation of link pointing
  • ==Reduce the effort spent on managing links==