# GEM - GUI for Elasticsearch Mappings

**URL:** <https://discuss.elastic.co/t/gem-gui-for-elasticsearch-mappings/68100>\
**Category:** Elastic Community and Ecosystem\
**Created:** [December 5, 2016, 8:18pm UTC](https://discuss.elastic.co/t/gem-gui-for-elasticsearch-mappings/68100 "2016-12-05T20:18:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![siddharthlatest](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/siddharthlatest/32/10050_2.png) [@siddharthlatest](https://discuss.elastic.co/u/siddharthlatest)\
**Post date:** [December 5, 2016, 8:18pm UTC](https://discuss.elastic.co/t/gem-gui-for-elasticsearch-mappings/68100/1 "2016-12-05T20:18:21Z")

</div>

I would like to introduce GEM, a GUI for Elasticsearch Mappings. Here is the [github link](https://github.com/appbaseio/gem).

GEM is at the first step towards true data modeling where it makes the mappings process very accessible. For someone coming from a SQL background, mappings in Elasticsearch are interesting because of it's nature of being both a search engine and a data store suited for exact queries and aggregations.

Would love it to eventually have some intelligence and heuristics built in, like recommending what data types to choose, data normalization patterns.

A preview of how it works -

 ![GEM Preview](https://camo.githubusercontent.com/5f14dd81d247722ee171365d4dcef2ff652128e8/687474703a2f2f692e696d6775722e636f6d2f513666454b55692e676966)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 2, 2017, 8:19pm UTC](https://discuss.elastic.co/t/gem-gui-for-elasticsearch-mappings/68100/2 "2017-01-02T20:19:18Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.