fix #32: handle custom params in URLs

[bboyle]

• prevent UI router from controlling query string parameters
• manually set query string parameters in URL when searching
• regenerate mam.js

[scottssutton]

This seems to have fixed most of the issue. If I search for an item using this mam.js it remembers custom parameters I've set and if I do a subsequent search, it remembers the items I set in my previous search.

One issue that still appears to be happening is that I can't set a default parameter for a dropdown menu that isn't All. If an All option is available this will show up by default, no matter where in the list it is or whether another option containing selected="selected". If there is not an All option in the menu a blank item is shown by default, not the first item in the list or the option containing selected="selected"

For example, I want to have a Status dropdown menu with the options Current (default), Complete and Planning Study. I've used the code below. This shows the All option as the default (even though it's last in the list), and if I remove the All option, that menu item is blank.

<li class="widget-col-half-right">
                <label for="status">
                    <span class="label">Status</span>
                </label>
                <select ng-model="form.search.Stage" id="status">
                   <option value="Current" selected="selected">Current</option>
                   <option value="Complete">Complete</option>
                    <option value="Planning study">Planning study</option>
                    <option value="">All</option>

                </select>
            </li>

[bboyle]

Options:

• support ng-selected. Currently not working because I'm overriding the form state based on the URL parameters
• use ng-init to set the value (can be placed on the option or select tag, or anywhere)

ngSelect feels nicer for authors.