# Role for MOCs in JD?

**URL:** <https://forum.johnnydecimal.com/t/role-for-mocs-in-jd/1745>\
**Category:** The Johnny.Decimal system\
**Created:** [August 17, 2024, 12:33am UTC](https://forum.johnnydecimal.com/t/role-for-mocs-in-jd/1745 "2024-08-17T00:33:42Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![PhillyChuck](https://forum.johnnydecimal.com/letter_avatar_proxy/v4/letter/p/f14d63/32.png) [@PhillyChuck](https://forum.johnnydecimal.com/u/PhillyChuck)\
**Post date:** [August 17, 2024, 12:33am UTC](https://forum.johnnydecimal.com/t/role-for-mocs-in-jd/1745/1 "2024-08-17T00:33:42Z")

</div>

On a long-term slog to get all my files into the JD system. I am starting to sense the need for another level of cross-referencing amongst IDs. For example (I am an academic), I might have students (each with their own ID in a category containing students) working on topic A and producing papers (in a category containing papers, each with its own ID) and being funded on sponsored research (in its own category). And perhaps along the way, I will teach a course with material on that topic. This, to me, calls for an MOC (map of content) linking all the relevant IDs (I am using Obsidian for my JD-dex). For the moment, I’ve started a MOC with major headings and links with JD ID 00.02 (reserving 00.01 for my area/category list).

I wonder if others see this approach as valuable - especially in a non-academic context.

---

<div class="post-metadata">

**Author:** ![fender](https://forum.johnnydecimal.com/letter_avatar_proxy/v4/letter/f/848f3c/32.png) [@fender](https://forum.johnnydecimal.com/u/fender)\
**Post date:** [August 17, 2024, 11:01am UTC](https://forum.johnnydecimal.com/t/role-for-mocs-in-jd/1745/2 "2024-08-17T11:01:53Z")

</div>

I use Logseq, and I’ve had the same thought.

Either to use

> #tags

or

```auto
Index entry Logseq
property:: property

```

to reveal connections to other IDs.

This is not relevant for ALL my index, but some parts.

Here’s an example of what it would look like - just to get a feel for it:

**Tags**  
 ![JD-tags-on-IDs](https://forum.johnnydecimal.com/uploads/default/original/1X/35bfea827049b74287d9a16859a239448451dc13.gif)

**Block-property**

Using **jdnote::** to add notes to certain ID’s - and then run a query to find all:

![JD-block-properties-to-IDs](https://forum.johnnydecimal.com/uploads/default/original/1X/b76eb643c3f51c75cd27dde5f66e48eb3cf01bd7.gif)

I’m leaning towards the last one, using the jdnote as block property. Feels cleaner.

---

<div class="post-metadata">

**Author:** ![PhillyChuck](https://forum.johnnydecimal.com/letter_avatar_proxy/v4/letter/p/f14d63/32.png) [@PhillyChuck](https://forum.johnnydecimal.com/u/PhillyChuck)\
**Post date:** [August 18, 2024, 12:38pm UTC](https://forum.johnnydecimal.com/t/role-for-mocs-in-jd/1745/3 "2024-08-18T12:38:30Z")

</div>

After playing around a bit more, I decided to take fuller advantage of the automation capabilities of Obsidian and wikilinks. So when I want to call out a particular topic, I embed the wikilink, e.g., [[SubjectA]] into my ID entry, then click on it and Obsidian will set up the page. And on that entry page for SubjectA, if I show backlinks, it will link to each of the entries using that (and of course also populate the graph view). I also moved the topical link pages to the top of my hierarchy using the folder \_CollectedLinks

So no need for manual MOCs!!!

---

<div class="post-metadata">

**Author:** ![brookscl](https://forum.johnnydecimal.com/user_avatar/forum.johnnydecimal.com/brookscl/32/918_2.png) [@brookscl](https://forum.johnnydecimal.com/u/brookscl)\
**Post date:** [August 23, 2024, 1:06pm UTC](https://forum.johnnydecimal.com/t/role-for-mocs-in-jd/1745/4 "2024-08-23T13:06:38Z")

</div>

I do a mix (in Obsidian) of both automated MOCs (really just a DataView summary of inbound links to an ID) and hand-crafted MOCs for IDs that will benefit from it. This is usually IDs that have a lot of notes associated with them, perhaps with some value in sub-organizing them. The MOCs live in the note corresponding to the ID itself.
