Help us improve Huwise
📌 Context & problem statementCurrently, our visualization assets mix two very different types of showcases : Internal reuse (intended for Business Manager / BM). External reuse (intended for the General Public). The lack of a clear distinction between the two can cause confusion for the end user.🚀 Identified ActionTo address this, can it be possible to add a new asset category "External Reuse" ?Thanks @Mathieu Wolfarth for suggesting this product idea ! 💡
Avec la mise en place du sso, j’ai créé un mapping pour que toute personne de mon organisation qui se connecte soit rattachée au groupe consommateur de données, cela fonctionne mais dans la vue utilisateur l’appartenance au groupe n’est pas affichée;On ne peut donc pas facilement lister ensuite l’ensemble des utilisateurs du groupe consommateur de données sauf à aller sur chaque utilisateur pour ajouter l’info. Auto-translation 🪄With the implementation of SSO, I created a mapping so that anyone in my organization who logs in is attached to the data consumer group, this works but in the user view the group membership is not displayed; we cannot therefore easily list all the users in the data consumer group unless we go to each user to add the information.
-
Having a video block would allow the Studio page to have a hero video to describe the data or highlight any data story presented in the studio page.Auto-translation 🪄Avoir un bloc vidéo permettrait à la page Studio d'avoir une vidéo principale pour décrire les données ou mettre en évidence toute histoire de données présentée dans la page Studio.
We need the ability to control what is and isn’t visible on the Explore page such as the default map and fields on the data table (don’t delete, just hide so the fields can be referenced by pages/dashboards elsewhere). Having a ‘front and centre’ chart on this page would also be useful and save additional clicks.This is all functionality/flexibility we had and have now lost.This follows on from the conversation: Default Map View | Community
Dear ODS Team,Last week, we experienced an outage and were unable to access the data portal. We were not informed about what was happening.Could you please send us an email notification whenever the server is down and let us know how long the data portal will be inaccessible? Often, we are left in the dark about the situation and the nature of the problem.Thank you for your assistance.Best regards, BorisAuto-translation 🪄Chère équipe ODS, La semaine dernière, nous avons connu une panne et n'avons pas pu accéder au portail de données. Nous n'avons pas été informés de ce qui se passait. Pourriez-vous s'il vous plaît nous envoyer une notification par e-mail chaque fois que le serveur est en panne et nous faire savoir combien de temps le portail de données sera inaccessible ? Souvent, nous restons dans l'ignorance quant à la situation et à la nature du problème. Merci pour votre aide. Bien cordialement, Boris
Contexte : Lors de la publication d’un jeu de données, il arrive qu’un message d’erreur "Someone reached a quota limit when publishing the dataset" s’affiche. Ce blocage n'est pas lié à la taille de la source (limite technique), mais au quota global du domaine (lié à l'offre commerciale/licence).Besoin : Clarifier les limites (volume Vs quota) dans les erreurs du backoffice.
As a department that manages datasets from different entities and departments through one centralized platform, the Open Data Portal, it would be very helpful to have a workflow or status tracking feature for each dataset after submission.Currently, once entities upload their datasets, they do not have clear visibility on what happens next. We usually confirm the publication by email after the dataset is published, but entities would prefer to track this directly through the platform.The suggested feature is to show the dataset status at each stage, such as Submitted, Under Review, Requires Update, Approved, or Published.This will help entities understand where their dataset stands, reduce follow-up emails, and improve transparency in the publishing process.
The option to choose a dataset update date would be more helpful if the dataset creator could receive a notification on the selected date to update the dataset.Since our portal hosts data from different government entities, we currently need to follow up with them manually to remind them to update their datasets. Therefore, it would be useful if this process could be simplified or automated, either through an email reminder or a notification within the portal. This would help ensure that datasets are updated on time and reduce the need for manual follow-up.
We’re considering introducing a new URL data type.At this stage, the main use case identified is to make it easier to detect and manage outdated links.If this new type would be useful to you, please upvote this idea and share your use case. Your feedback will help us determine whether to move forward and how best to design it from a functional perspective.
Hello!When inviting users to register for the portal, the email that is sent contains a text that, in our case, is not “fit for purpose” as it doesn’t reflect the goal of our data portal.We think it would be a good feature to have the ability to edit this text from the backoffice in order to adapt it to each specific context.Thank you!
I think a useful feature to help us manage our back office would be for the datasets section to allow us to filter by the Update frequency.
A toggle in the security tab of a dataset. If activated, the dataset will be accessible via link for everyone (not just users of the portal), but isn’t listed in the dataset catalog. In that scenario, the “Default Security” toggle isn’t activated.The use case was coming up while integrating data of several departments of our city. In order to work low-threshold and to avoid that everybody has to get an account, but still the ability to check the data and/or dashboards before publishing them, this feature would really be great sometimes.Auto-translation 🪄Une bascule dans l'onglet de sécurité d'un ensemble de données. Si elle est activée, l'ensemble de données sera accessible via un lien pour tout le monde (pas seulement les utilisateurs du portail), mais ne sera pas répertorié dans le catalogue des ensembles de données. Dans ce scénario, la bascule « Sécurité par défaut » n'est pas activée. Le cas d'utilisation se présentait lors de l'intégration des données de plusieurs services de notre ville. Afin de travailler à bas seuil et d'éviter que tout le monde doive créer un compte, tout en ayant la possibilité de vérifier les données et/ou les tableaux de bord avant de les publier, cette fonctionnalité serait vraiment géniale parfois.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK