-
Notifications
You must be signed in to change notification settings - Fork 13
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
[BUG] - Example data not yet usable with the BODS visualiser #734
Comments
Thanks for raising this issue. We are just in the final stages of updating the BODS visualisation library to handle version 0.4 data. You can see the ongoing work over in https://github.com/openownership/visualisation-tool We've conducted two sprints of work in recent months and are just coming to the end of sprint 1. Here are the project boards for sprint 1 and sprint 2. I hope that we will be in a position to release an updated version of the visualisation library which will handle version 0.4 data by early December 2024. I'd love to know more about how you are using the visualisation library. If you go to https://www.openownership.org/en/about/team/stephen-abbott-pugh, you can find my email address and reach out. This would also allow me to immediately update you as soon as the latest changes are released. |
@oxyuranus-scutellatus We are also in the process of updating the BODS data review tool and will be releasing those changes very soon. Here is the project board for that work: https://github.com/orgs/openownership/projects/10 New releases for both https://github.com/openownership/cove-bods/ and https://github.com/openownership/lib-cove-bods to add new tests and handle BODS version 0.4 data will be published very soon, likely in early December 2024. |
@StephenAbbott Thanks for your fast reply. |
@oxyuranus-scutellatus I've just run https://github.com/openownership/data-standard/blob/0.4.0/examples/indirect-ownership.json through the internal demo version of BODS visualisation tool which is running the soon-to-be-released code and here is the resulting image: |
Summary of the bug or issue
Additional context and details
statementType is missing but required. Check that the field is included and correctly spelled.
The text was updated successfully, but these errors were encountered: