Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display Should Reflect History for Name Change for a Body #49

Open
RichardTaylor opened this issue Jun 9, 2011 · 6 comments
Open

Display Should Reflect History for Name Change for a Body #49

RichardTaylor opened this issue Jun 9, 2011 · 6 comments
Labels
easier-admin Make issues easier to resolve f:authorities improvement Improves existing functionality (UI tweaks, refactoring, performance, etc) user-experience x:volunteer

Comments

@RichardTaylor
Copy link

Currently when a body changes its name the requests from both before and after the change carry the new name of the body.

Ideally requests / correspondence from before the change ought be associated with the old name; and those after the change with the new.

@RichardTaylor
Copy link
Author

Ben has noted that sometimes a name is changed because the old one was never correct - in these cases the name change should be retrospective.

Nothing is ever simple!

@bjh21
Copy link

bjh21 commented Jun 9, 2011

And for added complication, sometimes we're late with a name change and so some requests should be updated and others not. I think the most general approach would be for the authority to have a list of names together with the dates from which they were correct, so then the right name can be attached to each request.

@sebbacon
Copy link
Contributor

sebbacon commented Aug 9, 2011

Or how about just when there has been a name change, a small indicator or link indicating "this authority has been called different things in the past", and listing its different names? Just as a cheap fix.

(Or just "previously called X, Y, and Z on this site" on the authority listing)

@bjh21
Copy link

bjh21 commented Aug 9, 2011

I think that would be less good than what we currently do on WhatDoTheyKnow, which is to create a separate record for each name and link them together with notes. The major shortcoming of this is that we have n different pages of requests for the n different names. Your suggestion would solve this, but at the expense of putting the wrong names on all the old requests, which I think is worse.

@tmtmtmtm
Copy link
Contributor

tmtmtmtm commented Feb 4, 2012

This explanation of how we currently create a new record on WDTK should be in the guide for people installing international versions.

@RichardTaylor
Copy link
Author

#285 is the analogous ticket for username changes without changing history.

Current practice on WhatDoTheyKnow is to change the name of a body but note the previous names in the notes field.

We get examples where this feature would be useful reasonably regularly. A name change we carried out today was on:

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

@garethrees garethrees added f:authorities improvement Improves existing functionality (UI tweaks, refactoring, performance, etc) labels May 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
easier-admin Make issues easier to resolve f:authorities improvement Improves existing functionality (UI tweaks, refactoring, performance, etc) user-experience x:volunteer
Projects
None yet
Development

No branches or pull requests

6 participants