Blockchain Journal Data Fabric v.95 Migrated To CMS

Well before BCJ launched in January in order to bring you some of our first articles from the World Economic Forum in Davos (and even before Blockchain Journal had a name or a domain), we knew that it would need two major components to serve as the foundation for all of its content; a glossary and a data fabric that matched the inner workings and machinations of the blockchain industry. 

For example, public blockchains are not companies nor are they products that are offered by companies. This structure is relatively unorthodox compared to other tech sectors. As services go, they're like the internet. Once they're launched, nobody really owns them (after all, that's the entire point of decentralization). And the majority of the ones that matter are either permisionless or on their way to being permissionless which is exactly how the internet works. Little blockchain industry-specific details like that require careful consideration when one is building a data fabric that essentially documents the industry's structure, entities, and participants.  

Given the need for such a bespoke data fabric, we started to develop its schema back in early Fall 2022 and then began the data curation process. Among a great many other data, this involves making a record of all the different public distributed ledgers, the tokens that are supported by those ledgers, the inventors of those ledgers, the projects that run on those ledgers, and even the structures of the coalitions that service the primary interests of those ledgers. 

However, back in Fall 2022, we didn't even have a content management system to store the data we were already collecting. But knowing we had to get started on the curation process, we launched the data fabric and its schema as a separate system. Since then, we've been loading it with data and adjusting its schema based on how the data entry process was testing our initial industry structure assumptions. 

Today, as we prepare to launch our Enterprise Blockchain Adoption Tracker (which strategically requires the support of this fabric), we migrated the data fabric's structure and data--what we're calling version .95 of the fabric--from the separate system to our content management system and have started the process of marrying our existing content to that fabric. For example, where an existing BCJ article mentions Ethereum, we can now marry that article to our data fabric's record of the Ethereum public ledger. All of the posts in our upcoming Enterprise Blockchain Adoption Tracker are deeply tied to the data fabric given how those posts will make mention of projects, organizations, solutions, and people. Below is a partial screenshot of the data fabric's data-entry form that we'll be using to make a record of the many blockchain projects that we'll be tracking. 

Now that the data fabric has been migrated into our content management system and our research team has been trained on how to maintain it, the Enterprise Blockchain Adoption Tracker will come next (probably within the next week or two). However, one important thing to note is that it will probably be 6 to 12 months before any evidence of the data fabric's existence will start to make an appearance in BCJ's public facing interface.  

Once we solve for a few areas of friction in the data fabric management and we launch the adoption tracker, we'll declare the fabric and the site to been synchronized in a way that both have officially reached version 1.00.