Hi all,
Looking for solutions for handling “null specification” at the data element level in Aristotle.
For QA purposes, it would ideally be an attribute that is filterable or searchable within the metadata in Aristotle, with drop-down options such as “Null allowed” and “Null not allowed.”
I’d love to hear the community’s feedback on this use case and any insights on how feasible it would be to bring this into the current view of data element–level handling.
Interesting - This is something I had flagged (internally) when developing a Data Set Specification, but hadn’t considered implementing something like this for Data Elements.
If it’s about NULL values (& whether or not they are valid/permissible) it could be incorporated into Value Domains, possibly through Conceptual Domains?
IF this was a suitable approach, then you could possibly create 2 separate conceptual domains (1 for allowed, another for not allowed) & the related content could show which data elements have each implemented.
Using conceptual domains was our first idea too @A_Gore! Couldn’t have made a better suggestion myself.
Great question @AnjuAjith — hopefully @A_Gore’s idea above does the trick for you?
