This is not really an issue but a suggestion, just to reiterate what I said last evening at the end of the conf call. Please don't be shy about submitting problems that you discover/perceive with the BLR website or with Zenodeo. The more you discover errors, the better the app and the API become when those errors are fixed.
If you see a problem with the UI – the perhaps the font is garbled, or the UI text has a spelling mistake, or the formatting is not nice on your particular device (combination of device, OS and browser version) – or if there is a problem with UX – misleading terms, too many clicks required to do simple things, expecting something but getting something else – those are all problems likely with the website. Please report that as an issue on the BLR repo https://github.com/plazi/BLR-website/issues
If you see a problem with the results – you ask for something but get something else, performance is not good enough – that is a problem with Zenodeo. You can confirm that by using curl or even your browser to run the same query that the BLR website is running, but querying Zenodeo directly (you can find the query by looking at request that your browser is making using the Developer tools or menu in your browser). The query to Zenodeo will be something like as follows https://zenodeo.org/v2/<resource>?<query here> where resource will be either treatments or images. Please report that as an issue on the Zenodeo repo https://github.com/punkish/zenodeo/issues
One important note: Please restrict each issue to just one problem. In other words, make the issue as narrow as possible. Control the urge to add another problem to the same issue. Instead, open a new issue. And be as detailed as possible that will allow me (or @teodorgeorgiev) to reproduce the problem. In both cases, please tag the issue as a bug or a feature request or any other suitable tag.
In any case, don't worry about misreporting, or reporting something in the wrong forum. We can always move the issue to the right place. It is important that you report.
This is not really an issue but a suggestion, just to reiterate what I said last evening at the end of the conf call. Please don't be shy about submitting problems that you discover/perceive with the BLR website or with Zenodeo. The more you discover errors, the better the app and the API become when those errors are fixed.
If you see a problem with the UI – the perhaps the font is garbled, or the UI text has a spelling mistake, or the formatting is not nice on your particular device (combination of device, OS and browser version) – or if there is a problem with UX – misleading terms, too many clicks required to do simple things, expecting something but getting something else – those are all problems likely with the website. Please report that as an issue on the BLR repo https://github.com/plazi/BLR-website/issues
If you see a problem with the results – you ask for something but get something else, performance is not good enough – that is a problem with Zenodeo. You can confirm that by using
curlor even your browser to run the same query that the BLR website is running, but querying Zenodeo directly (you can find the query by looking at request that your browser is making using the Developer tools or menu in your browser). The query to Zenodeo will be something like as followshttps://zenodeo.org/v2/<resource>?<query here>whereresourcewill be either treatments or images. Please report that as an issue on the Zenodeo repo https://github.com/punkish/zenodeo/issuesOne important note: Please restrict each issue to just one problem. In other words, make the issue as narrow as possible. Control the urge to add another problem to the same issue. Instead, open a new issue. And be as detailed as possible that will allow me (or @teodorgeorgiev) to reproduce the problem. In both cases, please tag the issue as a bug or a feature request or any other suitable tag.
In any case, don't worry about misreporting, or reporting something in the wrong forum. We can always move the issue to the right place. It is important that you report.
Many thanks
@myrmoteras @mguidoti @millerjeremya @tcatapano @plazi/poa-office @teodorgeorgiev