Learn & share

Hey everyone! 👋The latest Huwise Product Newsletter (Summer Edition) is out, and it’s packed with updates designed to turn our data into a true source of knowledge. As Opendatasoft transitions fully into its new identity as Huwise, the focus is entirely on democratizing data access for everyone—not just data experts.Here’s a quick wrap-up of what’s landing:🤖 Meet Huwy: a conversational AI agent that lets anyone explore datasets and build visualizations using everyday language.📋 Huwise forms: streamlined, fast data collection tools built to ensure data is clean, compliant, and ready for AI applications the moment it's submitted.🔒 Enterprise-grade security: the marketplace solution is now officially ISO 27001 certified, meaning our data sharing remains as secure as it is accessible.🤝 True self-service: improved cataloging and data product discovery tools to help business teams safely find, reuse, and extract value from data without IT bottlenecks.What feature are you most excited to

We are at a monumental turning point. As generative and agentic AI flood the market, organizations face a critical choice: allow technology to cause information chaos, or harness it intentionally to amplify collective intelligence.The freshly co-created Data Voices 2026 Manifesto gathers insights from nearly 100 Data & AI leaders across international industries to establish a definitive roadmap for the next four years.Here is a look at the 6 strategic predictions that will define the AI-first enterprise by 2030, along with the immediate actions you need to take today. 📋 The 6 strategic predictions for 2030 # Prediction The core insight 1 Data Leaders as Business Strategists The CDO/CTO will evolve from a technical executioner into the CEO’s core strategic partner, balancing technical foundation with real ROI. 2 Effortless Data Democratization Data-driven culture will become organizational DNA. Every employee will independently leverage data, backed by intelligent age

You notice that your published dataset contains more records than your source file. For example, your file has 22,000 rows, but the dataset shows 24,000+. Clearing the cache and republishing does not fix the issue.Root causeThis is a known behaviour with the XLSX extractor on FTP sources.When a new file is deposited on the FTP under a different name than the previous one, the platform does not recognise it as a replacement; it treats it as an additional file. As a result, records from both the old and new files accumulate in the dataset instead of the old ones being replaced.The XLSX extractor does not detect deleted files in an FTP folder. Unlike CSV, it has no mechanism to automatically flush previous data when a new file with a different name is added.Solutions✅ Recommended — Keep the same filenameThe cleanest fix is to always use the same filename when replacing a file on the FTP. When the platform detects an update to a known file (same name), it correctly flushes the old data bef

