Problems with the search and special characters like ‘#’

[jcreel]

The URL encoding is likely breaking the search.
When searching for something that has the pound symbol ‘#’, the URL being rendered in the browsers URL bar does not work. If this URL gets copied or the page gets reloaded, a 400 error is presented. Removing the “%23” (the encoded variation of the pound symbol ‘#’) from the ‘value’ field in the URL results in a working page.

Everything search seems fine. But searching for Title like so provides no result (the example here uses parentheses):
https://library.tamu.edu/discovery/discovery-context/time-of-resolve?field=title&value=Map%20Showing%20Proposed%20Roads%20Between%20New%20Road%20(Rear)%20of%20Administration%20Building%20(New)%20and%20Highway%206&direction=ASC&sort=title

Ideally, this should be handled at the Solr core, but we need to ensure that SAGE is not mangling the URL somewhere in the pipeline.

[kaladay]

Created the following issues due to investigation.

• Angularjs $location.search is not safe to use when passing '#'. #502
• The ID for fields, such as facets and more button, need to be sanitized. #497
• Creating a new Metadata, updating an existing Reader changing that field, then updating another Reader still shows value from other Reader. #501
• Null Pointer Exception in empty Discovery View when doing wildcard search. #500

The first two are more ore less directly related.
The second two are other issues that popped up in the process.