# Search field tags

**URL:** <https://discuss.elastic.co/t/search-field-tags/279932>\
**Category:** Elastic Search\
**Created:** [July 29, 2021, 5:07am UTC](https://discuss.elastic.co/t/search-field-tags/279932 "2021-07-29T05:07:04Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![reka.gay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/reka.gay/32/91470_2.png) [@reka.gay](https://discuss.elastic.co/u/reka.gay)\
**Post date:** [July 29, 2021, 5:07am UTC](https://discuss.elastic.co/t/search-field-tags/279932/1 "2021-07-29T05:07:04Z")

</div>

My documents have a `concept` field which has values that act like tags. I would all concepts to be treated individually so I can use them as filters. Imagine e.g. A genre field on a movie database.

With the limitation of `text`, `number`, `date` and `geolocation` (no array) the only thing I could do is add the concepts as a comma-separated string. Is there any way I can make the facet API to split these up and treat them one by one?

I'm going to have similar problem with subheadings: I would like matched (exact) subheadings to be ranked higher in the result so I'm planning to extract the headings and add them to the document. These would not be available as a facet but each comma-separated value should be treated individually and matched as one. Any way to achieve this?

---

<div class="post-metadata">

**Author:** ![Byron\_H](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/byron_h/32/82245_2.png) [@Byron\_H](https://discuss.elastic.co/u/Byron_H)\
**Post date:** [July 29, 2021, 12:12pm UTC](https://discuss.elastic.co/t/search-field-tags/279932/2 "2021-07-29T12:12:24Z")

</div>

Hi [reka.gay](https://discuss.elastic.co/u/reka.gay) (I love the Megamind avatar)

At this time Enterprise Search does not support an "array" field type with the functionality you are describing. Facets are generated from the entire string of the field's value. At this time you will have to rely on our scoring methods to match the contents of these strings containing comma seperated values.

---

<div class="post-metadata">

**Author:** ![reka.gay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/reka.gay/32/91470_2.png) [@reka.gay](https://discuss.elastic.co/u/reka.gay)\
**Post date:** [July 30, 2021, 4:43am UTC](https://discuss.elastic.co/t/search-field-tags/279932/3 "2021-07-30T04:43:18Z")

</div>

Thank you @Byron_H , (I used to be in QA where my job was to concoct evil plans to break things. The avatar was fitting then - and I'm rather fond of it myself. Thank you).

Is handling arrays on the roadmap by any chance?

---

<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:** [November 4, 2022, 8:31am UTC](https://discuss.elastic.co/t/search-field-tags/279932/4 "2022-11-04T08:31:38Z")

</div>


