Skip to content

🔄 Update reinv parameter name #2

@JFWooten4

Description

@JFWooten4

This column in the PII DB should really be reInv for reinvestment preferences (for clarity), since it takes up the same amount of space data-wise.

Also, hold (bool) / holdWhy (S) can be trivially refactored to just be hold (S), where reasoning is required and can be analyzed to interpret as bool(string)==TRUE.

Lastly, let's look into the dot classification of Minor registrations v. full mini records (as implemented in legacy imports..) using proper fields as applicable. This should make it easier should we need to find children in foster care after physical emergencies.
^ Violates the association resolution scheme. Still worth considering if no line of inheritance on the parent account, but generally tough to get PII consent for minors...1

Footnotes

  1. This sounds a lot more like a UI issue since you can pull the info from parent(s) (if joint) and just infer from the inherited signing schemes on-chain. Namely, you don't need this data explicitly individualized presuming the same fundamentals between householded accounts. Ofc this defers to our individual delivery choice for marriages given low delivery costs and preference for accuracy and democratic participation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions