Data Stewardship


In the past, developers of NoSQL systems had to use a variety of tools to manage enterprise metadata. There were often dozens of configuration files that each needed to be modified as new data elements were added to a system. Auditing all the rules for a given data element was time consuming and expensive. It does not have to be this way! What if we had graphical tools that allowed you to navigate directly to any given data element and see the properties directly in the model! This is the vision of EasyMetaHub's new framework of tools. Based on the advanced Google Polymer-3 web components, it puts all the tools right in the had of the data steward!

Here are the top 47 questions your staff needs to answer:

  1. What is the definition for this data element?
  2. Who approved this definition?
  3. When was the approval done?
  4. Is there a distinct URI associated with this data element?
  5. Is there a namespace for this data element?
  6. What is the ObjectClass name for this data element?
  7. Are there mappings of this data element to Open Linked Data sources? (DBPedia, Wikipedia etc.)
  8. Does this data element name conform to ISO/IEC 11179 guidelines?
  9. Is there a mapping of this data to the National Information Exchange Model (NIEM)
  10. Are there alternate labels used for this data element in different business units?
  11. What are the semantic concerns about this data element? Is the meaning clear?
  12. Has there been any history of putting different types of data within this data element?
  13. How long have we been using this data element?
  14. What are its valid values? (min, max, enumerations, etc.)
  15. What are the statistics of this data element?
  16. What is the character set used in this data element?
  17. Is this character set "distinctive" - that is do the distribution of characters or character order help identify this data type?
  18. If this is a date element, do we only store past dates?
  19. If this is a date, what is the range of dates in a chart?
  20. Is this data element used?
  21. If so, how many instances are there in your DEV, STAGE and PROD environments?
  22. Is there a range index for this data element?
  23. If it is a code, what is the distribution of the code values?
  24. How much does it cost to store this data element and all the indexes?
  25. What is the business justification for storing this data?
  26. Are there any security policies for this data element?
  27. Is this data element considered "Sensitive"?
  28. Is this a PHI data element as defined in HIPAA?
  29. Is this a PII data element?
  30. Who wrote those security policies?
  31. Are there redaction rules?
  32. Are there rules on who can search?
  33. Where did the data come from?
  34. What tables and columns in a source system store this data element?
  35. What are the source system formats?
  36. What versions of what programs were used to ingest and transform this data element?
  37. What are the valid formats of this data element?
  38. What are some sample parent elements that contain this data element?
  39. What are questions that people have about this data element?
  40. Who is the data steward for this data element?
  41. What documents store this data element?
  42. What retention rules are associated with these document?
  43. What source systems store this data element?
  44. What reports use this data element?
  45. How often do these reports run?
  46. How many resources do these report take (CPU time, memory)
  47. Do reports sort or order by this data element?

Let us help your organization answer these questions.