Orphan nodes in collections 774

[HirschSt]

Probably due to the later fixed #1350 bug we have still some collections with "db entry not exists" stuff, e.g. https://muscat.rism.info/admin/sources/452007152/edit. Maybe these records were changed sometimes before the fix.

@xhero Can we use https://github.com/rism-digital/muscat/blob/develop/housekeeping/correct/15_find_orphan_774.rb, or is this a completely different story?

[xhero]

There is something weird going on there, those sources don’t seem to have been deleted? They seem to have been attached to another source.

[HirschSt]

Yes, only the 773 in the children were updated to point to another collection AFAIK.

[xhero]

I think I know what the problem is here: if you delete a 773 and save, it will update the parent and remove the 774, but if you just select another id in the 773, I fear it does not update the old parent. I will have a look.

[jenniferward]

According to the health report, this is the only collection with this problem, and all other ones have been fixed. Herr Schmidt-Hensel deleted the links and unpublished the record on Tuesday.