idea Required Metadata When Publishing in ArcGIS Enterprise Ideas

Required Metadata When Publishing

JamesTchorzynski1 — Wed, 12 Apr 2023 15:54:56 GMT

When publishing or registering services to ESRI from ArcGIS Pro or from inside ArcGIS Enterprise I would like to see options for admins to incorporate required metadata from the metadata standard selected. I would also like that these options be controllable for different item types (apps, maps, features, etc.). I would envision the metadata interface coming right after mandatory metadata (reference Current Mandatory Metadata attachment).

By default, the required are title and tags to publish/register content. I presume this is just inherited as a line of thinking from ArcGIS Online. However, with on premise systems we need to be able to tailor individual documentation requirements to our business we deployed ArcGIS Enterprise to support.

For example, if an organization needed to ensure all data was properly classified for security, they need to be able to require the security data be filled in to publish. This should be something an admin can turn on and mandate users is populated (reference Security Classification Metadata attachment). The same may hold true for other metadata such as points of contact, citations, access constraints, additional keywords, language, etc.

In doing so it would be much easier to keep a cleaner house, allow for audits, and apply cleaner governance to our systems that match our business needs.

Re: Required Metadata When Publishing

AmaiaMartinez — Fri, 01 Dec 2023 07:51:09 GMT

Totally agree on this idea! THIS IS A MUST

Come on Esri, Metadata in GIS plays a crucial role in data discovery and evaluation as it is a vital component of geospatial data.

We need this feature in order to be able to configure some prefilled-metadata and custom policies regarding templates, such as required INSPIRE fields for an Organization, etc. It would be a really useful tool for the administrators on QA tasks.

Please, take into account!

Re: Required Metadata When Publishing

JamesTchorzynski1 — Fri, 01 Dec 2023 13:09:55 GMT

@AmaiaMartinez, great points! Consider providing kudos to this one too: Customizable Use of Metadata in Filters - Esri Community

Re: Required Metadata When Publishing

JennieCatalano1 — Fri, 02 Aug 2024 21:25:27 GMT

Great point. It would also be nice if AGOL and Enterprise Portal administrators could set the default metadata and security categorization requirements based on the publisher's selected audience (Everyone, Organization, Group). However, in case a publisher needs to quickly publish something, say for emergency response, a GIS Administrator can bypass the metadata requirements and share the item for them (temporarily).

Re: Required Metadata When Publishing

DiegoMeira — Fri, 21 Feb 2025 14:54:04 GMT

This feature is essential.

It would significantly improve metadata management in ArcGIS Enterprise.

In a federal department, administrators need the ability to enforce specific metadata fields to meet safety and security requirements. This would help ensure that data is properly classified and documented, making audits easier, improve governance, and keeping things more organized.

Integrating this into the publishing workflow would reduce the burden on users while maintaining data integrity. Having this level of control is critical for organizations that rely on structured and secure geospatial data.

Currently, we work around this limitation with scripting and rely on users to classify new content correctly, but this is difficult to maintain. A built-in solution, similar to those found in Microsoft and other big-tech applications, would be far more effective.