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

logging for linking process #131

Open
1 task
ericbuckley opened this issue Nov 14, 2024 · 0 comments · May be fixed by #135
Open
1 task

logging for linking process #131

ericbuckley opened this issue Nov 14, 2024 · 0 comments · May be fixed by #135
Assignees
Labels
feature New feature or request qa Technical improvements to increase code quality

Comments

@ericbuckley
Copy link
Collaborator

Summary

Add additional logging statements to the recordlinker.linking.link module to capture key data points of the process. Ideally we should capture enough information to understand why a match, no match or possible match happened.

Acceptance Criteria

  • Add new logging info/debug calls to link.py

Details / Tasks

  • At the pass level
    • Capture information on the blocking call
    • Capture information on the calculated belongingness ratio for each cluster evaluated
    • Possibly, capture information on the comparison results (might be too noisy)?
  • Capture information on the linkage results

Background / Context

Logging context will be important here. The extra kwarg to the logging methods can be used to pass a dict of information about the context of the event. Using this will make it much easier to analyze the records when using a log analysis tool like Splunk.

Dependencies

#91

@ericbuckley ericbuckley self-assigned this Nov 14, 2024
@ericbuckley ericbuckley added feature New feature or request qa Technical improvements to increase code quality labels Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request qa Technical improvements to increase code quality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant