Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add White Paper #4

Open
12 of 15 tasks
darnjo opened this issue Jan 5, 2022 · 0 comments
Open
12 of 15 tasks

Add White Paper #4

darnjo opened this issue Jan 5, 2022 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation high priority

Comments

@darnjo
Copy link
Member

darnjo commented Jan 5, 2022

The ULI Pilot R&D process will produce a white paper containing the following information:

Business and Outreach

  • Concise outline of the problem being solved with a brief statement of impact and a couple examples where it surfaces, e.g. across state boundaries, data shares with other markets.
  • More formal outline of business needs.
  • Current alternatives to the ULI methodology outlined in the white paper, their benefits and potential downsides.
  • Why are we working on this problem?
  • Statements from Pilot participants conveying their experience using the pilot ULI Service so far.
  • Issues to Address
    • Privacy: How is your member data handled, do others see it, and how do we link markets together?
    • Why is it important to work across borders?
  • How will this solve the problem?
    • Matching Algorithm
    • Collaborative Filtering

Technical

  • Outline of the methodology. How are we doing things differently? 1) Insight: it's a search and matching problem rather than normal data model or transport standards. Describe the search methodology and how it addresses the issues. 2) Novel approach: crowd-sourced, cooperative data scrubber with human review supplemented by probabilistic, consensus based ranking using open source algorithms. The ability to adjust weights based on success and error rates and analytics provides a feedback loop to continue to improve the results over time.
  • Reproducible results to back up our claims that it's a viable solution. This has been tested on M markets with L licensees, and we were able to match with an average score of S, with error rate E.
  • Potential next steps to put it into production. Benefits from shared (neutral) aggregate pool. Make a nice diagram, etc. Rough estimate of resources required to do so.
  • Additional opportunities: same methodology can be used to help de-duplicate listings into their underlying property records. Or anything that has a collection of weighted fields that can be scored and matched against using this approach.
@darnjo darnjo added documentation Improvements or additions to documentation high priority labels Jan 5, 2022
@darnjo darnjo pinned this issue Jan 5, 2022
@darnjo darnjo self-assigned this Jan 7, 2022
darnjo added a commit that referenced this issue Mar 3, 2022
darnjo added a commit that referenced this issue Mar 3, 2022
@darnjo darnjo changed the title Add White Paper to README Add White Paper Apr 5, 2022
@darnjo darnjo unpinned this issue Jan 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation high priority
Projects
None yet
Development

No branches or pull requests

1 participant