Case Study write-up: WMR

[popovayoana]

Overview

Create a Datopian case study for WMR: https://data.winnipegmetroregion.ca/

Follow the official case study template:
https://docs.google.com/document/d/1cjbMYSV-_KHpOLToqvhCSFepPPoAu3TmCPyaDeFYAIU/edit?usp=sharing

or

You can do lighter mode of a case study, see below:

Format	Written case study, 600–800 words. No video required.
Audience	Government officers evaluating PortalJS Cloud. Municipal and regional data leads.
Portal URL	https://data.winnipegmetroregion.ca/
GitHub	#1554
Pain point	Government evaluators need social proof from organisations like theirs. A live portal with operational detail is more persuasive than any feature list.
Objection addressed	"Can it handle a real government deployment? What does it actually look like in production?" — A named, live, working portal answers this directly.

Structure

• Context: Who is Winnipeg Metro Region? What data do they publish? What was the situation before?
• What they needed: Specific requirements — compliance, accessibility, ease of publishing, public-facing UX.
• What was built: What PortalJS Cloud features are they using? Any customisation? Any CKAN integration?
• What it does now: What datasets are live? What does a citizen or staff member actually do on this portal?
• Outcome: One quote if available. If not, describe the outcome in factual terms only.

What William needs to deliver

• Answers to the structure questions above
• Any internal context on the build: what was technically interesting, what the client asked for, what the migration involved.
• Confirmation of what features are live and what is accurate to claim.

Point of Contact

If there are questions or missing information, contact: @demenech

[popovayoana]

@demenech to provide context for this

[popovayoana]

WMR onboarding issue: https://github.com/datopian/portal-wmr/issues/1