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

Field in DB that toolID is "verified" #279

Closed
joncison opened this issue Nov 4, 2017 · 4 comments
Closed

Field in DB that toolID is "verified" #279

joncison opened this issue Nov 4, 2017 · 4 comments
Assignees
Labels
critical priority Our top priorities, including most of the reported bugs. housekeeping Concerns routine housekeeping / maintenance functions.

Comments

@joncison
Copy link
Member

joncison commented Nov 4, 2017

This is definitely required, and should be set to "true" for all things from the spreadsheet from hell, false by default. What's the status of this @hansioan - I imagine something is already there?

@joncison joncison added critical priority Our top priorities, including most of the reported bugs. housekeeping Concerns routine housekeeping / maintenance functions. labels Nov 4, 2017
@hansioan
Copy link
Member

@joncison We have the field, will update it to mark the spreadsheet from hell tools as verified

@joncison
Copy link
Member Author

very good, once done pls. close this

@hansioan
Copy link
Member

re-open and update the field with the verified tools from the spreadsheet from hell

@joncison
Copy link
Member Author

joncison commented Sep 5, 2018

Field in DB is added, IDs that were verified in spreadsheet from hell have been set to "true" (1), and we have a new list of IDs to verify since that check (#357)

@joncison joncison closed this as completed Sep 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
critical priority Our top priorities, including most of the reported bugs. housekeeping Concerns routine housekeeping / maintenance functions.
Projects
None yet
Development

No branches or pull requests

2 participants