EGMP key terms

A geodatabase grouping for compatible feature classes that can support relevant shared spatial behavior under actual dataset requirements.

A constraint defining an allowed set of attribute values in its supported scope, distinct from arbitrary free-text labeling or a database user role.

A supported classification of rows in a feature class or table that can apply relevant defaults/domains without creating a separate class for every category.

A supported correspondence between input and output fields during loading or transformation, which still requires checking types, units and intended meaning.

A supported isolated editing version created from default under the branch model’s hierarchy and lock rules, not an arbitrary independent database copy.

A version comparison operation under configured conflict rules, distinct from automatically choosing the correct business value or completing every post operation.

The supported application of relevant reconciled edits to the target version under actual authority, distinct from merely saving a local screen or editing metadata.

A view of data history supported by records actually retained under the applicable temporal/versioning model, not a promise of every past state forever.

A traditional-versioning state still needed by relevant versions or transactions, which cannot simply be discarded because a cleanup was requested.

Information describing relevant data distributions for query planning, which can become stale and differs from an index or actual performance measurement.

An access structure supporting relevant spatial predicates under the actual DBMS/type configuration, not a universal cure for every slow map or query.

A supported large data transfer with justified mapping, privileges, validation and recovery arrangements, rather than permission to disable required constraints indiscriminately.

The designated supported ArcGIS GIS Server role supplying relevant hosted capabilities for a portal, distinct from every federated server site.

A supported data source referenced by a service at its registered location, distinct from an automatically managed hosted copy or every portal item.

A particular running installation or execution instance of a product component, distinct from the number of product-family names in an architecture list.

A stated quality or operating constraint such as response time, availability or security, whose satisfaction requires actual design and validation evidence.

The usable resource capacity remaining under a specified failure or maintenance condition, which can be less than the total installed rating.

The relevant resource work per request under a representative workload model, requiring explicit units and conditions when translating throughput into capacity.

The actual configuration, data, dependencies and time consistency covered by a recovery arrangement, not every external source merely referenced by the system.

A resource or condition common to nominally redundant components, which can defeat the intended resilience when the modeled event affects it.

A supported portal/server integration affecting relevant security and administration, distinct from assuming every service has the same underlying data permissions.

The actual item/service access arising from relevant settings, identity and roles, which an item title or successful login does not establish alone.

The supported sequence, compatibility and downtime conditions for an actual release/platform change, not a generic rolling-update recipe from another product.

Comparison of relevant logs, timestamps, paths and measured behavior to investigate a condition without treating one symptom as conclusive root-cause proof.