-
Notifications
You must be signed in to change notification settings - Fork 2
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
Network creation query without CPVs results in a network without edges and nodes #517
Comments
Hey @nightsh! Thanks for pointing out. This is not a bug in Elvis actually. The original data just happens to lack the name of the bidders sometimes. It's one of those cases where it would really help to see the network query 😄Then it would become pretty clear that it has anything to do with the CPVs at all. This is how the network query looks in the db. It's perfectly fine but you're getting those nameless bidders because you chose Greece. @zufanka We actually talked about this in #428. The idea was to show the nameless bidders/buyers as grey nodes. I see that the issue was closed a few days ago. Does that mean we're dropping that idea? |
That issue was about them not appearing at all. The issue was closed because they now do appear as a node with no name. |
How do they appear though? |
I don't understand how we decided to display the tenders who are missing the bidders |
I am confused: #428 was about "bidders missing a name", not tenders that are missing bidders? |
@zufanka This are the same thing in the data: a tender record with an empty cell in the bidder name. Of course there must've been a bidder if the tender was awarded but we don't know it. I suggest we close this issue in favour of #524 |
@georgiana-b I think this something else. If you create a network but select no CPV codes at all, it does not select all CPV codes, instead it selects nothing at all. See https://defense.tenders.exposed/network/d0649fbb-f298-4d26-83ac-5abc592a6978/ for example |
Example network: https://defense.tenders.exposed/network/395ec875-ec97-41f3-afe2-083d5dccb1c9
Steps to reproduce:
The text was updated successfully, but these errors were encountered: