Omeka service#43
Merged
Merged
Conversation
…red handling of scope and modified_since variables
… hardware configuration
Contributor
Author
|
@alexdryden, please take a look when you can, it's basically the digital objects integration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces significant enhancements to the
arcflow/main.pypipeline, primarily adding support for digital object processing and improving configuration and timestamp management. The changes enable fetching, updating, and deleting digital objects alongside existing collections and creators, and refactor how timestamps are tracked to ensure accurate incremental updates.Key changes include:
Digital Object Processing and Integration:
process_digital_objects,task_digital_object, and enhancements to repository and deletion handling to support digital objects.Timestamp and Update Logic Refactoring:
last_updated_globaltimestamp to ensure updates are detected across all object types. The update and deletion logic now uses these improved timestamps for more accurate incremental processing.Pipeline and Argument Updates:
process_collections,process_creators,process_deleted_records) to accept explicitmodified_sincearguments and to update timestamps after successful runs, ensuring correct incremental behavior and preventing missed updates.