Ongoing discussions

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.