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

econservation: Topic 3: How will the original tab Condition be affected by Checks? #1239

Open
rondlg opened this issue Jan 6, 2025 · 1 comment
Labels
econservation This issue relates or refers to the conservation module workflow This issue generated either a change to an existing workflow or created a new one

Comments

@rondlg
Copy link
Member

rondlg commented Jan 6, 2025

DISCUSSION POINTS:

  • Used to record the condition for treatment and for condition reports.
  • Old loan condition reports (handwritten) are physically transcribed from handwritten to typed text in this tab.
  • Old loan condition reports (PDF) may be physically transcribed into this tab -- it is not clear how this will work.
@rondlg
Copy link
Member Author

rondlg commented Jan 6, 2025

DECISION(S): Going forward, each condition record will be a separate conservation record which will be a child of a master condition report see Topic 2.

DATA CHANGES: None
Data Changes Doc
Pre new development
Post development

@rondlg rondlg added workflow This issue generated either a change to an existing workflow or created a new one econservation This issue relates or refers to the conservation module labels Jan 6, 2025
@rondlg rondlg changed the title econservatiokn: Topic 3: How will the original tab Condition be affected by Checks? econservation: Topic 3: How will the original tab Condition be affected by Checks? Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
econservation This issue relates or refers to the conservation module workflow This issue generated either a change to an existing workflow or created a new one
Projects
None yet
Development

No branches or pull requests

1 participant