PDCT-451 Added summary endpoint to new analytics route.

[katybaulch]

Description

• Added new analytics router & updated AuthEndpoint and the AUTH_TABLE.
• Added the 'analytics/summary' endpoint returning a dummy response (with the schema below).

{
  n_documents: int,
  n_families: int,
  n_collections: int,
  n_events: int,
}

Another PR to come to flesh this out with the correct data.

Type of change

Please select the option(s) below that are most relevant:

• Bug fix
• [x ] New feature
• Breaking change

How Has This Been Tested?

Tested locally using HTTPie - tests to come in next PR.

Reviewer Checklist

• The PR represents a single feature (small driveby fixes are also ok)
• The PR includes tests that are sufficient for the level of risk
• The code is sufficiently commented, particularly in hard-to-understand areas
• Any required documentation updates have been made
• Any TODOs added are captured in future tickets
• No FIXMEs remain

[linear]

PDCT-451 Add summaries Endpoint

Return the count for DFCE - see peter - put this on GET /api/v1/analytics/summary

Response spec:

{
  n_documents: int,
  n_families: int,
  n_collections: int,
  n_events: int,
}

Suggested Approach

"Thin slices" … I suggest two PRs, this would be good to do - to form the habit of small slices of value:

• First PR will add the endpoint returning a dummy response (same schema as above) - this will/could allow Patrick to start to use it for frontend development.
• Second PR will add a "analytics" service with a summary() to query all the repos for their count - I suggest adding count() to all the repos - also add tests

[diversemix]

Looks great! Assumed you've tested locally 😄