[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[EP-tech] indexcodes.txt CHECKSUM



Hi Tomasz,


I thought you should be able to do that with epadmin


/opt/eprints/bin/epadmin rehash <ARCHIVEID> <DOCID>


But this does something interesting but not particularly useful to your 
predicament.? I don't think there is any programmatic way to regenerated 
the hash for a file at the moment.


I can see you have generated a GitHub issue for this: 
https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feprints%2Feprints3.4%2Fissues%2F201&amp;data=04%7C01%7Ceprints-tech%40ecs.soton.ac.uk%7Cf14ac570b2f047db04da08da008a1cb6%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637822890440341997%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=jShtHoepL9bUr8RWB4Yo8DmgzEsVHN0ln4jFbzoDu%2FI%3D&amp;reserved=0


I think this should be an epadmin command line option:


/opt/eprints3/bin/epadmin redo_hashes <archiveid> file <fileid1> 
<fileid2> ... - Regenerate hashes for all the file ID listed using the 
current hash type specified or default to md5 (maybe have a flag for the 
hash type)


/opt/eprints3/bin/epadmin redo_hashes <archiveid> document <docid> - 
Regenerate hashes for all the files associated with the document with 
docid. (Allow multiple docids to be specified).


/opt/eprints3/bin/epadmin redo_hashes <archiveid> eprint <eprintid> - 
Regenerate hashes for all the files associated with all documents 
associated with eprint with eprintid. (Allow multiple eprintids to be 
specified).


This is a bit like the redo_mime_type epadmin option but update the hash 
(and potentially hash_type) rather than the mime_type.


I have updated the GitHub issue to reflect this proposal.


Regards


David Newman


On 07/03/2022 4:55 pm, Tomasz Neugebauer via Eprints-tech wrote:
> *CAUTION:* This e-mail originated outside the University of Southampton.
> Hi everyone,
>
> I got an unusual issue in that during export to archivematica, one 
> deposit (out of thousands processed so far without this issue) has an 
> incorrect checksum value stored for the indexcodes.txt file.
> How can I get EPrints to re-assign/re-evaluate the indexcodes.txt 
> checksum value?
> I tried running epadmin reindex on the eprint, and a new 
> indexcodes.txt file was generated, but the checksum value for it seems 
> not to be updated.
> Would "epadmin rehash" on the document do the trick?
>
> Tomasz
>
> PS.? Also, I have the impression that I'm no longer seeing messages 
> from this list in my inbox, anyone else experiencing issues with that?
>
> *** 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%7Cf14ac570b2f047db04da08da008a1cb6%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637822890440341997%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=PpAdnqzGrJm6WdtkffOaV2f0%2BM2fgRy4%2BGEog2x31f8%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%7Cf14ac570b2f047db04da08da008a1cb6%7C4a5378f929f44d3ebe89669d03ada9d8%7C0%7C0%7C637822890440341997%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=I2CatTy0i4kIy00gTkZ38V6IWHHeI%2BglTOUay5lpryU%3D&amp;reserved=0
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ecs.soton.ac.uk/pipermail/eprints-tech/attachments/20220307/b2ae7419/attachment.html