Feature/pdct 451 add summary endpoint

[katybaulch]

Description

• Replaced dummy response with analytics summary data using count queries on the document, family, and collection services.
• "n_events" is currently set to 0 as we have not implemented events in the admin backend yet (see here. When we implement events in the admin backend, we should update how "n_events" is calculated.

Link to Linear ticket PDCT-451

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. Actual tests to come.

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]

Amazing! This is exactly how it should be done 👍 😺

[diversemix]

Excellent once again! 🍨