Overview

I encountered an issue where the Omeka S OAI-PMH repository’s resumptionToken was outputting a [badResumptionToken] error even though the token was still within its expiration period.

Here are my notes on how to address this bug.

Solution

By adding a comparison between $currentTime and $expirationTime to the following file, tokens within their expiration period are now properly retained.

p{riva$$]f}tae)oepx-rip>efi'ga$$i}u=reeccef nexthux/c$dpCrp(/ttTio(ri!$ihorn$er$aAoiketenaepdnsedexttxid-n'npTip-er>stiioi>des=(rmnrdse=>)eeTeeur;didlmv$tT=mTeeiaroeotLcpuknkeieieee=e(sL-,nwn'to>s$oRcs\eaeaeaDxistasappporti$morc$erchn-heTeu_s>(xidrreg'pmTre(eoieoep$tar(knot(ie)etso'pd;nTikCmT-iteoho>monn_keer)trexy:renAp>_op)ditlodr$ools{eaekieidtxedrtipnPooislrnr'uy(a,g_)tit;i$no eMknxaeTpnniiasAmrg'deee,d)dreT'[d{o) k-/e>/ng-eA>tdi(dd'e(ad)p)i;');

There were cases where things worked without this fix, so there may be differences depending on the PHP version, etc.

References

For reference, I checked the contents of the table created by the OAI-PMH repository module.

m8myysFivmcfusersi111111qideeurnexoqd89012345lertrottpwl>lbasmiis>ddolrDaraiSvLLLLLLLLEttnEeiiiiiiiiSaiLrssssssssC_osEbttttttttRpneCRRRRRRRRIrtTeeeeeeeeBeccccccccEf(ooooooooi0rrrrrrrrox.Fdddddddda0Rssssssssi1OpMmTivviddvdshynaanaaaaeomoooooooorptrrtttrtcaeaaaaaaaaeecceece)itiiiiiiiiphhtthtpa________oaaiiaimdddddddddsrrmmrmhacccccccci((ee(ertt111eao599p_r)00opy))sr_iettfooikNNNNNYYYNrxeuOOOOEEEOynlSSS_;ltockuerKPMns11112eRUo55055050yILLr00000000IMIDNNNNNNNNTfNNNNNNNNeUUUUUUUUrUUUUUUUUfLLLLLLLL1oLLLLLLLLaLLLLLLLL0mLLLLLLLLu;ltuNNNNNNNNnUUUUUUUUtLLLLLLLLEaiLLLLLLLLxulttroa_isNNNNNNNNneUUUUUUUUctLLLLLLLLrLLLLLLLLemene22222222tx00000000p22222222i44444444r--------a11111111t00000000i--------o11111111n000000000000000077778888::::::::0000111177776666::::::::4445334404941614

Summary

There may be some incomplete aspects, but I hope this serves as a useful reference.