EPrints Technical Mailing List Archive

Message: #08368

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] Trying to understand a disaster after a database update

CAUTION: This e-mail originated outside the University of Southampton.

I would check the apache logs, maybe there's some hint or error that can
help you on finding the cause of eprint removal. Also check the mysql
history, maybe you made some mistake and deleted the eprint table contents.

If anything works, just recover from a recent backup and follow David
advice on moving fields. Eprints recommit accept a list of ids, you
should have tested your sql changes on few elements.

epadmin recommit repository_id dataset_id [eprint_id eprint_id ...]

Il 16/11/20 12:09, David R Newman via Eprints-tech ha scritto:


Hi Laurent,

So to confirm: Are there are no records in the eprint database table
or you just don't see any records when you look at the Manage Deposits
page in the repository?  When you ran recommit at the end of your set
of instructions.  How long did this take to run and how many record
did you have before you started this whole process?  If it took quite
a long time then it suggests some how the recommit process caused you
problem.  However, if it ran quickly this suggests you eprint records
were already deleted or broken so could not be displayed in the Manage
Deposits page.

As a general comment on your solution.  I would have not dumped out
and reimported database tables.  I would have created a rule (block of
code) in your archive's cfg/cfg.d/eprint_fields_automatic.pl to map
(probably just copy) the old field to new field.  You would have still
had to have the old field defined in eprint_fields.pl but as long as
you had removed the old field from the eprint workflow and any other
config files (except eprint_fields_automatic.pl and eprint_fields.pl)
it should not be editable, or visible to non-logged in users.  You
would then need to run epadmin recommit like you did in your original
instructions and once this completed you could remove (probably best
to comment out) references to the old field and the rule to map the
old field to the new field.

Regards

David Newman

On 16/11/2020 10:49, Laurent Cloarec via Eprints-tech wrote:

*CAUTION:* This e-mail originated outside the University of Southampton.
Hello everyone

The initial problem : many (about 1,000) metadata values entered by
archive editors in a non appropriate field (used in parallel for
another purpose by another import mechanism), let's say "infoX". Into
the database, this information was stored in a table looking like
"eprint_creators_infoX(eprintid,pos,creators_infoX)"

The solution employed :

 1. create a new metadata/field (let's say "infoY") among the
    creators metadata (with "eprints_fields.pl") and update the
    database structure in consequence => creation of a new table
    "eprint_creators_infoY(eprintid,pos,creators_infoY)"
 2. backup (SQL values dump) the important values previously entered
    and stored into the "eprint_creators_infoX" table;
 3. from this backup, create a new SQL file where the "infoX" column
    name is replaced by "infoY";
 4. import these values into the new table ""eprint_creators_infoY";
 5. delete the previously entered value from "eprint_creators_infoX"
    table (/there was an objective criteria to distinguish the
    entered from the imported values/);
 6. run "bin/epdamin recommit <archivename> eprint"

The disaster/issue that happened : all the records from "eprint" main
table have been deleted, and the archive/repository consequently
appears as empty!!!

Could someone explain this???

Best regards
--
Laurent Cloarec
Service Commun de la Documentation - Service du Numérique Documentaire
Université Toulouse 1 Capitole

*** Options:http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive:https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&amp;data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cb14e51a1a62342d537ab08d88a334a23%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637411300178733901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=xA4o9%2Fp9Y3%2FrqcgwwdY8KR8IrmLSM92wk%2BubPCPszZY%3D&amp;reserved=0
*** EPrints community wiki:https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.eprints.org%2F&amp;data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cb14e51a1a62342d537ab08d88a334a23%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637411300178733901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=6AJ5bMovpV%2Bk2eidJnZF6DyoMINdzuzWc8jaad89%2FIU%3D&amp;reserved=0


<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.avg.com%2Femail-signature%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Demailclient&amp;data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cb14e51a1a62342d537ab08d88a334a23%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637411300178733901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=xNL47XsakJx0s7%2BB4DKZ4yPL20Cjho5PJsFQFTrVgic%3D&amp;reserved=0>
      Virus-free. https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.avg.com%2F&amp;data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cb14e51a1a62342d537ab08d88a334a23%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637411300178733901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=nGcfLWDplBubO4rvvi9PaaJg6Z3%2FDpeWWz39hswRo%2BM%3D&amp;reserved=0
<https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.avg.com%2Femail-signature%3Futm_medium%3Demail%26utm_source%3Dlink%26utm_campaign%3Dsig-email%26utm_content%3Demailclient&amp;data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cb14e51a1a62342d537ab08d88a334a23%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637411300178733901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=xNL47XsakJx0s7%2BB4DKZ4yPL20Cjho5PJsFQFTrVgic%3D&amp;reserved=0>


<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

*** Options: http://mailman.ecs.soton.ac.uk/mailman/listinfo/eprints-tech
*** Archive: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.eprints.org%2Ftech.php%2F&amp;data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cb14e51a1a62342d537ab08d88a334a23%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637411300178743901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=oNaS3C064p4D1Q7BnKg9Akyf1tIPLxVz66zeBB%2FpuDI%3D&amp;reserved=0
*** EPrints community wiki: https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwiki.eprints.org%2F&amp;data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cb14e51a1a62342d537ab08d88a334a23%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637411300178743901%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3k%2Bdo0bBgbeBCYlyZ4SAxzOWVEH1ozk0HMnpG0WNY3k%3D&amp;reserved=0