Open
Conversation
A sketch of how to use the entity-organisation config to give facts from the authorititive source for an entity priority over facts from other sources. Depends on a new pipeline.sqlite3 database
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.
Spike: needs more work before merging!
Assign and order facts based on a priority value.
Entries, and facts from an entry, are assigned a priority, 1 for facts from the organisation, 2 for facts from elsewhere.
Facts with the highest priority (1) are used for the entry ahead of the lower priority (2).
Depends on a new var/cache/pipeline.sqlite3 database, which can be built from the config by the load-pipeline.py script.
Tested with the conservation-area-collection branch:
https://github.com/digital-land/conservation-area-collection/tree/entity-organisation