What is the asset inventory?
The Asset Inventory contains information about every asset your site, providing a global view of all the data on your site. This tool has an entry for every dataset, view, story, etc. including published and unpublished datasets and views. It differs from the public catalog on your site, because it contains private and public datasets.
How do I access the asset inventory?
The asset inventory can be accessed through the administrative panel of your site.
The Asset Inventory is a private dataset, so it is only available to roles with permissions to view private datasets on your site.
You can view the Asset Inventory as a dataset via the button "View as a Dataset" in the Asset Inventory. You can also find it by searching for "Asset Inventory," a table view, in your site’s Admin Datasets or Asset Inventory View.
Note: If the "View as a Dataset" button is greyed out, you will need to reach out to us at email@example.com to get your asset inventory set up.
What does the Asset Inventory include?
The columns of the Asset Inventory contain information about every dataset, view, visualization, or story on your site. These include metadata fields such as name, description, and category, as well as statistics, such as number of visits and downloads.
The Asset Inventory is updated once per day.
Columns in the Asset Inventory include:
- URL: The full URL link to the dataset or view.
- UID: The unique, 4 digit identifier associated with the dataset or view.
- Public: (True or False) True if the dataset is public, false if it is private.
- Derived View: (True or False) True if the dataset/view is a derived or based on another dataset. For example, a filtered view of a dataset or a Data Lens page.
- Parent UID: The unique identifier of the parent dataset. This entry shows if the asset is a derived view and has a parent.
- Domain: The domain of the dataset.
- Type: The type of dataset or view, e.g. dataset, Table, chart, map view, data lens, story, file, href, gis map, filter, calendar.
- Name: The name of the dataset.
- Description: The description of the dataset.
- Visits: The number of visits to the dataset.
- Creation Date: The date the dataset was created.
- Last Update Date (data): The date the data in a dataset was last updated.
- Category: Categories associated with the dataset.
- Keywords: Any keywords associated with the dataset.
- Downloads: Number of downloads of the dataset.
- Owner: The name of the owner of the dataset.
- Contact Email: The contact email associated with the dataset.
- License: Any licensing associated with the dataset.
- Publication Stage: Has four possible values:
- Published: The authoritative and broadly available current copy of a dataset
- Unpublished: In working copy state. Does not show up in catalog. Waiting to be published.
- Snapshotted: An older copy of the dataset which has been saved for reference
- Copying: A dataset which is in the process of being copied internally. This is an ephemeral state.
- Published Version Name: The name of the currently published version of this dataset. Depending on the publication stage, this field may be blank.
- Published Version UID: The UID of the currently published version of this dataset. Depending on the publication stage, this field may be blank.
- Data Provided By: The name of the data source, for example an agency name.
- Source Link: The link to the source for the data.
- routing_approval: The status of a dataset in Routing & Approval; possible values are: Not in Queue, Pending, Approved, Rejected.
- api_endpoint: The SODA API json endpoint, following the format https://[data.yourgov.gov]/resource/[UID]/json.
- Update Frequency: The rate at which the dataset or view is updated. Options are Annually, Semi-Annually, Static, Quarterly, Ad Hoc, Monthly, Other.
- owner_uid: The UID of the user account who has ownership of that asset.
- View Moderation Status: The status of a dataset in View Moderation; possible values are:
- Not in Queue
- provenance: To distinguish between Community and Official views.
- Connected ESRI Map Layer Fields: The connected ESRI map layer generates metadata fields based on what is stored in the ESRI map layer. Some examples of commonly used fields include:
- Spatial Reference wkid
- Any custom metadata fields defined on the domain are also included
Published Version Name & Published Version UID will have entries if the asset is snapshotted or an unpublished version of a dataset that has already been published. For instance, if I publish a dataset and then create a working copy, that working copy is an unpublished version of the dataset where a published version also exists, and as such would have an entry in these columns.
How can I make use of the Asset Inventory?
The Asset Inventory is an important tool for program management and dataset tracking. You can search this dataset, sort it, filter and visualize as you would with any dataset. You can also download it or export it via OData or the API Endpoint so that you can use common tools like Excel and Tableau to do further analysis of your open data program.
Here are some examples of ways to use the Asset Inventory to answer important questions.
- What’s the breakdown of source datasets and derived views?
- Use the Visualize panel to create a Data Lens page view of this dataset. There add the column card for the Derived View column and compare the “false” entries, meaning source datasets, to the “true” entries, meaning derived views.
- What has been most recently published?
- Sort the Creation Date column in descending order, so that the most recently created asset is at the top.
- If you’d like to know only assets that are actually published, you can add a filter on the Publication Stage columns for “published.”
- Alternatively, you could also view these 2 cards on a Data Lens page and filter Creation Date by a set of dates.
- Who is publishing the most assets?
- First, you’ll want to create a filter on the dataset for entries where the column Publication Stage is “published."
- Then, use the Sort & Roll-Up function to group by the columns Owner and Type, roll-up on column UID by the count function. Finally, sort the UID column in descending order to have the highest count at the top.