In 2019 it's a must. Users don't want to see Not Secure near your logo.

• lets encrypt
• yeah, lets

Sale description currently shown in larger font and red text. Do something more pleasent for eyes

When code is updated and merged back to master (either through PR or directly) we should build and redeploy artifacts to the server on OVH. Secrets store in Github Secrets

Since we have a lot of stores which sold items without excise it should be clear to the user what he is buying. Restaurants and Cafes require excise on the alcohol

Add solr collection with stats, where we can gather history stats for each scrapping process
Basic stats shall include

• Total scrapping time
• Total items count
• Scrapping started
• Scrapping finished
• Per provider:
  • Start/Finish/Scrapping times
  • Total count
  • Data Coverage

A lot of people confused about search because there is no search button. Investigate google/duckduckgo search panels and do something similar.

Right now we writing to SOLR, which is obvlious, but would be good to produce CSV or XLS with daily updates

Default links from the search page route to the store, which is ok. But we should provide some icon to open a consolidated product page on our side. It should show description and other props as well.

Show simple page like "Database unavailable, try again later"

Make sure winetime scrapping is stable

When scrapping is finished we get an email with scraping results and possible errors. Would be good to have the email formatted as a table with a list of stores and their results.

Would be nice to have an integration with cocktaildb in one way or another:

http://www.cocktaildb.com

For example: get all alcohol drinks, starting with cheapest, that fit a given recipe. Or get all recipes, in which a given drink participates.

For example if we process category "whiskey" we already know the type of spirit and can append it to solr document

Would be good to track price changes for the specific products. For example how much was the bottle of Glenfiddich 12 year ago?

Tracking can be registered two ways:

• By store specific ID (Goodwine_12345)
• By query (glenfiddich 12 0.7)

Result of tracking should be stored to separate solr collection and it should be a block at the stats page

Epic task to release first minimum viable product which allows users to track prices for whisky for most popular online whisky shops in Ukraine.

• Rest endpoints for /search functionality
• Clean, shippable and generic code for all providers
• Deploy everything to OVH
• Scheduler for daily updates (and trackable via admin interface, forced update)
• Monitoring (logs)

Query results can be cached for the same queries. When new data is available, we should invalidate cache.

We have experienced a number of ways sites utilize paging for the products.
Let's implement the most common strategies, which can be reused by providers.

When accounts available one of the user-specific features could be notify when price changes. For example you want to try out a new whisky but 1000 is a big price for it. You can get email or push (if mobile) about price drop.

It's kinda unclear do we need it or not but it's good for testing to have random button "Мне повезет"

We need to handle russian words by enabling proper stemming algotithm

Flux is abandoned solr client, which prevents to migrate to latest clojure 1.10.

Make sure goodwine scrapping is stable.

Non-distractive background image for search

Whiskybase is a popular resource for whisky lovers which provides ratings, description, etc.
Would be good to provide options for users to see the whiskybase score, and possibly a link

This needed for consumers of priceous service (like bots) and FE for design prototypes

Sometimes we can see something like this:
"Найдено 1 товаров за 0.0 секунд."

1. Change the plural/singluar form, especially having awesome cl-format function
2. Revisit approach to show search time. Is it really needed?

Some stores work better with thread pool with size 20, some with 10, some do not allow more than 3 parralled connections, so would be good to have this configuration per provider.