Make metadata mandatory to publish your data assets 🚀
Ask questions, get answers and engage with your peers
We would like to request support for repeatable Creator fields in Marketplace.In most metadata application profiles, the Creator element is repeatable so that resources with multiple creators can be described accurately. This is standard practice for
We would like to request that support for Persistent Identifiers (PIDs) be added to the Marketplace product roadmap.In contemporary Research Data Management environments, support for identifiers such as ORCID iDs for individuals and ROR IDs for organ
In Marketplace, the Asset Template Creator value appears to auto-populate Publisher in exported Dublin Core and DCAT-AP metadata, with no ability to override. This is not aligned with DCMI / DCAT-AP semantics.Creator identifies the entity primarily r
We’re currently trying to navigate the new interface in the back office. There is a filter we were using on a daily basis which we cannot see/find.We used to be able to filter for Last modified and date range:The new experience provides only a singl
With our Power BI and Tableau connectors, your dashboards join your Huwise catalog and reach more users. ✨ BenefitsDashboards visible in search Smooth exploration, without switching tools Access rights from your BI tools respectedPractical informatio
I would like to request ODS supports and includes an “exact” search option. I would have thought the option of searching for title:”parking” would bring back options with the term “parking” in the title and not parks (for example). I have commented
Bonjour,Savez-vous quand vous prévoyez de faire évoluer l’API SIRENE V3 afin qu’elle propose les codes NAF 2025, en vue de l’obligation prévue pour janvier 2027 ?
Hi everyone,More and more of you use your Huwise portal to share data with a selected audience: partners, subsidiaries, logged-in staff, contractors. @Lauralee reviewed what the platform lets you do today to manage these accesses in detail, with rea
I realise this may be a bit niche for some people, especially if you haven’t use Claude Code before, but I have developed an effective workflow for building pages on the portal without having to directly code in HTML \ CSS \ Angular with AI coding as
Hi Community,We just published an ebook on AI and data context. It explains why AI agents need to know how data is actually used, and how a data product marketplace can give them that information. Here are the main points. Key takeawaysAgents lack th
I think I remember that in the legacy experience, in the Table view, if you mouse hovered over the field (column) heading, the field’s Description metadata would appear. This was and would be quite useful for fields which are defined in complex or am
Hi everyone! 👋A recurring question since the migration: in the old experience, some of you could split/ventilate a chart's values by a secondary field (e.g., a bar chart broken down by category). Here's where that stands in the new experience.📊 Today
Reliable data is essential for addressing today’s complex global challenges. The United Nations has launched the UN system data commons : a platform developed under the UN80 initiative to bring together publicly available data and statistics from acr
Hi everyone! 👋We've had a lot of great questions since the new Explorer rolled out. Few of them come up several times, so here's a quick index to help you find the right answer fast. 🔍 Filters & sortingWondering where the active filters summary w
Hello,I'd like to update the metadata for the assets using the Automation API. It seems that not all metadata fields can be modified directly via the API.Where can I find these restrictions?Using `/automation/v1.0/metadata/templates/default/fields`,
Huwise embarque aujourd'hui plusieurs briques d'intelligence artificielle, chacune pensée pour un usage précis. Les connaître vous permettra de choisir le bon outil au bon moment. Tour d'horizon.1. AI Insights : transformez une question en graphiqueC
For a spatial dataset, I can add an additional geographic projection e.g. 27700 for BNG in the backoffice. But this doesn’t appear in the export tab as an option, and my testing shows that the export is still in WGS84 - the default. Am I missing some
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.