Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Search: Searching on a negative number returns a lot of false results. #819

Closed
kcondon opened this issue Aug 11, 2014 · 2 comments
Closed

Search: Searching on a negative number returns a lot of false results. #819

kcondon opened this issue Aug 11, 2014 · 2 comments
Labels
Feature: Search/Browse Help Wanted: Code Mentor: pdurbin Type: Bug a defect User Role: Guest Anyone using the system, even without an account

Comments

@kcondon
Copy link
Contributor

kcondon commented Aug 11, 2014

Tested on 8/11/2014

I entered -160 in Geographic Bounding Box for West Longitude and -65 in North Latitude and got 122 results, which I find very unlikely. also, the cards did not show matches, whereas when I searched on 143 for East Longitude, it returned the dataset I was looking for.
@kcondon kcondon added this to the Beta 4 - Dataverse 4.0 milestone Aug 11, 2014
@pdurbin
Copy link
Member

pdurbin commented Aug 14, 2014

As described at #444 (comment) as of 9b5c634 we have been using Solr's "text_en" field to improve English-language search.

In #370 I intend to get away from using "text_en" for everything. It should help resolve the bug reported here.

@pdurbin pdurbin modified the milestones: Beta 10 - Dataverse 4.0, In Review - Dataverse 4.0 Nov 4, 2014
@pdurbin pdurbin removed their assignment Jan 20, 2016
@scolapasta scolapasta removed this from the Not Assigned to a Release milestone Jan 28, 2016
@pdurbin pdurbin added the User Role: Guest Anyone using the system, even without an account label Jul 4, 2017
@mheppler mheppler mentioned this issue Feb 3, 2020
Closed
@mheppler
Copy link
Contributor

mheppler commented Feb 3, 2020

@kcondon and @pdurbin I am closing this issue, and consolidating it with other related issues in an old issue that I have retitled as Search: Accented characters, ampersands, negative numbers and other special characters #820.

If you have any further information about this bug or other "special character" related search issues, please add your comment there.

@mheppler mheppler closed this as completed Feb 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature: Search/Browse Help Wanted: Code Mentor: pdurbin Type: Bug a defect User Role: Guest Anyone using the system, even without an account
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@pdurbin @mheppler @scolapasta @kcondon @eaquigley