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

Auto-guess expiration dates #6

Open
lentschi opened this issue Aug 25, 2017 · 0 comments
Open

Auto-guess expiration dates #6

lentschi opened this issue Aug 25, 2017 · 0 comments

Comments

@lentschi
Copy link
Owner

(Originally brought up by @sap7772000zilla via email and @benfreu via Slack)

When an article is entered, that has been added before (by any user in the db), the server should try to deduce the expiration date of the new entry (by adding the average expiration duration to the current date). The estimated date should then be sent to the client and serve as the default expiration date in the new-entry-form.

Another way to solve this would be through categorization (s. #3). For example a yoghurt won't last as long as a closed can of beans. However, since categorization can be quite arbitrary (again s. #3), I would suggest using deduction on base of the article (identified by the barcode) only.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant