Skip to content
This repository has been archived by the owner on Feb 1, 2024. It is now read-only.

Include contributor verified status when sorting extended fields and prioritize claim over most frequent #1570

Closed
jwalgran opened this issue Jan 5, 2022 · 0 comments
Assignees

Comments

@jwalgran
Copy link
Contributor

jwalgran commented Jan 5, 2022

Overview

Include contribuor verified status when sorting extended fields and prioritize claim over most frequent

Describe the solution you'd like

  • Rename ExtendedField.trusted to ExtendedField.is_trusted to be consistent with Contributor.is_trusted
  • When sorting results
    • Consider Contributor.is_trusted in addition to ExtendedField.is_trusted
      • Sort by count of trust flags (2, 1, or 0)
    • Prioritize claimed ahead of most frequent when sorting
  • Include the other_names/_addresses/_locations information with the extended_fields when serializing to allow proper server-side sorting and inclusion of contributor data
  • Prioritize the name/address/location from an active/verified facility claim over the facility object's name/address/location when serializing the Facility.name, Facility.address, and Facility.location (unless it is in embed mode and prefer_contributor_name is active, in which case prefer the contributor name)
  • Adjust the created_from to hide other contributor information in embed mode
@jwalgran jwalgran changed the title Include contribuor verified status when sorting extended fields and prioritize claim over most frequent Include contributor verified status when sorting extended fields and prioritize claim over most frequent Jan 12, 2022
@TaiWilkin TaiWilkin self-assigned this Feb 3, 2022
@TaiWilkin TaiWilkin mentioned this issue Feb 7, 2022
3 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants