What should I call classes? Is this name too long or too long?

Question

I have the following top-level package: "com.gmail.email.aviersproject". In this top-level package, I have a class containing my main method and the ".summonerdata" package.

My question is what I should call a class inside the summonerdata package. The class will receive caller information using the screen that clears the website.

Since the package that it is in "summonerdata" is the class name SummonerDataScreenScraper is too long? Maybe just "ScreenScraper" or "Scraper" or "SdScraper" or "DataScraper"?

I was told that it is important that class names are descriptive, as short as possible.

Answer 1

There are many examples in the JDK itself. For example, ConcurrentHashMap is in the java.util.concurrent package, but they felt it was clearer to use concurrent in the class name to distinguish it from other HashMaps.

I would use a long name if you only have one Scraper in the whole project, which is SummonerDataScreenScraper, but this becomes inappropriate because there is no alternative. In this case, the short name can be quite clear.