Record not processed because submitted version: 1704539208 is less or equal to previously submitted version 20240105072246102
Hello, and thanks for your message.
Each time a given DOI is updated, our system requires that the value in the xml is numerically larger than the previous submission’s . The purpose of this is to prevent someone from accidentally overwriting newer metadata with older metadata, if they happen to submit an outdated xml file.
Ensuring that each timestamp is numerically higher than the last is typically accomplished by using a standard date-time format to construct the timestamp when the xml files are created.
However, different systems use different date-time formats, so when a DOI needs to be updated by a different organization than the one that first registered or last updated it, or if you’re using a different system to produce the xml, there can be instances where a smaller timestamp value is used after a larger one. This will cause the deposit to fail.
We can reset the timestamp when necessary, after a title transfer or system change, etc. If you can send me a list of DOIs that need to be reset, I’ll change their timestamps to something smaller. Then, you can proceed with your update submissions.
If you ever need to check the most recent timestamp for a given DOI, you can find it in the previous metadata deposits, the xml api record, or the depositor report for the relevant journal.
Also, please note, if your xml is constructed in a way that you’re repeating the same DOI multiple times in a single deposit, this will always result in a timestamp error for all but the first instance. This is okay, and you can ignore the error in that case as long as the metadata is accurate and up to date.
Best,
Evans
1 Like