Helpful tags used by Esri

[#1]

There are many teams at Esri who specialize in areas which span multiple parts of the community. These teams may use tags to identify content which corresponds with these topics. Below, we have listed examples of some cross-Esri tags which may be added to your posts. If you are submitting something which aligns with some of these topics, please feel free to add these tags yourself!

Accessibility

Accessibility refers to websites, tools, and technologies that are designed and developed so that people with disabilities can use them. Accessibility encompasses all disabilities that affect access to technology (e.g. auditory, visual, physical, speech, cognitive, neurological), but also benefits people who are temporarily or situationally limited (e.g. broken arm, lost glasses, loud environment), as well as our aging population of technology users.

The use of the tag “Accessibility” can include, but is not limited to, posts related to: the use of keyboard navigation; using assistive technology such as screen readers, voice control or screen magnification; implementation of alt text on images; color contrast and color patterns; and clarity of language and text. Accessibility topics often contain references to known standards and guidelines (e.g. Web Content Accessibility Guidelines [WCAG], section 508), as well as requests for information about accessibility feature documentation (e.g. Accessibility Conformance Report [ACR] or Voluntary Product Accessibility Report [VPAT]).

Interoperability

Interoperability has two dimensions. It means working well with external tools and systems, and working well across the ArcGIS product suite. On the external dimension, interoperability describes how ArcGIS works with third-party systems (e.g. Autodesk BIM 360), non-ArcGIS data sources (e.g. Knowledge Graph/Neo4J), and other data formats (e.g. KML, GeoJSON). On the internal dimensions, it describes how certain functionality in one product impacts the user experience or expectations of consistent functionality across other ArcGIS products (e.g. support for OGC standards, military symbology, branch versioning, data feature editing, ArcPy). 

In the context of ArcGIS Ideas, the “Interoperability” tag should be used to refer to any ideas related to the definition above, including:

• Data interoperability: Requests for native support for datastore types (e.g. Snowflake, Key-Value Pair storage) and data formats not currently supported across the platform to read, edit, or publish.  Functional issues and data connectors related to the ArcGIS Data Interoperability extension should be posted in the ArcGIS Pro Idea Exchange, using the label "Extension: Data Interoperability".
• Standards: ideas for support of standard data formats, services, catalogs, metadata or protocols related to international standards endorsed by ISO, OGC, W3C, other national standards bodies (e.g. national metadata profiles), or industry/sector specific authorities (e.g. IHO for maritime, NENA for public safety)
• Third-party Add-Ins or Integrations: any ideas related to NEW desired integrations with third-party apps or enterprise systems. Examples of existing add-ins would be ArcGIS for PowerBI, ArcGIS for Office, and ArcGIS for SharePoint.  These products have their own Idea Exchanges so if you have an idea about them, ensure that you post in the appropriate Idea Exchange. This is NOT meant to include issues related to cloud implementation patterns (Enterprise in Azure/AWS/etc) which can be discussed in the following question board instead: ArcGIS Enterprise in the cloud.
• Integration Enabling Capabilities: any ideas that would improve or enable desired ArcGIS integration patterns such as Webhooks (event types), SOI/SOEs, or Developer SDKS to use by other products/solutions.

Productivity

Productivity describes the following:

• A work process that is made unnecessarily difficult or time consuming by the application. Said another way, the process could be simplified in order to take less time.
• Scenarios where tools and information that a user needs to do their work are not readily available.
• Moments when a user is made to jump back and forth between different areas of the application.

Security

Software security means functionality, controls, and processes that in some way impact or facilitate aspects of an information system’s Confidentiality, Integrity and Availability (CIA). This topic encompasses Identity and Access Management, Encryption, Security and Risk Management, Security Architecture and Engineering, Communications and Network Security, Security Assessments and Testing, Dev-Sec Operations and Secure Software Development practices.

This tag should be used to identify ideas/questions that ask about configuration options or practices used to enforce CIA practices, in this context, defined as:

• Confidentiality: Only authorized users and processes should be able to access or modify data
• Integrity: Data should be maintained in a correct state and nobody should be able to improperly modify it, either accidentally or maliciously
• Availability: Authorized users should be able to access data whenever they need to do so

The tag “Security” should NOT be used for users who wish to discuss security vulnerabilities. If you wish to discuss security vulnerabilities, please do so by visiting the ArcGIS Trust Center.

Usability

Usability is a quality attribute that assesses how easy and pleasant user interfaces are to use and is defined by 5 quality components:

• Learnability: How easy is it for users to accomplish basic tasks the first time they encounter the design?
• Efficiency: Once users have learned the design, how quickly can they perform tasks? If efficiency is the only usability aspect of an idea, then tag the idea as “Productivity”
• Memorability: When users return to the design after a period of not using it, how easily can they reestablish proficiency?
• Errors: How many errors do users make, how severe are these errors, and how easily can they recover from the errors?
• Satisfaction: How pleasant is it to use the design?