Vous vous posez une question simple (et très utile) :“Quels sont les utilisateurs qui consomment le plus mon API, et sur quelle période ?”Que ce soit pour identifier vos power users, repérer un pic d’activité, ou préparer une action de communication ciblée, avoir un classement des utilisateurs les plus actifs est un excellent point de départ. La solution : sans export, sans requête complexeBonne nouvelle : votre portail enregistre déjà tout ce qu’il vous faut.Le dataset ods-api-monitoring trace chaque appel API effectué sur votre portail en temps réel. En quelques paramètres, vous pouvez extraire un top utilisateurs par volume d’appels sur la période de votre choix. ✅ La requête (Top 50 sur 12 mois)GET {{https://{votre-portail}}}/api/v2/monitoring/datasets/ods-api-monitoring/records ?select=user_id, count(*) as nb_api_calls &where=timestamp >= now(years=-1) &group_by=user_id &order_by=nb_api_calls desc &limit=50Cette requête retourne le top 50 des utilisateurs ayant

 ​@patrick.smith  rolled out a series of fresh articles and essential updates to help you navigate, enrich, and optimize your data strategy like a pro. Whether you are looking to make your datasets more discoverable or streamline how you connect external platforms, we’ve got you covered.Here is a quick look at what’s new: Master Your Metadata 🏷️ Getting Started with Metadata: Learn why filling out metadata is the key to ensuring your datasets are easily found, understood, and reused by your community. Navigating Basic & Standard Metadata: Discover how to configure default and custom "Basic" templates, use inherited metadata fields, and accurately manage details like geographic coverage, licensing, and update frequencies. Zero-Copy Data Sharing (Virtualization) ⚡ Explore how to make massive resources searchable and filterable in Huwise without copying the underlying records. Keep your data securely in your source system while avoiding duplication. Get step-by-step

If you need to accurately calculate the gap between two key moments, the DateDiff function in the Expression processor is your best ally. 🔍 What is DateDiff?It’s a date and time function that counts the number of units (days, hours, minutes, etc.) between two datetime expressions. 🛠️ How do you implement it?In your Expression processor, the syntax usually follows this logic:DateDiff(unit, start_date, end_date)Unit: choose what you want to count ("day", "hour", "minute", etc.). Start_date & End_date: the two datetime fields you want to compare. 📖 Concrete exampleImagine you want to calculate the age of an alert in days:DateDiff("day", Alert_Created_Date, Current_Timestamp) 🌟 Why is it useful?Automation: no more manual calculations or complex scripts. Accuracy: ideal for monitoring your SLAs or account velocity. Reporting: lets you build powerful KPIs directly at the data source.And you — what’s your favourite function in the Expression processor for saving time? Share your tips

Hello Community!We’ve seen so many of you making the leap to our New Experience, and frankly, we’re a little jealous of how good some of your setups are looking.Transitioning to a new interface is more than just a fresh look—it’s about building a more powerful data portal for your teams and users. Now, we want to see how you’ve made it your own.The Challenge 🏆: We’re calling on all Clients and CSMs to drop a screenshot of your newly designed portal in the comments below. Whether you’ve relooked your home page, rebuilt your catalog, or just simply turned it on—we want to see it!How to participate :Snap a shot: take a screenshot of your favorite view in the New Experience. Tell us why: share one "pro-tip" or favorite feature about your new experience. Tag your partner: clients, tag your CSM to give them a shout-out for the help. CSMs, tag your star clients to show off their hard work!Help your peers visualize what’s possible in the new experience.Note: Please ensure you blur out any sen

Hello everyone,The Huwise experience is evolving!The Huwise Academy now offers a learning path to guide you step by step through activating the new experience. 🎯 Why follow this path?The new experience isn’t just a visual update—it’s a redesign of how your users interact with the platform. This path gives you the keys to:Master the new features and navigate the interface with ease. Optimize your datasets to align your engagement strategies with Huwise’s new technical capabilities. 📚 What’s included:Interface exploration: understand the structural changes. Optimal setup: configure the platform for a smooth activation. Best practices: explore platforms that have already adopted the new experience.Bonus: The path is designed to be quick, actionable, and immediately applicable. 🔗 Ready to level up?👉 Access the Huwise Academy pathQuestions about the impact of this activation? Let’s discuss in the comments! 👇!-->

 At Huwise, your satisfaction and the progress of your projects are our top priorities. To ensure fast response times and high-quality follow-up, we have structured our communication channels.This article helps you identify the right point of contact so each request is handled by the relevant expert as quickly as possible. 🛠 1. "Self-service": your first stepBefore reaching out to us, remember :The User Guide which brings together all our technical and functional documentation. The Academy which centralizes all tutorials and courses on how to use Huwise products and services. The Community which shares use cases from Huwise users around the world. Feel free to post your questions and your product ideas. 📨 2. Who to contact depending on your needsIf you did not find what you were looking for in the resources above, here is who to contact depending on your request.Request type Primary contact Preferred channel Operational and technical Support team support@huwise.com or via th

I’ve been investigating options for accessing the data on our portal using AI assistants, mainly Claude code. I previously posted my experience of a REST to MCP adapter, which works, but is a bit clunky and not very token efficient. I have recently experimented with a new library called mcp2cli which enables the coding agent to use CLI commands to query data on our portal.MCP2CLI can create a skill which introspects the swagger.json  - which is published under the portal’s API tab, to understand the explore API of the portal. This enables the coding agent to discover datasets, understand their structure and create SQL queries to return filtered and aggregated data. The skill is an alternative approach to MCP servers that is more token efficient due to progressive disclosure and the use of a command line interface to query the data. I iterated over creation of the skill several times to improve it.My limited testing of the skill I created indicates that it is quite accurate and token -

Hey community! 🚀Ready for a new challenge? 🏆This round is all about Forms.We’d love to hear how you’re using the Forms feature - the context, how you set it up, what data you collected, and, most importantly, what it changed for you.Did it help you…✨ save time or streamline a workflow?✨ build a new asset or surface insights?✨ collaborate better across teams or with users?✨ or something else entirely?Share your use case in the thread, check out others’ ideas, and don’t forget to react to your favorites! 👍💬The submission with the most likes will earn the new Monthly Challenge badge 🎖️Let the inspiration and the competition begin! 🔥Monthly challenge badge 

Discover our Sources of inspiration page, a collection of real-world use cases showing how our users leverage, share, and create value from their data with Huwise.From public organizations to private companies, these concrete examples highlight:How data is transformed into impactful use cases How our platform supports data sharing and visualization How real projects inspire new ideas and innovationWhether you're starting a new project or looking to unlock more value from your data, these use cases are here to spark ideas, guide decisions, and demonstrate what’s possible. Explore the Sources of inspiration and get inspired by real success stories. Don’t hesitate to share your own use case in Community—your project could inspire the next one!

Hi allI’ve been using Claude Code quite a lot for developing software and doing analysis. It’s an agentic AI coding assistant in the CLI if you haven’t come across it. Anthropic (the parent company) developed a protocol called MCP to help the AI use external resources like APIs.Someone has developed a tool to take openapi or swagger API specifications and turn it into MCP tools. What this means is that you can ask Claude Code, in natural language, questions about your data, and it will translate this, quite well into code to send a request to the API and return data. HuWise have done something similar on the portal in their “Explore data with AI” feature, but this is a bit more powerful for deeper analysis - but requires some setup and a Claude account and Claude Code.I simply cloned the repo and asked Claude to create MCP tools from the swagger json for my portal, and it did the rest.Here is my cloned repo, with the ods_server.py script providing the mcp tools for my portal. Full desc

Hello, I can see that the region ID - Name used for Japan in OpenDataSoft follows the FIPS standard. I also see in different sources that FIPS is no more used since 2008. Do we know why OpenDataSoft is still using this norm ? is there a way they could update to use one of the used norms in the whole world now ( JIS X 0401 or ISO )

🎯 We’re happy to announce the launch of the Huwise status page, a tool designed to efficiently share information about the status of our services.From now on, the fastest and most up-to-date way to get this information is to check the Huwise status page directly!(Of course, if your incident isn’t listed, feel free to contact us!) 💡  Visibility and transparency 🔍 Ease and relevance: You can check the status of Huwise services at any time—and even view it region by region.📢 Effective communication: Automatic notifications (email, webhooks, etc.) keep you instantly informed of any incident.⏱️ Real-time information: The page is connected to our monitoring tools, allowing updates to be automated.📚 Incident history: Each event is archived to support better analysis and stronger prevention of future incidents. 🌍  A page tailored to your region Each user can view the service status according to their hosting region and subscribe to alerts for that region.Cloud region Identifier Cloud

Are there plans to add more mapping capability for Studio Maps - for example clusters, dots and shapes and heat maps - same functionality that is shown in Map Builder? 

Hello dear community,I’m having an issue with sorting in the filter. I created a dropdown filter with the names of care homes. The problem is that the alphabetical order doesn’t prioritize uppercase and lowercase letters correctly. I have care homes named "dandelion" and "irides" which are lowercase and appear at the very end of the filter. Is there a way to work around this?                <div class="shared-width-ods-selects">                    <div ods-facet-results="reglist"                         ods-facet-results-facet-name="name"                         ods-facet-results-context="myctx0"                         ods-facet-results-sort="alphanum">                        <ods-select ng-init="myctx0.parameters['refine.name'] = []"                                    options="reglist"                                    selected-values="myctx0.parameters['refine.name']"                                    multiple="false"                                    label-modifie

Is it possible to remove the label indicating the cluster count ? - or at least the option to style it  - so the label has the same colour as the icon behind it?

Dear Support Team,I am currently trying to display data in a chart, and I have encountered an issue. The chart is displaying the years along the X-axis, but some years are not being shown, likely due to space constraints.Is there a way to force the diagram to display the missing years, such as 2017, 2019, and so on?Thank you for your assistance. I look forward to your guidance on how to resolve this issue.Best regards,Boris

Hello Community,It seems many of you are looking to create content that helps your users get more value from the portal.We’d love to know how you currently support your users, and how we can make it easier for you.Quick poll, takes 2 min tops. Mind giving it a go?👉 Go to the poll.Thanks a ton! 

I’ve been trying to use the Geofilter.polygon to refine the results in a dataset per this documentation:https://userguide.opendatasoft.com/en/articles/2257346#:~:text=geofilter.polygon,%2C2.386968)However it always looks like it does a text search in the records.  Is there a setting I need to activate at the dataset level to accept geofilter options? 

I’ve found this article very interesting :  https://open.substack.com/pub/benn/p/disband-the-analytics-team

Hello,  I’m student, and I need to use OpenDataSoft for French municipalities per year, I want to know if it’s possible to get an API key to get this kind of data without limitations please. This is the data that I need between 2015 and 2024. https://public.opendatasoft.com/explore/embed/dataset/georef-france-commune-millesime/table/?disjunctive.reg_name&disjunctive.dep_name&disjunctive.arrdep_name&disjunctive.ze2020_name&disjunctive.epci_name&disjunctive.ept_name&disjunctive.com_name&disjunctive.ze2010_name&disjunctive.com_is_mountain_area&disjunctive.bv2022_name&sort=com_name