Open Ownership is launching a new software tool for visualising beneficial ownership (BO) data. Beneficial ownership data is at its most useful when it can be understood by the widest possible group of people. Visualisations of corporate structures are intuitive and easily understood, allowing more people to use beneficial ownership data. It is open-source and available for anyone to use in their own projects. A hosted version is also available, so that it can be used straight away without any coding. Users will need to bring some valid Beneficial Ownership Data Standard (BODS) data, but Open Ownership has done the hard work of turning the basic rules from the Beneficial Ownership Visualisation System (BOVS) into code so that users can generate visualisations of any networks they have.
Open Ownership has had a network visualisation feature in the register for a while now, so we know how useful it is for users to be able to see their data in graphical form. We have had great feedback on this feature and many implementers have told us they would like to offer something similar to their users. Because our existing visualisation is tricky to untangle from the register, we built this new tool which we hope will be easier to integrate.
There are lots of great options for data visualisation out there, but we see a niche in allowing BO registers and other data publishers to quickly give users a visualisation of their data. It runs completely in the browser, so should be simple to integrate into any existing web-based tools. The tool works with BODS data and we hope it will also encourage publishers to adopt the format.
As well as being useful to visualise data when publishing, it is also helpful for users to visualise data whilst they are working with it. In conjunction with our data review tool, this new visualisation tool is part of a suite of tools that can help implementers understand BO data better.
npm install @openownership/bods-dagre
The version of the tool launched today is basic and very much an alpha version. We are working with several implementers who would like to use it whilst they work towards publishing BODS data, or integrate it into their own registers. We will use these experiences to develop the features further and find the inevitable bugs. You can keep track via our issue tracker and we will also announce when we think we have something that is noteworthy to share. Our tech team would love your feedback on whether you think this is useful or not, and what changes you would like to see.