-
Notifications
You must be signed in to change notification settings - Fork 11
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
Type of Tool - add to submission form and tool listing #76
Comments
hum - I don't even see Type of Tool any more? I do think we might want to add it in the future -- which would mean getting updated data for all submissions. |
It got dropped in the transition from json to data in github as the format changed to follow the submission form |
darn. The more I work with this, the more I think we do indeed need Type of Tool. I think we need to:
+1 to just add "other" along with with a field for them to explain (with limited character length, and not required) I looked around to try to see if EOWG had agreed on the types of tools to list for submitted to choose from... found #13 and not much else. Perhaps the types of tools list is in the old code somewhere? Maybe @SteveALee can easily point to it? @iadawn I set this for MVP+1 for now... although I think if feasible, would be good to at least get it in the submission form soon -- to save us having to go back to get that data from previous submitters. Though if EOWG had not already agreed on the types of tools to list, then no way we'll get that for MVP. |
In the survey
"The category "Type of Tool" will be extensible. That means that vendors can suggest new options not currently in the list. For example, someone could add tools with new type such as "Document Management System (DMS)", "Video Editor", or "Image Editor". These new options will need to be reviewed manually during the process for submitting new list entries."
For this to work a review and update process needs to be defined for new categories. Else it could grow continually.
For MVP maybe just add "other" value
The text was updated successfully, but these errors were encountered: