Recently active topics

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 sharing metadata across repositories, catalogs, aggregators, and Research Data Management platforms, where many resources are created collaboratively by more than one individual or organization.At present, Marketplace appears to support only a single Creator value. This limits the ability to represent co-authored publications, jointly produced datasets, collaborative projects, and other multi-contributor resources accurately. In practice, a resource may have more than one creator, rather than exactly one creator. Restricting the field to a single value results in incomplete metadata and reduces interoperability with systems that expect creator to be repeatable.This approach is not consistent with common metadata practice. For example, the

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 organizations is increasingly standard practice. These identifiers play an important role in improving metadata quality, enabling unambiguous identification of entities, and supporting interoperability across systems.PID support also complements the FAIR Guiding Principles, particularly by strengthening:Findability Interoperability ReusabilityAt present, the ability to associate structured persistent identifiers with people and organizations would provide significant value in cases such as:identifying creators, contributors, and contact persons using ORCID identifying institutions, affiliations, publishers, and other organizations using ROR improving metadata exchange with external systems and repositories supporting more precise and machine-act

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 responsible for making the resource, while Publisher identifies the entity responsible for making it available. These are often different.Is there a way to override this behavior?If not, could you please provide a separate Publisher field and allow Publisher to be managed independently of Creator in metadata mappings.

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 single date for selection -- could you reinstate the ability for a range to be selected?   

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 information Quick start: our Power BI and Tableau Academy paths guide you step by step, from setting up to managing the connector. Activation on your portal: the connectors are not included by default. To enable them, contact your Customer Success Manager or your Account Manager.

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 real (anonymized) examples from your portals. 🔒1. Identify who logs inSSO (OpenID Connect or SAML 2.0): your users log in with their company account. No accounts to create by hand, and removing someone from the directory removes their access. Several SSO providers on one portal: one group brought 7 of its entities together around a shared catalog, each with its own identity provider. Group mapping: your directory stays the source of truth. An international organization receives a staff category through SSO, and each user automatically joins the right group with the right permissions. Conditional access rules: based on a user’s attributes (company ID, email domain…), the portal approves the sign-up, rejects it, or sends it for manual review.2.

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 assistants and I wanted to share my experience. I hope it is useful.If you don’t have the experience in web design and software development that the wizards at Huwise have, the code editor can be baffling and frightening. It was for me, and even though I have developed a bit of expertise I am a long way from an expert. Claude Code (also cursor, codex etc) can help. I won’t go into the specifics of using an AI coding agent here, but will describe the steps I took to use Claude to create the page. The skills (guidance docs for Claude) I built are all here - use and adapt as you wish.Install Claude code and buy a subscription (plenty of docs online for this). Use the Opus model. Set up the local dev environment. Give Claude this url and ask it t

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 the knowledge experienced colleagues have. A finance analyst knows a legacy system runs two days behind the data warehouse. An HR director knows a survey with a 90% response rate is more reliable than one with 10%. An agent acts on the data without this knowledge, and small misreadings add up quickly when it works autonomously. A semantic layer standardizes definitions. Interpreting a metric correctly also depends on who asks, which system produced it, how fresh the data is, and which policies apply. That extra information is what the ebook calls context. Context covers many dimensions: time, location, relationships to other data, quality, purpose, permissions, business definitions, and provenance. Context changes all the time. A customer lea

Version françaiseAprès les îlots de fraîcheur de Clermont-Ferrand, direction l’Australie 🇦🇺 avec une nouvelle page publiée par la Ville de Casey sur son portail Open Data : Cartographie de la chaleur à Casey👇🔥 Le principe : un portail de science citoyenne pour mieux comprendre la chaleur sur le territoire, à partir de capteurs de température et d’humidité installés un peu partout dans la ville.🗺️ Ce qu’on peut y faire :Visualiser les capteurs sur une carte, colorés selon leur moyenne sur la période choisie (du bleu au rouge), et filtrer par plage de valeurs (par exemple, tous les capteurs au-dessus de 40 °C). Cliquer sur un capteur pour voir sa dernière mesure, son évolution dans le temps et surtout son contexte : couvert arboré, surfaces imperméables, ombre, proximité de l’eau, exposition au vent… Bref, tout ce qui aide à expliquer une mesure. Comparer plusieurs capteurs sur un même graphique. Accéder aux données brutes, déjà filtrées selon la sélection.🔬 Le petit plus : un ongl

Mandatory fields are now checked automatically to ensure key metadata is always filled in. If any is missing, publication is automatically blocked. ✅         Why make your metadata mandatory? 💡Easier discovery: more complete metadata makes data easier to understand, find, and use — for both users and AI agents. Time saved: completeness of essential metadata is checked automatically at publication, so you can delegate with confidence, without manual review. Guided experience: completion indicators let you track progress and spot which metadata — required or recommended — is still missing.Practical informationUnfilled mandatory metadata: on your existing data assets, it automatically switches to “recommended”. This keeps your upcoming publications and automated processes from being blocked. To get the list of affected metadata, contact your Customer Success Manager or the support team. Metadata templates covered: you can make metadata mandatory on all your templates: standard, custom an