Repository navigation
Fix repository dashboard accuracy and source links - #20
Merged
Merged
Conversation
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
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.
The repository dashboard counted overlapping and archived source memberships as current records, omitted untagged published records from its total, and labeled migrated records as not yet synced. Count unique records in active sources and all published database records, show Archived/Disabled/Active status separately from historical harvest results, and describe overlaps without implying a synchronization failure. Clearly label database counts and their distinction from live index verification.
Normalize GitHub repository links to include the OpenGeoMetadata organization when metadata is incomplete. Add a Search API link to every row using that repository as the active
ogm_repofilter. Preserve unknown Aardvark status rather than assuming presence.Validation:
No production deployment is included in this PR.