EPrints Technical Mailing List Archive
See the EPrints wiki for instructions on how to join this mailing list and related information.
Message: #08882
< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First
Re: [EP-tech] indexcodes.txt CHECKSUM
- To: <eprints-tech@ecs.soton.ac.uk>, Tomasz Neugebauer <Tomasz.Neugebauer@concordia.ca>
- Subject: Re: [EP-tech] indexcodes.txt CHECKSUM
- From: David R Newman <drn@ecs.soton.ac.uk>
- Date: Mon, 7 Mar 2022 22:30:40 +0000
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://github.com/eprints/eprints3.4/issues/201
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
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: http://www.eprints.org/tech.php/ *** EPrints community wiki: http://wiki.eprints.org/
- References:
- [EP-tech] indexcodes.txt CHECKSUM
- From: Tomasz Neugebauer <Tomasz.Neugebauer@concordia.ca>
- [EP-tech] indexcodes.txt CHECKSUM
- Prev by Date: Re: [EP-tech] indexcodes.txt CHECKSUM
- Next by Date: [EP-tech] trunked DOI on citation
- Previous by thread: [EP-tech] EPrints/CRIS
- Next by thread: [EP-tech] DOI handling in orcid_support_advance
- Index(es):