# Links between documents?

**URL:** <https://discourse.devontechnologies.com/t/links-between-documents/45949>\
**Category:** Scenarios\
**Created:** [March 26, 2019, 9:19pm UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949 "2019-03-26T21:19:54Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![midas](https://discourse.devontechnologies.com/letter_avatar_proxy/v4/letter/m/e9c0ed/32.png) [@midas](https://discourse.devontechnologies.com/u/midas)\
**Post date:** [March 26, 2019, 9:19pm UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/1 "2019-03-26T21:19:54Z")

</div>

I’ve been wondering how to link one document (A) to another document (B).

Of course, I could put the UID (x-devonthink-item://) of A somewhere in B. But, this means that I’d have to edit B itself, inserting an unseemly URL.

It would be more desirable to put the UID of A into some meta-field of document B. Furthermore, it would be helpful to not limit how many links can point out of a document. That is, be able to generate multiple links from document A to documents B, C, D, etc.

In this way, I could build relationships between documents, even if they’re stored in different places.

Is this possible, and if not, is this a request that fits into the philosophy and scope of what devonthink is aiming for?

---

<div class="post-metadata">

**Author:** ![BLUEFROG](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/bluefrog/32/135_2.png) [@BLUEFROG](https://discourse.devontechnologies.com/u/BLUEFROG)\
**Post date:** [March 26, 2019, 9:53pm UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/2 "2019-03-26T21:53:24Z")

</div>

> [@midas](#):
>
> to another document (B).

There is no _document_ in DEVONthink. There are several. You should be more specific as the ideas, problems, and suggestions may easily be relative to a particular format.

---

<div class="post-metadata">

**Author:** ![midas](https://discourse.devontechnologies.com/letter_avatar_proxy/v4/letter/m/e9c0ed/32.png) [@midas](https://discourse.devontechnologies.com/u/midas)\
**Post date:** [March 26, 2019, 10:56pm UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/3 "2019-03-26T22:56:12Z")

</div>

Actually, my point is to seek a solution that is agnostic to format of the file/document.

Suppose, for example, that the document (A) is a PDF file. I’d like to have a link from A to other documents (B, C, etc) without actually inserting the link inside A. That is, I don’t want to modify A itself.

---

<div class="post-metadata">

**Author:** ![StephenL](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/stephenl/32/8402_2.png) [@StephenL](https://discourse.devontechnologies.com/u/StephenL)\
**Post date:** [March 27, 2019, 12:42am UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/4 "2019-03-27T00:42:14Z")

</div>

You can put a link in the “document’s” url. This is what it looks like on The iPhone. I don’t know what you could do if you need multiple links. Annotations works like that.

 ![image](https://devontech-discourse.s3.dualstack.us-east-1.amazonaws.com/uploads/original/2X/9/9c46c45032e0fa5854faa0f8d94a9dbe2f174bac.jpeg)

---

<div class="post-metadata">

**Author:** ![midas](https://discourse.devontechnologies.com/letter_avatar_proxy/v4/letter/m/e9c0ed/32.png) [@midas](https://discourse.devontechnologies.com/u/midas)\
**Post date:** [March 27, 2019, 10:44am UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/5 "2019-03-27T10:44:24Z")

</div>

Thanks, @StephenL. I was aware of the URL field, but the limitation is that there is only one field for storing a link.

As your example shows, this field tends to be a useful place to keep a connection to the original source.

However, what to do if I now want to link this document (suppose it’s a Web Archive, or a pdf generated from a web site) to a couple other related documents (oh, say a spreadsheet, a RTF with some notes I’ve written, and a mindmap file)? This problem comes up as I try to draw links and relationships between documents.

Devonthink seems to be a great platform to accomplish this, but a quota of one outgoing link per document is constraining. I understand a million links could be embedded into documents, but that changes the document itself — not desirable, and in some cases, like a read-only file, not doable.

Extending the topic, suppose we had the ability to put in multiple links as metadata associate with a document. What then? How would one traverse and explore these links?

There is presently a link button that, when clicked on, takes you to the single url link associated with the document. But, in this hypothetical version of DevonThink, if you control-click on that icon a menu would pop-up next to the pointer giving you a list of target documents. As you hover over each choice, a small preview icon would show up next to the menu item. Select one, and you jump to it. Hit command-[and you go back. Command-] go forward.

We can get even more powerful. The drop-down menu shows target links, a divider, and then source links (things that point to this document).

All this would be really amazing. One could build an amazing wiki of documents with this capability.

---

<div class="post-metadata">

**Author:** ![ryanjamurphy](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/ryanjamurphy/32/5890_2.png) [@ryanjamurphy](https://discourse.devontechnologies.com/u/ryanjamurphy)\
**Post date:** [March 27, 2019, 11:46am UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/6 "2019-03-27T11:46:49Z")

</div>

I’m not sure what the affordances of this arbitrary metadata link approach is over, say, providing a table of contents file in the directory of your curiousity and replicating that ToC anywhere else that’s relevant.

Such a ToC might be more powerful than what you’re suggesting because you can add “metadata” to it and arbitrarily restructure its contents.

---

<div class="post-metadata">

**Author:** ![Silverstone](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/silverstone/32/34093_2.png) [@Silverstone](https://discourse.devontechnologies.com/u/Silverstone)\
**Post date:** [March 27, 2019, 12:29pm UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/7 "2019-03-27T12:29:14Z")

</div>

I think you just have to adopt the right use of groups and replicants. Simply group the Items you think connected. If you need some of these items in other groups - replicate them. To make it even easier, make groups as tags and just tag what you need. As simple as that. This is a really powerful feature of DTPO, underused by many, who are trying to establish a many-to-many connections in this or that way.  
Everything you need is already here, just use it.

---

<div class="post-metadata">

**Author:** ![BLUEFROG](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/bluefrog/32/135_2.png) [@BLUEFROG](https://discourse.devontechnologies.com/u/BLUEFROG)\
**Post date:** [March 27, 2019, 1:48pm UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/8 "2019-03-27T13:48:24Z")

</div>

I’m confused.  
In editable formats, like PDF or webarchive, you already can select text and **right-click** to **Add Link** or **Link To** other items in your databases. This creates active hyperlinks from the selected text.

---

<div class="post-metadata">

**Author:** ![shmavon](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/shmavon/32/17857_2.png) [@shmavon](https://discourse.devontechnologies.com/u/shmavon)\
**Post date:** [December 11, 2020, 9:15am UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/9 "2020-12-11T09:15:26Z")

</div>

I would like to continue this topic as I am facing the same scenario @midas had.

I am looking for a way to link documents/files within my DEVONThink database so that I can build associative relations between them.

The closest implementation of this idea is in Jira, where you can link issues between each other with links (and can also specify type of link, such as “related to”, “is clone of”, “is duplicate of” etc.).

This is extremely helpful for organizing content in non-linear manner.

---

<div class="post-metadata">

**Author:** ![BLUEFROG](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/bluefrog/32/135_2.png) [@BLUEFROG](https://discourse.devontechnologies.com/u/BLUEFROG)\
**Post date:** [December 11, 2020, 1:54pm UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/10 "2020-12-11T13:54:40Z")

</div>

Welcome @shmavon

Please check out the **Help \> Documentation \> Documents \> Document Linking** for information on ways documents can be linked.

---

<div class="post-metadata">

**Author:** ![shmavon](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/shmavon/32/17857_2.png) [@shmavon](https://discourse.devontechnologies.com/u/shmavon)\
**Post date:** [December 11, 2020, 8:56pm UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/11 "2020-12-11T20:56:36Z")

</div>

Hi @BLUEFROG

Thanks, I guess you mean “Document Linking” section on page 33 of DEVONThink Handbook (there is no “Documentation” in Help menu of my version of the software).

I saw it before, but it doesn’t explain how I can link 2 image files together as related.

I would really appreciate if you could advice on how to achieve this with current functionality.

---

<div class="post-metadata">

**Author:** ![BLUEFROG](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/bluefrog/32/135_2.png) [@BLUEFROG](https://discourse.devontechnologies.com/u/BLUEFROG)\
**Post date:** [December 11, 2020, 9:11pm UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/12 "2020-12-11T21:11:47Z")

</div>

**Help menu \> DEVONthink 3 Help \> Documentation…**.

Document linking is meant for text-based documents. You could use tags on the images and filter based on tags to see ones with the same assigned tags.

---

<div class="post-metadata">

**Author:** ![shmavon](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/shmavon/32/17857_2.png) [@shmavon](https://discourse.devontechnologies.com/u/shmavon)\
**Post date:** [December 12, 2020, 8:47am UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/13 "2020-12-12T08:47:33Z")

</div>

Thanks @BLUEFROG

It would be great to log it as a feature request in case more people will be looking for such functionality. Should I open a ticket for that in Helpdesk?

---

<div class="post-metadata">

**Author:** ![BLUEFROG](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/bluefrog/32/135_2.png) [@BLUEFROG](https://discourse.devontechnologies.com/u/BLUEFROG)\
**Post date:** [December 12, 2020, 12:51pm UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/14 "2020-12-12T12:51:25Z")

</div>

No. The request has been noted here. Thanks.

---

<div class="post-metadata">

**Author:** ![Stiivi](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/stiivi/32/17044_2.png) [@Stiivi](https://discourse.devontechnologies.com/u/Stiivi)\
**Post date:** [December 18, 2020, 5:47am UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/15 "2020-12-18T05:47:56Z")

</div>

Just to add a use-case that I run into that would benefit from having links in between files: extract of reading/research notes and quotes.

1. Have a document/PDF as a source for reading/research
2. Read the document, highlight and mark notes in the document.
3. Create a text (markdown/rich) document with all the notes extracted
4. Add additional information/custom notes into the text document
5. Create a bi-directional link in between the newly created text document and the original PDF

There might be multiple extracts from the same PDF book/paper: either by topic, project or other relevant grouping.

This would allow one to easily navigate from extract/quote document to it’s source and vice-versa.

Another use case:

- (Rich) text document linked to a Keynote presentation(s) – talks given from that written work
- any manual or automated derivative work linked together that might end-up in a different context as the original document

It can be also thought as an information provenance linking – “where this comes from? Where this went into?”

Useful for content creators to track “source of truth”.

---

<div class="post-metadata">

**Author:** ![cgrunenberg](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/cgrunenberg/32/7172_2.png) [@cgrunenberg](https://discourse.devontechnologies.com/u/cgrunenberg)\
**Post date:** [December 18, 2020, 8:32am UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/16 "2020-12-18T08:32:13Z")

</div>

> [@Stiivi](#):
>
> Create a text (markdown/rich) document with all the notes extracted

That’s what Tools \> Summarize Highlights does and…

> [@](#):
>
> Create a bi-directional link in between the newly created text document and the original PDF

…the documents will be actually linked (the new one linking to the source, the source showing back links in the Document \> Links inspector)

---

<div class="post-metadata">

**Author:** ![shmavon](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/shmavon/32/17857_2.png) [@shmavon](https://discourse.devontechnologies.com/u/shmavon)\
**Post date:** [December 22, 2020, 11:57pm UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/17 "2020-12-22T23:57:41Z")

</div>

Just to add on the examples of such functionality - Zotero’s way of linking documents could be used as an inspiration for MVP.

![](https://devontech-discourse.s3.dualstack.us-east-1.amazonaws.com/uploads/original/3X/8/c/8ca1fa45fb613bb5da113d66fffa5048c69e2d9e.png)

---

<div class="post-metadata">

**Author:** ![BLUEFROG](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/bluefrog/32/135_2.png) [@BLUEFROG](https://discourse.devontechnologies.com/u/BLUEFROG)\
**Post date:** [December 23, 2020, 12:26am UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/18 "2020-12-23T00:26:30Z")

</div>

What is _MVP_ ?

---

<div class="post-metadata">

**Author:** ![pete31](https://discourse.devontechnologies.com/letter_avatar_proxy/v4/letter/p/d26b3c/32.png) [@pete31](https://discourse.devontechnologies.com/u/pete31)\
**Post date:** [December 23, 2020, 1:34am UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/19 "2020-12-23T01:34:19Z")

</div>

> [@BLUEFROG](#):
>
> What is MVP ?

I’m shocked! You don’t know MVP? Seems it’s this …

> **[Minimum viable product](https://en.wikipedia.org/wiki/Minimum_viable_product)**
>
> A minimum viable product (MVP) is a version of a product with just enough features to be usable by early customers who can then provide feedback for future product development.
> A focus on releasing an MVP means that developers potentially avoid lengthy and (possibly) unnecessary work. Instead, they iterate on working versions and respond to feedback, challenging and validating assumptions about a product's requirements. The term was coined and defined in 2001 by Frank Robinson and then populariz...

---

<div class="post-metadata">

**Author:** ![BLUEFROG](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/bluefrog/32/135_2.png) [@BLUEFROG](https://discourse.devontechnologies.com/u/BLUEFROG)\
**Post date:** [December 23, 2020, 1:38am UTC](https://discourse.devontechnologies.com/t/links-between-documents/45949/20 "2020-12-23T01:38:03Z")

</div>

If that’s the case, we’re many years past MVP 🙂

[Next page](https://discourse.devontechnologies.com/t/links-between-documents/45949.md?page=2)