Schools Data Service

Get Started. It's Free
or sign up with your email address
Rocket clouds
Schools Data Service by Mind Map: Schools Data Service

1. Initial Kickoff Notes

1.1. Whats the Current situation ?

1.1.1. Current Drivers

1.1.1.1. High ratio of enquiries via SEO

1.1.1.2. Domain search see this as a competitive differentiator

1.1.1.3. High intent users (property hunting parents)

1.1.2. Pain Points

1.1.2.1. Schools Data not up to date with the ACARA dataset

1.1.2.2. The current data model defines the relationship between a school and a catchment zone as 1:1 which does not reflect the current data sets

1.1.2.3. Updating Schools data at the moment is adhoc and reactive

1.1.2.4. Catchment zone data is in different formats making it hard to keep up to date

1.1.3. Current Customers

1.1.3.1. Domain web

1.1.3.2. Mobile apps

1.2. Where is the data coming from ?

1.2.1. School data

1.2.1.1. Old schools data in the DB

1.2.1.2. Glenn tool

1.2.1.3. ACARA: Current efforts have been to add Acara data to the existing data set

1.2.2. Catchment Zones

1.2.2.1. Old existing catchment data

1.2.2.2. Different state government sites

1.2.2.2.1. NSW and QLD data can be programmatically updated

1.2.2.2.2. Other states data comes in different formats ie PDF documents

1.2.2.3. Glenn tool

1.3. How is the data currently maintained ?

1.3.1. Glenn tool via offshore team, team managed currently by Mike Salway

1.3.2. Adhoc requests to the Wahyu to update catchment zones

1.3.3. Adhoc requests to the platform team (public API: Dave Chang and Duncan Chung did some work recently to match and add acara data)

1.4. Whats the new Value Proposition?

1.4.1. [email protected] will provide parents with reliable schools and catchment zone information

1.4.2. Potential offering to external customers via the Public API

1.5. What are the business requirements?

1.5.1. So what are our next steps ?

1.5.1.1. Breakdown and size the work

1.5.1.2. Reprioritise against other initiatives in the backlog

1.5.1.3. Set expectations with Mike Salway and team

1.5.2. School data

1.5.2.1. Make Acara dataset the source of truth for schools data

1.5.2.2. Maintain current schools (ids) and Match them to their acara counterparts

1.5.2.3. Remove old fields from the schools table that are not used or relevant

1.5.2.4. Support frictionless updating of school data every six months

1.5.3. Catchment zones

1.5.3.1. Support schools that have multiple catchment zones

1.5.3.2. Update Glenn tool to enable an admin to add multiple catchment zones to one school

1.5.3.3. Support to the extent that we can frictionless updating of catchment zone data

1.5.4. CFRS

1.5.4.1. Backwards compatibility with the current APIs

1.6. What needs to be true ?

1.6.1. Should V2 still have the latest data ?

1.6.2. Spike to elaborate options for V3

1.6.3. Spike: Domain Schools Vs Acara schools

2. Why

2.1. Primary Metrics

2.2. Schools data gives an interesting perspective on property and as property core, the ability to serve this to the rest of the business strengthens our mission as the source of truth for property information

3. Goal

3.1. Power the new schools @ domain search experience with the latest schools and catchment zone data

4. Stakeholders

4.1. Current and future stakeholders

4.2. Immediate

4.2.1. Blue dots: Mike Salway and Matt Colman

4.2.2. Search: Ivan Karajas and David Chen

4.3. Keeping Engaged

4.3.1. Mobile: Joanne Lee and Michael Yates

4.3.2. Public API: Lloyd and Duncan Chung

4.4. In conversation

4.4.1. All Homes: Starry Hardjadinata and Michael Shea

4.4.2. Pricefinder: Colin wright and Allan Craine

5. Features

5.1. Customer

5.2. Customer jobs

5.2.1. prioritised list

5.3. Users

5.3.1. Update glenn tool

5.3.2. Validated swagger documentation

5.4. Data

5.4.1. New data structure to support multiple catchments

5.4.2. Import and Match Acara schools to existing schools in database (maintain school id for existing SEO)

5.4.2.1. Only import schools we can match with high confidence

5.4.2.2. For schools with medium confidence, export those and manually verify with the help of the offshore team

5.4.2.3. For those we cannot match at all, verify existence with help of offshore team

5.4.2.3.1. If they exist but have no acara match, maintain them and attempt rematch when a new acara dataset is released

5.4.2.3.2. if they dont exist anymore, do not import

5.4.2.3.3. For Acara schools for which there is no match, add as new schools

5.4.3. Import catchment data for states where we can do it programmatically

5.4.3.1. For states that cannot be programmatically matched at the moment, we will rely on them being manually updated by the offshore team

6. Metrics

6.1. Adoption (leading)

6.1.1. The search platform is using the new API to power school based search

6.1.2. The new user experience on web for schools is powered by our APIs

6.1.3. Mobile

6.1.4. Public API

6.1.5. Pricefinder

6.1.6. All homes

6.2. Impact on user retention (lagging)

6.2.1. Increased retention rates for users pulled in via the school search funnel