Skip to main content
3 of 7
Did more research on initial answer, details here

After a short exploratory meeting with Alation, was pointed towards Data Cookbook which looks promising (and apparently is used by many other universities). Will look into further and may update this answer.

http://www.datacookbook.com/videos-2/ (as a DE, I'd recommend watching the videos in order: 1, 2, 5, 4, 3)


Preamble:

Def vs Spec? From watching the videos, seem to refer to...

  • "Definition" = an individual data asset definition/entry (eg. a table or set of unstructured data)
  • "Specification" = A deliverables/report, includes description and what data system it is for/from (eg. is a basic report, PowerBI dashboard?). Can have multiple Definitions linked to them (eg. so users can see what data assets are used in this report).

This link kinda illustrates the differences / relations: https://youtu.be/5SQR0NmccMo

A good description of the general workflow that Data Cookbook aims to support: https://youtu.be/jA-z9r8RnzA

Users:

Analysts:

  • Works with requesting users on Specs (ie. reports)
  • Day-to-day, can log in a see new requests ("information requests") by end users
  • or work on Specs and Defs that they are working on
  • Request info from requesting end users
  • Approve Specs to publish to catalog (can include link to report if reporting system supports that (eg. a PowerBI link))

Data stewards:

  • Works with requesting users on Defs (ie. data asset entries)
  • Can be assigned to a subset of "functional areas"
  • Get updates when new data asset Definitions are added / updated in the catalog
  • Can review Defs, request input from creator/editor (eg. for clarification or reasoning) (who then gets alerted)
  • Send email link to data asset definition creation/changes proposal to relevant users to request additional comments on proposed creation/changes
  • Approve or reject changes to publish to catalog

End users:

  • Can log into a web UI
  • Search for data
  • Leave comments about a Def or Spec (for data stewards or analysts to be notified of)
  • Make ticket requests in general if can't find the data they need (for a data "librarian" to either direct them to or start process of new Def or Spec creation for that data)