Engineer's week 2025: Model Datasets within Collibra
During the spring Engineers week, we presented the work we recently did to incorporate Model Datasets within the existing Global Data Platform. We start by first explaining why we have Collibra, and then explain how Model Datasets fit into our Global Data Platform.
So, what exactly is Collibra?
Collibra is part of the Global Data Platform solution. We use Collibra to implement Data Governance policies as well as use it for its Data Catalog capabilities. Users can use Collibra to find and request access to data that is available within the Global Data Platform. Within team Atlas, we focus on implementing the business requirements related to Data Governance and the general Catalog experience, using the Collibra platform.

Engineer's week: a solution to our unique challenges
About once a week, I have to explain to someone, what we actually do with Collibra in Rabobank. Here is an example of how this conversation goes: “Hey, what do you do?” – Im a Collibra developer. “A developer?, what programing language do you use?” – A well, its complicated, we use a mixture of BPMN Workflows and Groovy scripts and we use Java Spring for integration….. “So you are a Java Developer?” -No… By this point, neither of us know what’s going on anymore, but, as soon as I get the opportunity to show someone what we actually do on a daily basis, it all makes sense to them. Within Rabobank, there are many teams doing similar highly technical, world leading, advance implementation of some unique technology, and the Engineers week is the perfect time for us to demonstrate these things.
Model Data Sets, what is this about?
During Q4 2024, Q1 2025, we were working on the catalog implementation for Model Data Sets. During our presentation we explained the different data sets we currently support within our platform, and where these new kinds of Datasets would come in. This comes with its own unique set of challenges. As you can see in the image, the big “work in progress” banner reminds us that we are in a ever evolving environment, but, as long as we are clear in our communication, we can make things work. As shown below, model data sets are “Restricted”, meaning, they are not meant to be consumed in the same way Raw and Defined datasets are. More about that later.

Implementing these new datasets within Collibra
For team Atlas, we were able to split this task up into two technical topics: Workflows and Java Integration. Workflows, or, better known as BPMN flows, is what we develop and deploy within Collibra. We had to do some work to modify our existing workflows to handle the new kinds of Datasets. For instance, you cannot use our Access Request workflow to Request Access to a restricted or Model dataset, but you should be able to Register a Model dataset. We also did a small demo explaining how the integration works, showing how a producer’s metadata message leads to the automatic update of a Model Dataset, making the data available immediately within the dataset.
Looking ahead
As an engineer, I’m very happy that we also get the chance to show all the great things we are working on. Its also great to see what other colleges are up to as well. We are working for a big organization, and events like these is where we get the opportunity to just connect and, even get some good feedback from some out of the box thinking viewers.
About the author
- Stephan BouwerDevOps Engineer
