More things should enable tags...

reply to u/JonasanOniem at https://www.reddit.com/r/Zettelkasten/comments/16ss0yu/linking_new_notes/

This sort of practice is harder when you start out in most digital apps because there is usually no sense of "closeness" of ideas in digital the way that is implied by physical proximity (or "neighborhood") found in physical cards sitting right next to or around each other. As a result, you have to create more explicit links or rely on using tags (or indexing) when you start. I've not gotten deep into the UI of Zettlr, but some applications allow the numbering (and the way numbered ideas are sorted in the user interface) to allow this affordance by creating a visual sense of proximity for you. As you accumulate more notes, it becomes easier and you can rely less on tags and more on direct links. Eventually you may come to dislike broad categories/tags and prefer direct links from one idea to another as the most explicit tag you could give a note . If you're following a more strict Luhmann-artig practice, you'll find yourself indexing a lot at the beginning, but as you link new ideas to old, you don't need to index (tag) things as heavily because the index points to a card which is directly linked to something in the neighborhood of where you're looking. Over time and through use, you'll come to recognize your neighborhoods and the individual "houses" where the ideas you're working with all live. As an example, Luhmann spent his life working in sociology, but you'll only find a few links from his keyword register/subject index to "sociology" (and this is a good thing, otherwise he'd have had 90,000+ listings there and the index entry for sociology would have been utterly useless.)

Still, given all this, perhaps as taurusnoises suggests, concrete examples may help more, particularly if you're having any issues with the terminology/concepts or how the specific application affordances are being presented.

Las etiquetas son altamente importantes en la actualidad para asegurar también la búsqueda rápida de los contenidos. Por esto considero que es lo que más me gusta de Hypothes y su apuesta por la lectura anotada y compartida.

Tags are kind of like a link to important words or phrases to make reviewing your notes quicker.

Testing 3 using tags

Dit is een test. Voorstel voor aanpassing: behandeling van de dunne mestfracties

Jon Udell's Tag Rename tool for Hypothes.is.

https://forum.obsidian.md/t/group-tasks-by-page-tags-using-dataview/47354/2

A good description of tags in Obsidian and how Dataview views them at the YAML, page level, and task level.

Sorry, I'm only just seeing this now Jan. I tag a lot in Hypothes.is to help make things a bit more searchable/findable in the future. Everything in Hypothes.is gets pulled into my Obsidian vault where it's turned into [[WikiLinks]] rather than tags. (I rarely use tags in Obsidian.) Really I find tagging is better for broad generic labels (perhaps the way many people might use folders) though I tend to tag things as specifically as I can as broad generic tags for things you work with frequently become unusable over time. I recommend trying it out for yourself and seeing what works best for you and the way you think. If you find that tagging doesn't give you anything in return for the work, then don't do it. Everyone can be different in these respects.

Mastodon has RSS feeds available for tags!

https://www.youtube.com/watch?v=g9QOHaAqhXc

https://www.loom.com/share/a05f636661cb41628b9cb7061bd749ae

Synopsis: Maggie Delano looks at some of the affordances supplied by Tana (compared to Roam Research) in terms of providing better block-based user interface for note type creation, search, and filtering.

---

These sorts of tools and programmable note implementations remind me of Beatrice Webb's idea of scientific note taking or using her note cards like a database to sort and search for data to analyze it and create new results and insight.

It would seem that many of these note taking tools like Roam and Tana are using blocks and sub blocks as a means of defining atomic notes or database-like data in a way in which sub-blocks are linked to or "filed underneath" their parent blocks. In reality it would seem that they're still using a broadly defined index card type system as used in the late 1800s/early 1900s to implement a set up that otherwise would be a traditional database in the Microsoft Excel or MySQL sort of fashion, the major difference being that the user interface is cognitively easier to understand for most people.

These allow people to take a form of structured textual notes to which might be attached other smaller data or meta data chunks that can be easily searched, sorted, and filtered to allow for quicker or easier use.

Ostensibly from a mathematical (or set theoretic and even topological) point of view there should be a variety of one-to-one and onto relationships (some might even extend these to "links") between these sorts of notes and database representations such that one should be able to implement their note taking system in Excel or MySQL and do all of these sorts of things.

Cascading Idea Sheets or Cascading Idea Relationships

One might analogize these sorts of note taking interfaces to Cascading Style Sheets (CSS). While there is the perennial question about whether or not CSS is a programming language, if we presume that it is (and it is), then we can apply the same sorts of class, id, and inheritance structures to our notes and their meta data. Thus one could have an incredibly atomic word, phrase, or even number(s) which inherits a set of semantic relationships to those ideas which it sits below. These links and relationships then more clearly define and contextualize them with respect to other similar ideas that may be situated outside of or adjacent to them. Once one has done this then there is a variety of Boolean operations which might be applied to various similar sets and classes of ideas.

If one wanted to go an additional level of abstraction further, then one could apply the ideas of category theory to one's notes to generate new ideas and structures. This may allow using abstractions in one field of academic research to others much further afield.

The user interface then becomes the key differentiator when bringing these ideas to the masses. Developers and designers should be endeavoring to allow the power of complex searches, sorts, and filtering while minimizing the sorts of advanced search queries that an average person would be expected to execute for themselves while also allowing some reasonable flexibility in the sorts of ways that users might (most easily for them) add data and meta data to their ideas.

---

Jupyter programmable notebooks are of this sort, but do they have the same sort of hierarchical "card" type (or atomic note type) implementation?

This discussion seems to miss the broader intellectual historical background of tags in prior generations. There's not even a nod to commonplaces, topic headings, subject headings, indices, etc.

Worth taking a look at the various affordances of folders vs. links vs. tags.

Some of these functionalities may be highly dependent on the particular tool in question and what affordances the tool allows for these ideas.

Has anyone done this comprehensively across a number of tools other than threads in fora like reddit, zettelkasten.de, etc.?

https://www.reddit.com/r/ObsidianMD/comments/vofakc/folders_vs_links_vs_tags/

Forte frames things primarily from a digital perspective so he talks about folders and tags, but seems to wholly forget the grand power of having an subject index. While they're broadly the same, it's as if he's forgoing two thousand years of rhetorical tradition to have something that seems new and innovative, but which are paths that are incredibly well travelled.

sparql PREFIX osmt: <https://wiki.openstreetmap.org/wiki/Key:> SELECT * WHERE { ?museum osmt:addr:city "New York"; osmt:tourism "museum"; osmt:wikidata ?wikidataID . }

cito--cites--1375511 says “this article CiTO:cites article 137511”.

Machine Tags

A new kind of tags — machine tags — are supported now. A machine tag, e.g. meta:language=python consists of a namespace (meta), a key (language) and a value (python). Everyone can created machine tags, but the meta: namespace is protected and tags in there will be created by the site itself.

The codesite itself uses machine tags to make various properties of recipes accessible to the search:

• meta:language

  The programming language of the recipe, e.g. python, perl or tcl.

• meta:min_$lang_$majorver

  Those tags describe the minimum language version. If a recipe requires Python 2.5 it would have the tag meta:min_python_2=5.

• meta:license

  The license that was selected by the author, e.g. psf, mit or gpl.

• meta:loc

  This tag contains a number describing the lines of code in a recipes. It counts only the number of lines in the code block but not any lines in the discussion of in comments. This makes it possible to search for short recipes with less than ten lines or very large ones.

• meta:score

  The current score of the recipe. This is the same number that is displayed besides the recipe title and can only be influenced by voting on recipes. That way you could even search for down-voted recipes

• meta:requires

  Stores information about additional requirements of the recipes, e.g. required python modules. You can find recipes using python's collections module that way.

All those tags cannot be changed directly because they are generated from a recipe's properties.

We also support machine tags that follow the pattern NAMESPACE:KEY=VALUE. For example: geo:lat=43.555 camel:size=medium machine:tag=with space Machine tags are not revealed to the user on the track pages.

These: Aus einer Umweltperspektive können wir auf die Räume schauen, in denen besondere Kreativität Platz findet/stattfindet. Diese Räume macht aus, dass sie ein Austausch für hunches sind - wie Johnson sagt. Für Ahnungen, Ideefragmente. Bspw. die Kaffeehäuser der Aufklärung. Ich denke wir haben heute zusätzlich die Möglichkeit Räume zu etablieren, in denen wir über Raum-Zeit-Grenzen hinweg ein mingling und colliding von hunches (auch mithilfe von Algorithmen und zB tags) vollziehen können.

• musicbrainz:artist=<MBID>
• musicbrainz:release=<MBID>
• musicbrainz:track=<MBID>
• musicbrainz:label=<MBID>

WL journaling with specific body parts or yoga methods in title

eg. padmasana as y-pdma planck as arm-p

Tagging dream journals with "my" tags

eg. my childhood, my schooling my collegemates, my pallipattu, my wife, etc

• astro:name=NGC 4565
• astro:orientation=11.73
• astro:RA=189.083922302

The metadata is structured. So structured that we can represent the example machine tags in a table:

<table> <thead><tr> <th style="text-align:center">namespace</th> <th style="text-align:center">predicate</th> <th style="text-align:center">value</th> </tr> </thead> <tbody> <tr> <td style="text-align:center">astro</td> <td style="text-align:center">name</td> <td style="text-align:center">NGC 4565</td> </tr> <tr> <td style="text-align:center">astro</td> <td style="text-align:center">orientation</td> <td style="text-align:center">11.73</td> </tr> <tr> <td style="text-align:center">astro</td> <td style="text-align:center">RA</td> <td style="text-align:center">189.083922302</td> </tr> </tbody> </table>

Or in a tree:

  astro
  |-- name
  |   `-- NGC 4565
  |-- orientation
  |   `-- 11.73
  `-- RA
      `-- 189.083922302

ALT tags are clear and consise. Giving a great explaination of the Image.

"Five three-dimensional stars are in a line, each rising taller than the previous."

https://hypothes.is/users/pmbillings01

notes

Referencia HTML

DIRECTORY (in progress): This post is my directory. This post will be tagged with all tags I ever use (in chronological order). It allows people to see all my tags, not just the top 50. Additionally, this allows me to keep track. I plan on sorting tags in categories in reply to this comment.

External links:

Tags categories will be posted in comments of this post.

This is a test annotation for the page.

使用标签，可以赋予我们的笔记更多的入口

Testing Annotaion text

inherit from: https://hyp.is/ntzyjnVpEeuLxrvf8MzCkA/trailblazer.to/2.1/blog.html

I'm glad. I didn't like that the book (which is essentially a form of documentation/tutorial) was proprietary.

I think it's better to make documentation and tutorials be community-driven free content

I suppose this is also an argument that Python tries to make? That other languages have this con:

• cons: closing tags make it more verbose / increase duplication and that Python is simpler / more concise because it uses indentation instead of closing delimiters like end or } ?

