GSA / GSA/ITDB-schema

FY21 Projects Questions

Open
#347 3 comments 0 reactions 0 assignees View on GitHub
Resolved
Dominant language
No language data
Stars
20
Forks
30
PR merge metrics
No merged PRs in 30d

Description

Below are questions/concerns related to projects, based on the XSD and the validation and data dictionary changes. They are mostly technical in nature and are not a high priority at this time for any resolution.

1. The metricID and agencyMetric ID validation incidates an error when it "does not match an existing Performance Metric." To confirm, does this mean any metric (even if not in Strategic and Business Results) will be allowed? I would also assume that deactivated and retired metrics would be excluded.
2. The error for measurementCondition reads "Field measurementCondition with value XXXX only allows integers from the set: {over target, under target}." As the validations indicate a varchar(15), will this field supply "integers" or text? Given that it is text in the existing schema, I am expecting text.
3. The XSD contains a maxOccurs for the number of prod and test releases of 3, which makes sense. However, it seems releasesToProd and releasesToTest should have a minimum occurances of 0 as a new or future activity may not yet have any releases. Similarly, the number of dates to provide should also be set to 0 as it does not appear there is a way to otherwise clear out a set of dates, if they were submitted in error. (For example, activity provides a production date but actually meant to set it for test as there is no production deployment yet, or the case of providing the data for the wrong activity.) This seems like it would also match the validations, which indicate not providing this data is only a warning.
4. The rollback percentage and release cadence fields are both listed as warnings, but the validation message uses "is required".
5. The validations for rollback percentage indicate "rollbackPercentage with value XXXX requires data as a rate, values must be numbers between 0-1 in the following format: x.xxxxxx". However, the data dictionary lists "5.5" as an example. As OMB is asking for a percentage, we will be collecting data from users as a 0-100 decimal values but can easily convert it - we just need to know which value is expected.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.