We need to build a way to manage relationship / upload "dependency trees".
This would work in two ways:
1 - relationships TO a documentWe should surface all relationships TO a given document when you navigate to the document. For example, if you are viewing a media file, you should see all documents that relate to that given media document when you are viewing the media document itself in the admin UI. This will open up the possibility to, for example, prompt the user upon deletion of the document to say something like "You are about to delete this media document, but these X number of documents relate to the media document."
2 - Relationships ON a documentWe should also surface all relationships that a parent document has relations to. For example, if you are editing a post, and it has relationships to X number of media files, and X number of categories, tags, etc - - we should be able to view a list of all dependent relations easily. This will be helpful in cases where, say, you want to "bulk publish" changes to a parent post, but also want to bulk publish changes to all related documents at the same time.
Both of these new features in conjunction will allow us to build dynamic caching / purging down the line as well. For example, let's take an example REST response at /api/posts/:my-id?depth=2. If someone wanted to cache this URL, we would need to be able to purge this URL from cache not only when the post itself changes, but also when any of its relations up to 2 levels deep change.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4