你好

It isn't rocket science, but as Jon indicates, it's incredibly powerful.

I use my personal website with several levels of taxonomy for tagging and categorizing a variety of things for later search and research.

Much like the example of the Public Radio International producer, I've created what I call a "faux-cast" because I tag everything I listen to online and save it to my website including the appropriate <audio> link to the.mp3 file so that anyone who wants to follow the feed of my listens can have a playlist of all the podcast and internet-related audio I'm listening to.

A visual version of my "listened to" tags can be found at https://boffosocko.com/kind/listen/ with the RSS feed at https://boffosocko.com/kind/listen/feed/

ttest

Since I didn't know which variant was canonical, I tagged with both/all variants. Gross.

Tags were used for discovery of specific types of content. Who needs that now that our new overlords of artificial intelligence and algorithmic feeds can tell us what we want to see?!

Of course we still need tags!!! How are you going to know serendipitously that you need more poetry in your life until you run into the tag on a service like IndieWeb.xyz? An algorithmic feed is unlikely to notice--or at least in my decade of living with them I've yet to run into poetry in one.

Đây là chú thích

We add the target property _blank to force the target file to open in a separate window or tab. Another common target is _self, which will open in the same tab, replacing the current page. Check out W3 Schools for more info on the target attribute.

test annot

This is where the Enlightenment, which thinks of divisions and categories as things discovered by the rational mind, is in trouble, because those rational minds start turning inward on themselves.

