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

Record date policy #27

Open
JoselleAstrid opened this issue May 10, 2022 · 0 comments
Open

Record date policy #27

JoselleAstrid opened this issue May 10, 2022 · 0 comments
Milestone

Comments

@JoselleAstrid
Copy link
Member

JoselleAstrid commented May 10, 2022

Old FZC has one date field for records. New FZC will probably have two fields: date achieved and date submitted.

  • When we port records from old FZC to new FZC, do we transfer the old FZC date in as the new FZC's date achieved, date submitted, or both? (Currently, it's transferred in as date achieved, and the date submitted is the date the record was transferred in.)
  • In general, do we want to make sure every record has date-achieved filled in? Or is it better to only fill it in when we're reasonably sure it's accurate (i.e. when the record was actually achieved by the player)?
  • What date is better to use for WR history purposes, considering that hoarding happens sometimes? Should 'date proof was provided' or 'date verified' be considered?
  • Don't make this too complicated - ultimately our policies need to be easily understood.

There may be more considerations as well. When in doubt, look at how other communities handle things. A lot of folks out there care about their community's WR history.

@JoselleAstrid JoselleAstrid added this to the 0.3 (1.0 for web) milestone May 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant