Updates the readme to show how to pip install and run a transform.

[daw3rd]

Why are these changes needed?

To show user how easy it is to run a transform.

Related issue number (if any).

#872

[shahrokhDaijavad]

@daw3rd I like the way you have written the Run a transform at the command line section and have moved the stuff about Create a Virtual Environment to the README in the examples folder. I think the paragraph titled Fastest way to experience Data Prep Kit in a Notebook should come first in the Getting Started section, i.e., ahead of running from the command line.

[touma-I]

@daw3rd Let's start an issue and get peer input on what is the best way to solve this problem. We seem to have different stakeholders arguing for different things and also the more you put in the root readme the harder it is to maintain. cc: @shahrokhDaijavad

[daw3rd]

no consensus on utility of cli-based example, for now.

[daw3rd]

@shahrokhDaijavad I have reordered the Getting Started sections.

[shahrokhDaijavad]

Thanks, @daw3rd. This updated README is definitely better than what we have now. Let's wait for others to chime in.

[shahrokhDaijavad]

@daw3rd I tested your run-transform.ipynb on Google Colab successfully by uncommenting the pip install of data-prep-toolkit in the first line. Nice job! Clicking on the Open in Colab icon will only work when this notebook has been merged in dev.

[Bytes-Explorer]

An alternate thought for consideration..
With this PR, we are doing dpk install for a specific transform. But the readme is supposed to help you to get accustomed with the toolkit, so that you can use any transform, learning from a given example. Is there a reason we dont install full dpk? Ideally a one liner like,

pip install dpk
two line example on how to use a given transform

would make the experience simple and easy.

The conda setup etc helps a user not having to struggle with install issues or python mismatch errors. Removing it may cause some extra steps of debugging for the user which may go against the whole effort of simplification. What are we trying to achieve by removing the steps from readme? Understanding that perspective can help us come up with other solutions as well.

@sujee @agoyal26 since this will directly impact first time users, you guys should also chime in.