-
Notifications
You must be signed in to change notification settings - Fork 20
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
Cordaid organisations, projects duplicate #478
Comments
Duplication of projects is due to Black/Grey lists of Cordaid - these are a one-time thing and will not be repeated with other orgs as mach as possible. Duplciation of organisations is something we have put a fix into RSR to help to manage: #374 This will allow us to mark an existing organisation as either being managed by Cordaid or by another Support Partner. This will allow us to deduplicate the list, ensuring that we do not continue to create duplicates. I am starting this process today with @Anna-Marthe and we'll provide an update shortly on what we'll be doing and how it will be done. |
@adriancollier is there still anything technical we should do about this? Besides implementing the content_owner_id logic in the organisation upload script? |
I don't believe so - we should ensure that the org dupe list is empty (the physical one) as well as also clear the Cordaid items. |
I've added the organisation duplication for Cordaid in #690 |
Test planNone, no work was done for this issue. |
Talked to Pelle and @CharlotteSoed about this as well, but now adding the problem to Github, because the last couple of weeks this happened several times.
http://rsr.akvo.org/project/406/ and http://rsr.akvo.org/project/1075/ are the same projects. 406 already has got some updates. Elma let me know that user Nalugya can't post updates anymore because the organisation attached to the project is now called UGANDA NATIONAL HEALTH US instead of the previous (and same) UNHCO.
I think the problem starts with:
1 Duplication of projects
2 Duplication of organisations
As a consequences, users who are linked to the 'old' organisation can't post updates anymore because the same organisation is overwritten by a 'new' organisation created by Cordaid. Every time this happens we need to change the organisation linked to that user manually. We can't just delete the 'old' organisations because these might be linked to other projects as well. So in the future two organisations that are actually the same, can be linked to different projects again.
We need a structural solution for this, also because in the future we will work with other organisation's PMS.
The text was updated successfully, but these errors were encountered: