23 Matching Annotations
  1. Sep 2022
    1. The notes from each document are entered upon aloose leaf furnished with the precisest possible in-dications of origin. The advantages of this artificeare obvious : the detachability of the slips enablesus to group them at will in a host of different com-binations ; if necessary, to change their places : it iseasy to bring texts of the same kind together, andto incorporate additions, as they are acquired, in theinterior of the groups to which they belong. As fordocuments which are interesting from several pointsof view, and which ought to appear in several groups,it is sufficient to enter them several times over ondifferent slips ; or they may be represented, as oftenas may be required, on reference-slips.

      Notice that at the bottom of the quote that they indicate that in addition to including multiple copies of a card in various places, a plan which may be inefficient, they indicate that one can add reference-slips in their place.

      This is closely similar to, but a small jump away from having explicit written links on the particular cards themselves, but at least mitigates the tedious copying work while actively creating links or cross references within one's note taking system.

  2. Aug 2022
    1. While Heyde outlines using keywords/subject headings and dates on the bottom of cards with multiple copies using carbon paper, we're left with the question of where Luhmann pulled his particular non-topical ordering as well as his numbering scheme.

      While it's highly likely that Luhmann would have been familiar with the German practice of Aktenzeichen ("file numbers") and may have gotten some interesting ideas about organization from the closing sections of the "Die Kartei" section 1.2 of the book, which discusses library organization and the Dewey Decimal system, we're still left with the bigger question of organization.

      It's obvious that Luhmann didn't follow the heavy use of subject headings nor the advice about multiple copies of cards in various portions of an alphabetical index.

      While the Dewey Decimal System set up described is indicative of some of the numbering practices, it doesn't get us the entirety of his numbering system and practice.

      One need only take a look at the Inhalt (table of contents) of Heyde's book! The outline portion of the contents displays a very traditional branching tree structure of ideas. Further, the outline is very specifically and similarly numbered to that of Luhmann's zettelkasten. This structure and numbering system is highly suggestive of branching ideas where each branch builds on the ideas immediately above it or on the ideas at the next section above that level.

      Just as one can add an infinite number of books into the Dewey Decimal system in a way that similar ideas are relatively close together to provide serendipity for both search and idea development, one can continue adding ideas to this branching structure so they're near their colleagues.

      Thus it's highly possible that the confluence of descriptions with the book and the outline of the table of contents itself suggested a better method of note keeping to Luhmann. Doing this solves the issue of needing to create multiple copies of note cards as well as trying to find cards in various places throughout the overall collection, not to mention slimming down the collection immensely. Searching for and finding a place to put new cards ensures not only that one places one's ideas into a growing logical structure, but it also ensures that one doesn't duplicate information that may already exist within one's over-arching outline. From an indexing perspective, it also solves the problem of cross referencing information along the axes of the source author, source title, and a large variety of potential subject headings.

      And of course if we add even a soupcon of domain expertise in systems theory to the mix...


      While thinking about Aktenzeichen, keep in mind that it was used in German public administration since at least 1934, only a few years following Heyde's first edition, but would have been more heavily used by the late 1940's when Luhmann would have begun his law studies.

      https://hypothes.is/a/CqGhGvchEey6heekrEJ9WA


      When thinking about taking notes for creating output, one can follow one thought with another logically both within one's card index not only to write an actual paper, but the collection and development happens the same way one is filling in an invisible outline which builds itself over time.

      Linking different ideas to other ideas separate from one chain of thought also provides the ability to create multiple of these invisible, but organically growing outlines.

    1. After theactual note is written and the blueprints are removed, on each of the three cards one keywordis underlined with a pencil or a red pen so that each card can be placed inside the box basedon its underlined keyword

      This works, but I'm a bit disappointed at this advice/revelation...

    2. carbon paper process

      I wasn't expecting advice for creating multiple copies of cards with carbon paper...

  3. Jun 2022
    1. Index

      I'm guessing it's just the fact that I have an advance reader copy of the book that accounts for the missing index in my copy.

      If not, then dear G-d!!!

    Tags

    Annotators

  4. Apr 2022
    1. Another papyrus, recovered in Toura, Egypt, contains notes taken on apolemical work by the church father Origen (185–254), including both faithfulexcerpts of varying lengths and notes made by abridgment from his AgainstCelsus.1
    2. We have, forexample, some notes and drafts of treatises by the Epicurean philosopher Philo-demus (110–40 BCE) preserved under seventy feet of volcanic ash at Hercula-neum.
  5. Dec 2021
    1. Deeply importing Svelte components is not supported. Either import all components from one entrypoint, or always stick to deep imports, otherwise it could cause multiple instance of the Svelte library running.
  6. Sep 2021
  7. Mar 2021
  8. Jan 2021
  9. Nov 2020
    1. If I understand the problem correctly, just changing the imports to point to svelte/internal isn't enough because they could still point to different packages depending on how your components are bundled. It solved your specific issue, but if you had two completely unrelated Svelte components compiled to vanilla javascript bundled with Svelte, you'd still hit issues with mismatching current_component when using slots or callbacks.
    2. It sounds like another case of multiple svelte/internal modules? I think we need to look into reworking how svelte/internal keeps track of the current component since it breaks when mixing components not bundled with the app. It sounds like we need to find a way to pass Svelte's internal runtime state when instantiating components, since slots and callbacks end up mixing different svelte/internal together.
    1. As mentioned in #2937, this is the sort of thing that happens when you have two copies of Svelte's internal scheduler running. If you're importing the compiled version of an external Svelte component into another Svelte component, this is what you end up with. There's a svelte field in package.json that's respected by rollup-plugin-svelte and which is intended to point at the uncompiled Svelte source, so that the external component can be bundled together with the main app, without any duplicated internals.
    1. The resolve.alias option is used to make sure that only one copy of the Svelte runtime is bundled in the app, even if you are npm linking in dependencies with their own copy of the svelte package. Having multiple copies of the internal scheduler in an app, besides being inefficient, can also cause various problems.
  10. Jul 2020
  11. Sep 2018
  12. Nov 2016
    1. Comme pour les autres manuscrits, il ne s’agit pas d’une version originale du récit mais bien une copie d’une version antérieure.

      Quels indices ont permis d’affirmer qu’il s’agit de copies?