Initial readme and description

[anandaroop]

This PR adds a standard README to the project.

Here is some additional background info…

Motivation

In Fall 2016 the metadata team requested the ability to do the following:

• Batch correct partner genomes
• Batch correct Artsy genomes
• Genome Art Fairs
• Perform boolean searches for artworks using genes and tags from The Art Genome Project
  • for genoming purposes
  • for editorial purposes

All of these tasks require interactions that currently either do not exist or are not practical to do on a large scale in Helix, CMS, old Admin, etc.

Some of this is also made much simpler thanks to us having artworks and artists in Elasticsearch now.

Strategy

I made some prototypes to try out the following clump of ideas:

• We can continue to leverage Rails + Kinetic for admin apps
• We can also introduce first-class Javascript in the form of ES6 + React + Webpack
• The two approaches should live together amicably, in their own pipelines, in the same project
• The developer experience should be as 😎 as possible
• We can use Elasticsearch directly for fast, featureful searches that support an admin workflow

The client-side React+Elasticsearch prototype looked like this:

The Rails+Webpack prototype is in a private repo on my account. I've hopefully made most of The Mistakes over there so that this will be a smoother ride over here.

Next steps

We'll build out this idea into a deployable app, in stages:

0. Make the janky prototype itself deployable, so that the metadata team can immediately start to use the initial set of search functionality there for standalone searches, and as an alternate UI into Helix.

1. Rebuild the prototype with tests, better code organization, proper data fetching etc

2. Add the ability for Rosalind to queue updates to big batches of artwork and artist genomes, along the lines of "take these 200 artworks and delete Gene X and add Gene Y at a value of 70"

cc @starsirius @gnilekaw @madeleineb @sarahgottesman

[madeleineb]

✨ 💯 🎉 ✨ 🙌 🙌 🙌