You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 9, 2024. It is now read-only.
The 'tags' were initially organized hierarchically under the 'areas', but that is no longer the case, as the 'tags' are now directly associated to the 'proposals'.
It's more flexible, but the problem with that it's exactly the one you expose, it can look messy if there's a lot.
Not sure about using the Eurovoc concepts as 'tags' were conceived as free text classifiers (although I can understand your motivation), but some type of autocomplete behaviour could be useful indeed.
@esebastian I am a bit allergic with the term "free text classifiers" :) sorry! Coming from the Semantic Web world, I believe that using controlled vocabularies over free text wherever it is applicable would improve the experience of using applications on the web (and in whatever in my belief).
And tags in different kind of Web documents is a field of glory for SW technologies.
The gains would be the multilinguality of Tag Models, uniqueness, standardization and possible exploitation of the hierarchical relationships (in case of using Eurovoc or similar).
Autocomplete would be the way to go with this issue. I can support you if you decide to go this direction and need any help.
But in any case I believe it would be better if tags where attached to "Area" ("Theme") model.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently all tags are available when creating or editing a proposal. It could be more practical and scalable if tags change per "Area" selection.
The text was updated successfully, but these errors were encountered: