Get Local Plans data into Provide tool

[Ben-Hodgkiss]

We need to ensure that the local plans seeded data is available in the Provide service (at least development) for testing. Currently it is showing for standard local plans, but we will need to fix it to work for Joint Local Plans.

Steps:

• Fix organisation-builder to include Local Planning Groups - @eveleighoj
• Discuss the intended design for Joint Local Plans - @paris-dp to lead
• Fix provision-rule (if needed) following discussions - @Ben-Hodgkiss
• Implement fixes to Provide - @pooleycodes

[Ben-Hodgkiss]

Change Required to Provide Service

We have recently introduced Local Planning Groups which are collaborations between multiple LPAs for the purpose of creating local/minerals/waste plans. We have updated the organisation.csv to include the LPGs and introduced the organisations column which contains the semicolon separated list of LPAs in that group.

Currently the LPA Dashboard and subsequent pages only return details for that LPA. We need to amend the queries on the service to include both entities from the organisation in question as well as any entities from any LPGs that contain that LPA in its organisations list.

We should also introduce capitalising the first word of a dataset name across the platform - specifically the LPA Dashboard page, titles when you go into the dataset details, and guidance link but there could be other places as well.

[Ben-Hodgkiss]

Discussion between @pooleycodes, @Ben-Hodgkiss, @paris-dp and @sianteesdale.

The technical approach above will involve rewriting every query in the Provide service so that organisation is accepted as an array, rather than a single item. This will take a significant amount of time to change, plus will then require most of the 750 tests in the platform to be edited.

There was also discussion as to whether this approach is the best way forward, especially without any designs to notify users as to when data is coming from an LPG vs their LPA.

@pooleycodes has created a branch which shows an information box when an LPA is part of an LPG that could be used.

ACTIONS

• Block ticket until further discussion can take place on how to solve this issue
• @Ben-Hodgkiss and @paris-dp to discuss potential designs for Joint Local Plans in person on 12/02
• Aim to have high-level discussion and decision on w/c 16/02

[paris-dp]

Notes were shared with Paul on 19th Feb and discussed in my 1:1 on 20th Feb. Outcome- Paul is going to model data architecture for collecting joint local plans

[paris-dp]

Suggested 3pm today for a meeting to discuss this- awaiting confirmation

[Ben-Hodgkiss]

@pooleycodes - can you update with the result of your discussions on Friday please?

[pooleycodes]

Joint Planning Groups – Data and UI Model

The proposed model works as follows (Using Babergh as example):

Organisation Overview Pages

• The Babergh overview page displays all datasets provisioned against Babergh.
• It also shows a banner if there are other organisations babergh is a part of.

Local Plans View

• The Local Plans dataset page shows:
  • Data submitted directly by Babergh

Joint Planning Group Detection

• The service checks whether Babergh is part of a joint planning group. that is also provisioned to provide that data.
• If Babergh is part of a joint group:
  • A banner is displayed at the top of the Babergh dataset pages which that joint plan are also provisioned to provide the dataset
  • The banner links to the relevant joint planning group page

Joint Planning Group as an Organisation

• A joint planning group is provisioned as an organisation in its own right.
• The joint group:
  • Appears in organisation lists
  • Is provisioned only for the datasets it is responsible for providing
• The joint group organisation page displays only those datasets it is provisioned to provide.

Attribution Within Joint Contexts

• Within Local Plans dataset, it remains clear:
  • Which datasets were provided by only by Babergh
  • Which datasets were provided by only by Mid Suffolk
• Joint group membership does not obscure or override individual authority attribution. any datasets provided as a joint plan can only be found in that dataset page.
  ``