# Feature request

**URL:** https://community.mp3tag.de/t/feature-request/16165
**Category:** General Discussion
**Created:** [September 21, 2014, 2:05pm UTC](https://community.mp3tag.de/t/feature-request/16165 "2014-09-21T14:05:09Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![waterfall](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/w/53a042/32.png) [@waterfall](https://community.mp3tag.de/u/waterfall)
#### Post date: [September 21, 2014, 2:05pm UTC](https://community.mp3tag.de/t/feature-request/16165/1 "2014-09-21T14:05:09Z")

</div>

Would it be possible to create a capability within the application to intelligently lookup releases based off within sub folders of a folder?

For example:

directory = 2006 \> album name directory = 2006 \> album name directory = 2006 \> album name

So for all tracks within their respective albums, will be queried as a whole against say, either the beatport or discogs scripts?

Or if you have say a few hundred tracks within mp3tag loaded, have it query all tracks with the same album name and once successfully matched and tagged, automatically move on to the next - querying the next release - offering the user the search results to select from. This would save the user having to continuously select tracks individually run their queries.

I think this would be a really cool feature and help those with large collections trawl through their collections quite easily?

It could be a function that's activated/called upon by having its own menu rather than within the full application as this may not be what users are after all the time?

The functionality/method could something similar to MusicBrainz Picard?

Thank you 🙂

---

<div class="post-metadata">

### Author: ![waterfall](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/w/53a042/32.png) [@waterfall](https://community.mp3tag.de/u/waterfall)
#### Post date: [October 25, 2014, 8:35am UTC](https://community.mp3tag.de/t/feature-request/16165/2 "2014-10-25T08:35:02Z")

</div>

Any consideration?

---

<div class="post-metadata">

### Author: ![garym](https://community.mp3tag.de/user_avatar/community.mp3tag.de/garym/32/4822_2.png) [@garym](https://community.mp3tag.de/u/garym)
#### Post date: [October 25, 2014, 12:04pm UTC](https://community.mp3tag.de/t/feature-request/16165/3 "2014-10-25T12:04:47Z")

</div>

illustrate's PerfectTunes can do this now with regard to artwork, and post-rip accuraterip checking. The plan is for PerfectTunes to begin also offering the ability to add/correct metadata as well.

---

<div class="post-metadata">

### Author: ![waterfall](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/w/53a042/32.png) [@waterfall](https://community.mp3tag.de/u/waterfall)
#### Post date: [November 9, 2014, 1:00pm UTC](https://community.mp3tag.de/t/feature-request/16165/4 "2014-11-09T13:00:45Z")

</div>

Would you mean you can only batch process artwork and not actual tag info just yet?

Thanks for posting back 🙂

---

<div class="post-metadata">

### Author: ![garym](https://community.mp3tag.de/user_avatar/community.mp3tag.de/garym/32/4822_2.png) [@garym](https://community.mp3tag.de/u/garym)
#### Post date: [November 9, 2014, 4:34pm UTC](https://community.mp3tag.de/t/feature-request/16165/5 "2014-11-09T16:34:04Z")

</div>

yes. but the tag info processing/matching is in the work plan for the future. for now, just artwork and accuraterip checking.
