FLUID-1806: OSDPL: Pattern node tagging causes redundant search results and bad user experience.

Metadata

Source
FLUID-1806
Type
Bug
Priority
Critical
Status
Closed
Resolution
Fixed
Assignee
Jonathan Hung
Reporter
Jonathan Hung
Created
2008-11-13T19:43:21.000-0500
Updated
2013-04-11T17:45:51.371-0400
Versions
  1. 0.6beta1
Fixed Versions
N/A
Component
  1. OSDPL

Description

Some nodes, notably older patterns, have a hierarchical tag / categorization. Because of this, doing searches will create redundant results because a single pattern belongs to multiple tags.

To fix:
1. Remove all existing tags for each node.
2. For each node, determine which category term it belongs to best, and ensure it only has 1 category.
3. Test results of step #2.
4. Re-input some tags, and re-test results.
5. If all goes according to plan, everything should look good. Continue to re-input tags.

Comments

  • Jonathan Hung commented 2008-11-13T19:43:31.000-0500

    Iteration22

  • Jonathan Hung commented 2008-11-13T22:35:20.000-0500

    The above "fix" didn't really fix it. The underlying problem was that there are two taxonomies (Category, and Tags) used to describe a pattern. Our View was searching across these taxonomies and finding the same pattern under different tags and categories. Thus multiples were being output in a View because it wasn't smart enough to understand it already found the same item.

    To fix this, I added another condition to the View filter: exclude any pattern that was in the Tags taxonomy. This Views was successful in searching only in the Category taxonomy, and thus only returning a single instance of the pattern.