I am currently using the Omnivore API in a script that runs daily at 20:30 UTC (to send articles to kindle, see https://github.com/omnivore-app/omnivore/issues/2142#issuecomment-2323465807) . The script automatically retrieves articles based on a filter by date (e.g., saved:YYYY-MM-DD..*). However, I've encountered an issue where articles saved on the same day can appear in multiple runs (ie books). For example, an article saved earlier in the day could be retrieved both in today's and tomorrow's run, leading to duplicate entries in my processing pipeline.
To solve this, I would like to request support for filtering articles with datetime precision. This would allow users like me to filter articles based on both date and time, and avoid retrieving the same articles in consecutive runs of the script. For example, a filter like saved:2024-09-07 20:30:00..* would be ideal.
Hello Omnivore team,
I am currently using the Omnivore API in a script that runs daily at 20:30 UTC (to send articles to kindle, see https://github.com/omnivore-app/omnivore/issues/2142#issuecomment-2323465807) . The script automatically retrieves articles based on a filter by date (e.g.,
saved:YYYY-MM-DD..*). However, I've encountered an issue where articles saved on the same day can appear in multiple runs (ie books). For example, an article saved earlier in the day could be retrieved both in today's and tomorrow's run, leading to duplicate entries in my processing pipeline.To solve this, I would like to request support for filtering articles with datetime precision. This would allow users like me to filter articles based on both date and time, and avoid retrieving the same articles in consecutive runs of the script. For example, a filter like
saved:2024-09-07 20:30:00..*would be ideal.Thanks for considering this request!