-
Notifications
You must be signed in to change notification settings - Fork 54
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.
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
count outputs in scientific notation #616
Comments
@dpriskorn what's an example query creating this result? |
Example query please. This is another minor thing that will be fixed soon and should be added to #615 At the danger of repeating myself: Qlever currently does not fulfill SPARQL 1.1 in one hundred small respects. We are fully aware of this and it was a fully conscious decision to first work on the hard stuff (and get it to work and see whether it works at all). Once the hard stuff is done (SPARQL 1.1 Update and SERVICE is next), we will takes care of the hundred little details. But it would of course be great if you guys, or other competent people from the Wikidata community, would join https://github.com/ad-freiburg/qlever and help us fixing the hundred little details. The QLever code has a pretty high standard (in most parts) and is well organized and well tested and well documented. And we would of course help to find the right place and interface for adding stuff. And we do code reviews. I will also, in the coming weeks, write a document outlining the overall structure of QLever. So that newcomers to the project can quickly and easily find out which code is where and does what and how. |
See also #618 regarding documentation 😀 |
Example query https://qlever.cs.uni-freiburg.de/wikidata/dtZ84t |
Do you have a query that works? You posted a screenshot above, can you provide the query behind that screenshot? |
Here is the correct link https://qlever.cs.uni-freiburg.de/wikidata/ZrNcaM |
This has been fixed as a part of #648. The number is now formatted as an integer in the UI and in the exported downloads which is |
This is not expected or understood by non-technical users. Could we change it to output real full length numbers by default?
The text was updated successfully, but these errors were encountered: