Thanks Stuart - we do have other administrator accounts already so can still do admin things ok (the one that got deleted was the original one created via that script many moons ago). Before posting this I didn't realise there was functionality in Dspace 7 to allow for deletion of e-person accounts with associated submissions (since found the PR related to it), was actually wondering how on earth it happened in the first place. Now we are grappling with whether to try and reinstate that account and all its ties to former submissions via database edits (seems like it will be a bit painful to update all the right tables) or just to let it go, leave the submissions as orphans and create a new admin account with the same groups as the old one to use going forward. Unsure if there are now some items possibly stuck in workflow pools or if the account deletion process would have taken care of all that nicely - if the latter is true we will likely not bother to try and reconnect the orphan submissions.
Kind Regards, Romy On Friday, September 22, 2023 at 3:36:16 PM UTC+12 sye...@gmail.com wrote: > Assuming that you're running 6.x or 7.x, there's a command documented at > https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace for creating a > new dspace administrator account. > > cheers > stuart > > On Friday, 22 September 2023 at 10:02:26 UTC+12 Romy Forrer wrote: > >> 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 dspace-tech+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/3be9e3de-593f-4b54-ab09-87e8f4df88e9n%40googlegroups.com.
