mysociety / alaveteli

Provide a Freedom of Information request system for your jurisdiction
https://alaveteli.org
Other
385 stars 197 forks source link

Record and show relationships between bodies #4714

Open RichardTaylor opened 6 years ago

RichardTaylor commented 6 years ago

There are relationships between bodies which, if reflected in the public bodies database, and shown on the site, could perhaps enable easier administration and browsing of the site.

Examples of relationships:

This feature could assist browsing the site, and might assist site administration.

Currently administrators can manually add annotations which, for example, lead to a successor body when an organisation is marked "defunct". If we linked such bodies in the database the system could present such links.

It may be possible to do this with special tags eg. Owned_by:Body_Name

RichardTaylor commented 3 years ago

This feature could help deter, or prevent, duplicated requests.

This feature could enable the automated detection of requests made to:

i/ Multiple subunits of an organisation ii/ A subunit of an organisation and the organisation itsself

A specific example would be a request to an academy school, and a request to its multi-academy trust. In such a case a warning might be appropriate rather than preventing a request being made both locally to the school and to the trust.

RichardTaylor commented 3 years ago

A new example of a relationship between bodies

I came across this within the NHS organisation data at:

https://odsportal.digital.nhs.uk/

Their data includes "sites", and there can be multiple organisations at each site.

RichardTaylor commented 3 years ago

Alternatively:

RichardTaylor commented 2 years ago

Consider how we could best deal with bodies which cease to exist in their own right, but become subsumed into others eg.

https://www.whatdotheyknow.com/body/land_and_property_services https://www.whatdotheyknow.com/body/northumberland_college

Notes:

There may be a conflict between what serves our users best, and what is technically correct. Ideally we'd be both technically correct and serve our users as well as possible. One of the key things we try to do though is cut through complexity and confusion.

RichardTaylor commented 2 years ago

Sometimes a successor body has the same name as its predecessor: #6391

RichardTaylor commented 2 years ago

As an example of this being done manually, see notes added to a UK county council page on WhatDoTheyKnow suggesting requesters consider if their request would be better directed to one of the district level councils:

https://www.whatdotheyknow.com/body/lincolnshire_county_council

Even better in this case would be using more tags to describe functions/responsibilities of the relevant bodies to guide users to the right place. Related: https://github.com/mysociety/whatdotheyknow-theme/issues/579

RichardTaylor commented 2 years ago

We can use the existing functions/tools to do this to an extent.

eg. we list

https://www.whatdotheyknow.com/body/at_medics_ltd

and on that page we state

We list the GP surgeries run by AT Medics Ltd separately.

and we link to those bodies tagged run_by:at_medics_ltd

Currently the links from the individual surgeries back to the parent entity are in each individual notes field.

RichardTaylor commented 2 years ago
RichardTaylor commented 1 year ago

More work has been done using the existing tagging system on WhatDoTheyKnow to record relationships between bodies eg.

https://www.whatdotheyknow.com/body?tag=parent_mapit%3A2595

See

and

mdeuk commented 1 year ago

We actually contacted the Department for Education about an uncannily similar thing over the weekend (linking from education authorities to GIaS, the database identifiers are inconsistent with what they advertise) - once we’ve a reply on that one this would be a good set of tasks to join together.

laurentS commented 4 months ago

Jumping in from madada.fr here to mention that we are facing a similar situation with cities merging or splitting (a game they seem to love playing over here). We have addressed this by tagging "old" cities as defunct and adding a note to point to the "new" one, but this is very clunky to do, so I'm modifying the code so that we can use a tag like defunct:<url_name of new body> which would render as something more useful without affecting current functionality.

mdeuk commented 4 months ago

We have addressed this by tagging "old" cities as defunct and adding a note to point to the "new" one, but this is very clunky to do

Agreed - that’s generally what happens on WDTK. When it’s multiple bodies merging into one (or splitting), a tag note is often used.

I'm modifying the code so that we can use a tag like defunct:<url_name of new body> which would render as something more useful without affecting current functionality.

This sounds good. One concern that may, or may not, be an issue, is that some url_name parameters might get reused [^1] - so there may need to be a mechanism to account for that… perhaps the body ID? https://github.com/mysociety/alaveteli/issues/6535

[^1]: for example, WDTK lists a lot of companies, which are government controlled. If there is a significant change to constitution, it is generally part of the process to make one defunct, and add a successor - but, often the url_name will carry over.