Review and triage issues from pecanproject/bety

Including, but not limited to, issues labeled

Each open issue should be

closed with rationale OR
migrated to this repository
- in entirety using 'transfer issue' or
- as a new issue, summarized from the original

@dlebauer

Sir @dlebauer I completed an initial triage pass :

32 issues are in the constraints/qaqc baseline; 13 related integrity issues were also found.
#206: duplicate variable names need a decision on whether they are intentional aliases.
#250: production-only; betydata has no users/authentication data.
#340: exported references are valid; unused public-export treatments are not proven orphaned.
#172 and #640: the package export has broken pfts_priors references and duplicate PFT-variable prior pairs.

Please confirm these triage rules before I create successor issues or recommend any closures or transfers.

Thanks for doing this. Could you please summarize specific findings in a spreadsheet? That will make them easier to review.

Navigation Menu