are these two really related?

The corresponding SIMBAD object can be found at -- http://simbad.u-strasbg.fr/simbad/sim-basic?Ident=WISE+J085510.83-071442.5

DV tools

Red Hat can you fix this?

This could be a series of tags determined by prof.

Each of these could be sets and then subsets of controlled tags input by teacher as part of course and used by students in their annotations throughout.

vấn

Sarah and David Wrobel's project here is so cool: they leveraged the Hypothes.is tag feature to have students explore the "layers" of John Steinbeck's The Grapes of Wrath. While the idea of such layers could perhaps be said about any literary text, for Steinbeck there was something explicit about the layers of that particular novel. As he wrote to his editor at the time:

"The Grapes of Wrath" was published, Steinbeck wrote: "There are five layers in this book, a reader will find as many as he can and he won't find more than he has in himself."

This is text annotation

I don't think it's just forgetfulness. Tagging requires exact resolution of an idea to a tag. But when doing exploratory reading, deciding on the correct tag to use is often difficult and time-consuming (and rarely consistent across time).

A tag recommender would be a cool extension.

adding info

Neat use of TAGS Explorer. Did do so, to interesting effects. Regular livetweet events may be more interesting. And there’s something to be said about NodeXL and COSMOS.

I would love to see a worthy successor to delicious. Is hypothesis it?

Altmetric guidelines for optimising web pages

This documentation describes the technology behind indexing of websites with scholarly articles in Google Scholar. It's written for webmasters who would like their papers included in Google Scholar search results. Detailed technical information is helpful if you're trying to fix an error in indexing of your own website, or you need to make sure that your article hosting product is compatible with Google and Google Scholar search services.

le eş ve kardeşleri boşalan yerlere talip oldu. AKP yönetiminin, milletvekili aday adaylığı için başvuran bu isimlerden sadece birkaçına vize vereceği iddia ediliyor.

this is really cool, actually.

Global context of tags to inherit for this document

I need a way to add tags to a document that will apply to all annotations in a particular document (except where explicitly canceled).

The problem is that I often want to query all annotations related to a specific document, collection of documents, or type of activity.

Type of activity requires further explanation: Given a document or collection of documents I may annotate the document for different reasons at different times.

For example, while annotating the reading materials, video transcripts, and related documents for the CopyrightX course there are certain types of annotations that may be "bundled together" so that when I search for those things later I can easily narrow my searches to just that subset of annotations; but at the same time I need a way to globally group things together.

While reading judicial opinions the first activity/mode of interaction with a particular document may be to identify the structure of the judicial opinion (the document attached to this annotation describes the parts of the judicial opinion I might want to identify: *caption, case citation, author, facts of the case, law of the case, disposition, concurring and/or dissenting opinions, etc).

The above-described mode I may use for multiple documents in one session related to the course syllabus for the week.

To connect each of these documents together I might add the tags: copyx (my shorthand for the name of the course, CopyrightX), week 1 (how far into the course syllabus), foundations (the subject matter in the syllabus which may span week 1, week 2, etc), judicial opinions (the specific topic I am focused on learning at the moment (may or may not be related to the syllabus).

Later on another day I might update my existing annotations or add new ones when I am preparing to study for an exam. I might add tags like to study, on midterm, on final to mark areas I need to review.

After the exam I might add more tags based on my test score, especially focusing on areas that received a poor score so I can study that section more or, if I missed some sections so didn't study and it resulted in a poor score in that area, add tags to study for later if necessary.

I have many more examples and modes of interaction in mind that I can explain more later, but it all hinges on a rich and flexible tagging system that:

• allows tagging a document once in a way that applies to all annotations in a document
• allows tagging a session once in a way that applies to all annotations in all documents connected to a particular session
• allows tagging a session and/or a document that bundles together new tags added to an annotation (e.g. tags for grammar/spelling, tags for rhetological fallacy classification, etc)
• fast keyboard-based selection of content
• batch selection of annotation areas with incremental filling-- I may want to simply select all the parts of a document to annotate first and then increment through each of those placeholders to fill in tags and commentary
• Mark multiple sections of the document at once to combine into a single annotation
• Excerpting only parts of a text selection, but still carry the surrounding textual context with the excerpt to easily expose the surrounding context when necessary
• A summary view of a document that is the result of remixing parts of the original document with both clarifications or self-containing summary re-writes and/or commentary from the reader
• structural tagging vs content tagging