Stat report: quaterly report for marketig

Aperta
#2,876 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 6 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
18/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Ferma
Stack tecnologico
ruby
Ambito
analytics, backend

Direzione di ricerca

The issue lists quarterly marketing metrics (word cloud of domain names, registrations, deletions, renewals, domain counts, plus auction users, auctions, and invoices) but names no files, tests, or existing report code. Start by locating current statistics queries in the admin, registrar, registrant, and www apps and how auction data is reached today. Done means a quarterly report covering those bullets and a way for the registry to obtain auction figures (for example a scheduled export), or a documented decision to move reporting into a separate analytics service.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Report should include:

  • word cloud of most popular words used in domain name from previous quarter
  • new registrations from previous quarter and quarter before that and difference in percentage
  • deletions from previous quarter and quarter before that and difference in percentage
  • renewals from previous quarter and quarter before that and difference in percentage
  • domain count at the end of the quarter and quarter before that and difference in percentage

Now a tricky part

  • auction users - total at the end of the quarter and new users registered during that quarter and difference in percentage
  • number of auctions and invoices - total number of auctions held during the last quarter and number of new auction invoices from the same period

Auction part is tricky as there is no way fro registry to request the info directly from the auction system. So we should create a scheduled request in auction to get the necessary data and make it somehow available for the registry ie by saving the results in csv format to some directory or bucket.

PS: maybe we need a separate statistics/analytic service with data warehouse and reporting and move all the statistics queries and reports from admin, registrar, registrant and www

Lingua principale
Ruby
Stelle
50
Fork
18
Merge medio
5g 3h
PR unite (30g)
2

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di internetee/registry

Tutte le issue di internetee/registry

Issue simili

Altre issue su Ruby

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.