The task field of the entries currently has this description:
An array of strings, describing the basic tasks that are supported by the project.
Common examples of tasks are view, load, import, export, validate, or optimize.
This is somewhat rooted in the original structure of the projects list in the glTF README, where the projects had been in sections like "Viewers", "Importers", "Loaders", "Exporters" etc.
In general, it is sometimes hard to figure out a sensible value for this field. We might have to add some clarification here: Most of the current entries try to use one of the examples mentioned above, and I think that this makes sense to some extent. People can easily search for "view" when they just want a viewer.
We could, however, consider to either allow/foster more differentiation here, or add something like a "tags" or "keywords" field, which could basically be free-text, and be taken into account when typing something into the main search field. The description could then be:
Keywords that cause the project to be found during a search operation.
And yes, we will have to prevent people from adding a 10-million-entry list like "a", "aa", "ab", ... "zzz"... at some point - the keywords should be "reasonable"....)
Are there any thoughts or ideas on that?
The
taskfield of the entries currently has this description:This is somewhat rooted in the original structure of the projects list in the glTF README, where the projects had been in sections like "Viewers", "Importers", "Loaders", "Exporters" etc.
In general, it is sometimes hard to figure out a sensible value for this field. We might have to add some clarification here: Most of the current entries try to use one of the examples mentioned above, and I think that this makes sense to some extent. People can easily search for "view" when they just want a viewer.
We could, however, consider to either allow/foster more differentiation here, or add something like a
"tags"or"keywords"field, which could basically be free-text, and be taken into account when typing something into the main search field. The description could then be:And yes, we will have to prevent people from adding a 10-million-entry list like
"a", "aa", "ab", ... "zzz"...at some point - the keywords should be "reasonable"....)Are there any thoughts or ideas on that?