Hi there Hoping someone can advise on the best course of action to deal with someone accidentally deleting our administrator eperson account. Luckily we have another one with admin privileges as well so can still perform admin functions but I am worried that deleting the original one will have functional consequences. We are on Dspace 7.6 and migrated/copied over our dspace 6.3 PostGres database plus have a dev/test server where the account still exists so I have the eperson data, plus epersongroup2eperson data that is likely to still be current from the database. However there will have been other tables with associations to that eperson_id to try and re-populate. Is there a list somewhere of all the tables where that eperson would typically be referenced? Is it relatively safe to insert an eperson to the database via SQL (We have a DBeaver interface we use to query the database etc.) or should we be creating the account fresh via the admin GUI? We do keep postgres database backups but I have never had to load any before and am not all that confident to reload from backup (alas our most experienced dspace colleague is away on holiday) and don't want to risk losing new submission added since last backup.
Be fantastic to get some advice around how to handle this. Kind Regards, Romy Romy Forrer Library Systems Coordinator University of Canterbury -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/34fb4710-adc8-42f5-9125-fef3de0d82b0n%40googlegroups.com.
