[ICAT] run range issues

[Jay Rainey]

If you only fill in one side of the run-range an error is thrown: bad lexical cast: source type value could not be interpreted as target. Moreover, the size of the run range is 5-5 (e.g. 00000-00000), which is too small.

The following needs fixed:

1. No error if user inputs only one side (assume from start (000000) to INPUT, or INPUT to end (perhaps +10k?)
2. Remove limit on run-range size.

[Jay Rainey]

I have fixed this ticket, and you can find the changes ​here and the branch on github ​here.

To test

1. Open Mantid and log into the catalog with your federal ID.
2. Attempt to perform different searches using run-ranges. For example:

     62862 - 
     62862 - 62962
           - 62962
   

3. Ensure this returns the correct results (You can enable debug in the console log to view the query being performed).

[Martyn Gigg]

The functionality now works as described but the run range box is a little clunky and hard to use. I think we need to simplify it so that users can enter their text and we then parse what is there to decide whether it is a range, accepting either : or - as a separators.

If there is no separator then simply put the same number as start/end.

[Jay Rainey]

Improved run-range parse logic. Refs #8317.

• Added tooltip and removed input mask from run-range field.

Changeset: d9b068ca40abfaee396ec2f1d169504d8b2b7772

[Jay Rainey]

Added validator to run-range. Refs #8317.

• This allows only numbers and one hyphen or colon.

Changeset: d42538cb2ffa4767a4d66e58c48f9b90a2a520d2

[Jay Rainey]

To verify follow description in comment:1, and ensure the text-box has been made more user-friendly as suggested by Martyn in comment:3.

[Stuart Campbell]

This ticket has been transferred to github issue ​9162