Unexpected Behavior in Search by URN

[bencap]

Via the web based search interface we receive no hits for a search for urn:mavedb:00000053-a-1, but we do receive hits for a search for urn:mavedb:00000053. It seems like we should resolve searches for both queries.

[bencap]

I was unable to reproduce this issue, although two things did come up while I was investigating:

• Attempting to search via a URN in the UI currently redirects users to the MaveMD search page, see URNs are caught by HGVS RegEx in MaveMD Search Re-Route mavedb-ui#637
• Our current URN based search tests were insufficient for testing this case. They attempted to search via a non-existent urn property on the ScoreSetSearch object. These tests passed by coincidence-- when we added a single published score set and the search automatically searches for published score sets, we get results.

The changes on this branch will fix these tests, adding a second decoy score set and changing urn to text to match the correct search behavior.