This table covers what each field means in the product directory, what the associated data type is for the field, and what each entry in the field represents.
The product_id and product_name are required, while all other fields are optional.
Name given to the product by the product team. (Required)
When a product is a child of a larger encompassing parent directory, the parent name is supplied here.
The live VA.gov link where the product is accessible in production.
Name of the front-end repository where the product code is based.
Name of the back-end repository where the product code is based.
Names of the other repositories where product code is based. This could be utilities maintained for the product or other ancillary code that supports the product.
The associated GitHub label to identify GitHub issues for this product. This label should be unique to this product.
The associated GitHub label to identify the team with primary control over the product.
The contract that this product’s development is fulfilling.
The end date for the contract.
The hub on VA.gov that the product is grouped under with other related products.
A true or false declaring if the product currently has a team designated to maintain it.
Name of the OCTO crew that the product team belongs to.
Name of the OCTO product owner for this product.
Name of the PM for the team responsible for the product.
The organizational unit within the VA enterprise that is the primary stakeholder for a product.
Product’s current status, either
Date that this product launched into a production environment.
The full URL where the product outline can be found.
The full URL where the principal product documentation is located.
The TestRail project ID of the product. The user inputs the Testrail project URL and the script processing will extract the ID from the URL. This can only be populated if the TestRail project was set up in terms of the product and not the team.
The level of authorization required for a user to access this product.
A list of API endpoints that this product provides for other products to consume for data.
A list of API endpoints that this product consumes for data, provided by other products or services.
The category group in salesforce that corresponds to this product.
The category group that labels this product for analytics to group like-products together.
Categorizes the product as either Apps, Forms, APIs & Systems, Profile, Content. These groupings are planned to be used in the platform console.
A unique identifier in the form of a UUID v4 that gives a constant value that will never change allowing reference to this product. (Required)
The file path of where the product code is located in the Github repository.
A timestamp from when the product was last modified. This is based on the last time new code was committed to GitHub for this product. This field is populated automatically.
True or false depending on if there are corresponding unit tests for the product.
True or false depending on if there are corresponding end-to-end tests for the product.
True or false depending on if there are corresponding contract tests for the product.
Comma-separated list of required package dependencies for the product.
A list of products that shows if the product depends on any other products to be able to run.
An array containing information about the feature. The information included is the name of the feature, the URL where it’s located, the date it launched, and what its current deployment status is (see launch date and deployment status definitions above).