Model: MethodVariation

Implements method variations by mapping design methods to other design methods that are considered its variations.

Fields

• parent_id (foreign key DesignMethod model) : the main design method that the variations are derived from
• variant_id (foreign key DesignMethod model): the variant design method

did I have someone do this? I don't remember

Can you also be sure to edit the case study titles to be concise and informative.
e.g. Rheumatoid Arthritis Speakers Bureau Program—Envisioning Advanced Concepts --> Rheumatoid Arthritis Speakers Bureau Program
e.g. A Behind-the-Scenes Look at Developing iWitness --> iWitness - Managing Social Media Data

i think there's a devise config for this

Now that you pointed it out (the title issue with "UI" being "Ui", it is really bothering me, hahaha). Can you move this into a higher priority issue. Also, can you style the card text to be slight smaller.

http://help.papertrailapp.com/discussions/problems/1772-cant-filter-out-logs-with-advanced-regular-expression-negative-lookahead-assertion-and-more.html

From Jenn:
Something that came up was that the second-tier terms in the left sidebar were confusing. I got them from the current website, but are these the tags that are attached to methods in the database right now? Is there a way to rename them, or do you feel we should exclude them?

There seems to be a duplicate category. No methods are assigned to the first one...

Is the following output format fine for the helpers that will format the design method search results and build the filter hierarchy? @cearto @szhu

// example search result item
{ "id": 1,
  "name": "Example Design Method",
  ...
  "categories": [1, 2],
  "characteristic_groups": [1, 5, 10, 15],
  "characteristics": [4, 12, 24, 27, 50],
}

// example filter hierarchy
[
  { "id": 1,
    "name": "Build",
    "characteristic_groups": [
      { "id": 1,
        "name": "Fidelity",
        "characteristics": [
          { "id": 1,
            "name": "Low"
          },
          ...
        ]
      },
      ...
    ]
  },
  ...
]

change seeds so they're separated by purpose and data size instead of models and pick a sensible default seed for seeds.rb

Can someone look into this? It's a JS error that shows up on the homepage.

Mixed Content: The page at 'https://thedesignexchange.herokuapp.com/' was loaded over HTTPS, but requested an insecure stylesheet 'http://fonts.googleapis.com/css?family=Arvo:700'. This request has been blocked; the content must be served over HTTPS.

Point it to something.

For facet/filtered sidebar search. Need to have counts for each levels of the hierarchy.

Example:
query = "goats"

Ideation (15)
* Product Development (5)
* Purple (10)

So after finishing restoring the most of the backup database, I started working on restoring the tagging information for design methods used in case studies. However, due to some inconsistencies in the data format and weird missing data, I realized it would take me a lot longer to do this than the people that are actually working on the tagging. So I created the following table for all the tags that were in the backup database, so @cearto can have someone just refer to this table and do the tags again on the live app.

incorrect url on app/assets/javascripts/application.js

Building and Prototyping is in the db twice.

Should we move recsys onto a separate repo and have a separate api? Or for now leave it in the de portal repo?

769e5c0

Quick fix: Limit to at most two tags.
More permanent fix: Limit to x number of characters.

clean up the functionality

@nguyensomniac, @ikenohate09 - thanks for setting up the API. Started testing, and am encountering some problems. Wanted to clarify the appropriate call urls, to narrow down problem location. Are these valid calls?

https://thedesignexchange.herokuapp.com/api/case_studies
https://thedesignexchange.herokuapp.com/api/design_methods
https://thedesignexchange.herokuapp.com/api/method_case_studies

I'm getting a 404 response (on the first, haven't tested the others).

Maybe I'm jumping the gun, given the parenthetical not on the wiki - are these live?

should there be?

Try going to any /users/:id/edit URL.

This is because we don't have a before_action filter for checking for the correct user in the edit action.

1. Back up production data, write script to seed it into fresh databases
2. Check for and remove unnecessary models and fields
3. Update create migrations to get rid of all modify migrations

currently is on /design_methods/search/:q, should not have the design_method

make sure they're actually working

I messed up the commit order for my latest changes so I ended up bundling all of the changes into one commit instead of separating them and adding informative commit notes.

Basically, I removed all of the extra migrations that were modifying case studies and just updated the original migration with the correct field names and data types.

@cearto can you just comment and acknowledge that you read this and saw the changes so that you won't be wondering what happened to all the migration stuff that you guys did during your refactoring?

1-2-3-4-5 Pages on the bottom of case studies

Give @roxannemoslehi all the tags she has made.

not sure why it's no longer using sunspot

@cearto - I see that it's being used in some of the controllers, but the gem is not explicitly included in the Gemfile. Do you know where it's coming from?

• Quick fix: Small legend at the foot of the page
• Permanent fix: editor

Design methods load fine, though.

I'm running the latest version, 8739935.

Go through existing routes and remove unnecessary ones, reroute URLs that don't make sense, and deal with orphaned URLs that don't have a controller action.

A list of UI todos in order of importance

• Reintegrate image thumbnails into cards (dm & cs) [fixed by #53]
• Cut off gs and ys. [#31]
• Tag overflow [#31]
• Add permission restrictions to content creation pages
• Profile page dynamic layout is wrong. Fix mobile and desktop settings i.e. col-*-4 --> col-xs-4
• Add hoverIntent to card hoverEvent.