IHubContent

The preferred identifier to use for Hub URLs. This will be either the slug, hubId, or item id.

Whether the content is downloadable in the Hub app

The underlying portal item referenced by this content

Content visibility and access control, including groups NOTE: this needs to be reconciled with Hub permission system

Date the content was published (formal metadata), defaults to the date the content was created

Optional links to show in the Hub application for this content

links to additional resources specified in the formal item metadata

Parsed item categories (see parseItemCategories)

The the family of related types that this content belongs to.

Configure which Hub application actions (i.e. create web map) are available for this content

The content's ID for use with the Hub API For most content this will be the item's id For layers this will be <itemId>_<layerId> This will be undefined for private items and in enterprise because only public online items are included in the Hub API

Whether or not the layer or table is actually a proxied CSV

Information about the layer referenced by this content (geometryType, fields, etc)

URL of the Portal API endpoint for the resource

URL of the Portal API data endpoint for the resource

URL of the resource's page in the Portal Home application

Description of the source of the published date

Info to display about the content's publisher. Follows this fallback pattern:

1. Formal Item Metadata > Resource > Citation > Contact
2. Formal Item Metadata > Resource > Contact
3. Formal Item Metadata > Contact
4. Item’s Owner and Org Name
5. Undefined (Item Owner / Org are private and we can't access additional info)

Slug that can be used to lookup an entity by something other than it's id

The content's structured license info

Frequency at which the content is updated

definition for content that refers to a client-side layer view

boundary will default to the item extent but can be overwritten by enrichments from the Hub API (inline) or fetched from a location such as /resources/boundary.json

The portal item's data (if any)

Any errors encountered when fetching enrichments see https://github.com/ArcGIS/hub-indexer/blob/master/docs/errors.md#response-formatting-for-errors

The ids of any groups that the item belongs to

Detailed information about the service's layers (geometryType, fields, etc) for related layers in the service

The content's formal metadata

The owner's organization (portal) details (id, name, extent, etc)

The user that owns the item

The count of records for the layer referenced by this content

Information about the service referenced by this content (currentVersion, capabilities, maxRecordCount etc)

If the server's services directory is disabled. See https://enterprise.arcgis.com/en/server/latest/administer/linux/disabling-the-services-directory.htm

Data model for content