Related content a.k.a - relationship between content

Would be great to have this available where we can search and link to related content from the Edit form.

Say I create a post about a gadget, I can link to other gadgets similar to it. Or Groups that are related.

Hashtags, categories won't solve this. Because when you read the post after a few months, the label will be populated with more gadgets that might be only vaguely related to the item.

  • Up vote
    1
    Down vote
  • View
    687
  • More
Replies (4)

    • This is common feature, however in most cases it's only for relationship within single module. Say, discussion related to this discussion, or task related to another task. Is this how you see it too?

      • H

        The closest I can see is for Users - there is friend relation... And it is bi-directional... But for other modules I don't see this bidirectional relationship possible..

        Say from a post, if I add link to a Video (by video module)... Now from the Video there is no way to list all the posts that have a link to it.. Different posts by different users could have link to that video.

        But if you look at wikipedia files page ( I can't post links .. so add https before this commons.wikimedia.org/wiki/File:KinderdijkWindmills.jpg#globalusage )

        Another example would be openculturas.org feature list.

        This "Relationship" field will make UNA very powerfull since there will be no limit on what can be achieved on a website. So users can continue discussing a video in their own timeline (not just as comments under the video), and we can find out the most popular /discussed video.

        Add a macro something like this -

        # Example macro  get_related ..  wishlist 

# List all items that are related to this post.. 
~bx_posts:get_incoming_relation[ ]~

# For posts - get related but filter for  "Photos"  by author 10.
~bx_posts:get_incoming_relation[{"params":{"author":"10", "type":"bx_photos" }}]~

# For groups - Get related  Groups.. 
~bx_groups:get_incoming_relation[{"filter":"type", "params":{"type":"bx_groups"}}]~

        Currently I am working aroud this by adding it manually in the post.. But its getting difficult to maintain consistency..

        • Ok. What you are asking is great. Not as trivial or simple as an extra field, but indeed a much needed and powerful improvement, which would make UNA much more capable as a framework. We already have the underlying logic to enable relationships, however more work is required to provide UI for customising them and support across core apps to adopt them.

          The ticket will be for UNA 15. I'll follow up once it's created.

          • H

            Along with this, can you also consider making smaller re-usable, stand alone modules.. (micro modules or features or package or whatever we want to name it).

            For example - The category could be a stand alone module by itself. This has the main benefits

            1. Multiple categories for a content : I can create a category called CATEGORY1 consisting of (News, Analysis, ...) and aother CATEGORY2 comprising of (Arts, Technology, Environment ... ).. Now in the posts form I can have two different "relationship" fields pointing to the categories. One field linking to CATEGORY1 and another field to CATEGORY2. So one post can be a "News" related to "Environment". another could be "Analysis" related to "Environment".
            2. Re-use Categories across different modules : Currently the categories under Posts are different from categories under other modules. So I can't list all the "Environment" related content since Videos and Posts have different "Environment".

            You can continue to package "posts" as it is done currently (with the sensible defaults having one Category field). But advanced users will have more power.

            (There is a thread related to taxonomy here - https://unacms.com/d/building-a-dedicated-taxonomy-module-for-una, but I added more details here thinking the relationship could be re-used.

            Also labels cannot be an alternative. It could be a short term workaround though. Categories are for Site admins / operator to structure the site. Labels are for users to dynamically organize content.

            Login or Join to comment.