#77 - Content relationships (e.g. related content)
-
By Chris Graham
- Added
- 2 views
| Identifier | #77 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | Content relationships (e.g. related content) |
| Status | Open |
| Tags |
Has Patch (custom) Risk: Database change (custom) Roadmap: Sponsorship (custom) Type: Cross-cutting feature (custom) Type: Tagging (custom) |
| Handling member | Deleted |
| Addon | core |
| Description | Extend meta keywords to cover more tagging scenarios.
Create a privilege to allow members to add to the tags for some content. Send out staff notifications when this happens so that it can be monitored. Add 3 new blocks, all of which are intended to by integrated into our default templates, but can also be called up independently anywhere on the site: 1) main_content_tags. Takes a list of tags as a parameter, a list of content types, and an optional content ID. Shows all the tags, and these link through to the search module which then performs a keyword search. If a content ID was passed, and the member has tagging privilege, a UI to add tag(s) is provided. 2) main_related_content. Takes a list of tags as a parameter, and a list of content types. This shows boxes of other content that shares tags and matches the content type(s). The user has the choice to order either by how many tags are shared or by rating or by add date. It works with pagination. 3) main_more_by_submitter. Takes a member ID, and a list of content types. The user has the choice to order by either rating or by add date. For future we need to add keyword support for: - Forum posts (and therefore forum topics, as first post in topic essentially represents the topic) - IOTDs - Polls (these don't currently support keywords) |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
First, I identified some problems (and solutions) with just naively using keywords (tags)...
Problem: Hard to consistently use the right keywords.
Solution Allow auto-complete when typing keywords.
Problem: Hard to see what a particular keyword is shared with, when adding that keyword
Solution: Include an overlay to show everything current with that tag, and also provide a link to do that search
Problem: Don't want automatic association with minor keywords that are very common on one particular website.
Solution: Checkbox to define whether a particular keyword is used for related-content
Problem: Don't want association with old content with precedence over new content, just because it matches a keyword.
Solution: Bias towards newest content, with a limit on how many related content items to show.
Problem: Don't want stuff from completely different categories coming through just because it matches a keyword (categories may hold very different content).
Solution: Scope related content to particular groups of categories (i.e. particular news categories and forums)
Problem: Inputting keywords is tedious and feels like a step into the dark.
Solution: Auto-generate keywords before the article is even submitted (currently it happens after submitting). Have a link to click to show recent keywords, popular keywords, etc, so there's something to easily reference against.
This would all have been a lot of work, and led to a system that may be more complex than its worth. Defining relationships manually may be better, which is what I did.
I've attached a patch to this issue that achieves that. It was written for ocPortal v9. The module overrides in there are just to get the relationship field into the UI, as well as saving functionality for that.
This has fewer content types, but also Comcode pages which the previous didn't.
I left out any changes to the CMS modules as they are similar.
There are also some relevant tweaks in here.
Not very helpful for me to be posting multiple patches that aren't really useful to anybody, but they can both be reviewed in the future when we try and add something proper to Composr.