<h1 id="so-you-want-git-for-data">so You Want Git for Data<a aria-hidden="true" class="anchor-heading icon-link" href="#so-you-want-git-for-data"></a></h1>
<ul>
<li><a href="/wiki/notes/BzaAaifsfEv5mTiEOFBPA">hasURL</a> <a href="https://www.dolthub.com/blog/2020-03-06-so-you-want-git-for-data/">https://www.dolthub.com/blog/2020-03-06-so-you-want-git-for-data/</a></li>
<li><a href="/wiki/notes/UkrTl5xMh45SMAfs7ei9L">isRelated</a> <a href="/wiki/notes/7fXkqdJWZAjrmGRiEUI0Y">Dolt</a></li>
</ul>
<h2 id="aspects-of-git-that-you-might-want-for-data">Aspects of "Git" that you might want for data<a aria-hidden="true" class="anchor-heading icon-link" href="#aspects-of-git-that-you-might-want-for-data"></a></h2>
<ul>
<li><a aria-hidden="true" class="block-anchor anchor-heading icon-link" id="^aMM7kNHdxfTR" href="#^aMM7kNHdxfTR"></a><a href="/wiki/notes/OS3A5hrl5Q35SVu8Qk5Rt">Version Control</a> 
<ul>
<li>rollbacks</li>
<li>diffs</li>
<li>lineage</li>
<li>branch-merge</li>
<li>sharing</li>
<li>addressability</li>
<li>multiple remotes</li>
<li>staging area</li>
</ul>
</li>
<li><a href="/wiki/notes/kFzBVa3s1or3LKbJuUqrs">Data Catalog</a>
<ul>
<li>thriving open data community</li>
<li>collaborate remotely and asynchronously</li>
<li>pull requests</li>
<li>create issues referring to certain parts of the data</li>
</ul>
</li>
<li><a href="/wiki/notes/wlg4ZLETCHqnRGv5qmRtr">Types</a></li>
<li>transformation can happen externally</li>
<li><a aria-hidden="true" class="block-anchor anchor-heading icon-link" id="^FJEbyfH4liTs" href="#^FJEbyfH4liTs"></a><a href="/wiki/notes/DopNBWXjezcWPthkt4oxm">Data Labelling</a> can happen as statement metadata? </li>
</ul>
<h2 id="three-types-of-solutions">Three types of solutions<a aria-hidden="true" class="anchor-heading icon-link" href="#three-types-of-solutions"></a></h2>
<p>The products fell into three general categories:</p>
<pre><code>1. [[Data catalogs|t.cs.data.catalog]]
2. Data pipeline versioning
3. Versioned databases
</code></pre>

Aspects of "Git" that you might want for data

so You Want Git for Data

public-notes


Welcome! And beware!  

## Purpose

This vault is the "[[learning-in-public|ar.swyx.learn-in-public]]" part of my Second Brain. If you share some of my interests, please [reach out](https://djradon.github.io)! 

## Contents

- [[t]] my personal wikipedia
- [[idea]] (not necessarily mine)
- Resource Notes, including highlights, thoughts and metadata, for various things:
  - [[ar]] mostly articles, papers and web pages
  - [[book]]
  - [[community]]
  - [[course]]
  - [[event]]
  - [[game]]
  - [[loc]]
  - [[org]]
  - [[user]] 
  - [[prdct]] mostly software products, but also ontologies
  - [[recipe]]
  - [[video]] movies, tv episodes, youtube, etc
- [[vs]]
- [[wanted]]
- Some "Metadata Notes":
  - [[tags]] which may refer to any and multiple (or none) of the above
  - [[c]]: ways to categorize resources
  - [[p]]: ways to assert things about resources (mostly abandoned)

In terms of the [[t.km.zettelkasten]] method, this wiki is a commingling of literature notes with something @Sönke-Ahrens warned about: a "personal Wikipedia or a database" [^1]. 

In terms of [[t.tm.getting-things-done]], it's references, someday-maybe, next actions, and public projects.

## Beware!

This is a cluttered cupboard of jumbled jottings riddled with inaccuracies, confusion, and mistakes.

## What This Is Not

- evergreen-notes/digital-garden: for "synthesized" / original-ish publishable big-idea notes that should evolve over time, props to @andy-matuschak and @maggie-appleton
- blog: for "point-in-time" items to be shared: personal news, articles, etc.
  - e.g., [[ar.substack.carpe-noctem]]


[^1]: [[book.how-to-take-smart-notes]]  