Skip to content
This repository has been archived by the owner on Jan 4, 2022. It is now read-only.

Search functionality is not fully functional and is inconsistent between web app instances #428

Open
xhoenner opened this issue Aug 13, 2018 · 0 comments

Comments

@xhoenner
Copy link
Contributor

Steps to reproduce

Go to the production web app landing page - version 3.35.4
Search for A69-1602-26876.
In another tab, do the exact same thing except on the dev web app, same version used.

Try the same thing on both instances with A69-1602-24963.

Try the same thing on both instances with VR2W-120773

What happens

Despite the fact that this tag exists in both the production and dev databases (e.g. https://animaltracking.aodn.org.au/tag/show/134076088), there is an inconsistency in the results returned by the web apps.

The production web app returns that nothing matched this query, see screenshot below
screen shot 2018-08-13 at 1 41 19 pm

On the dev instance a result is returned, see screenshot below
screen shot 2018-08-13 at 1 44 52 pm

For A69-1602-24963, no search result is returned on both instances despite the fact that this tag exists in both databases.

For VR2W-120773, the number of results differ between the two web app instances

What should happen

  1. Results should be consistent between web app instances.
  2. When searching for a given tag that has been registered in the database, the web app should return the corresponding result
  3. When searching for a given receiver that has been registered in the database, the web app should return the same number of results for each instance
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant