In order to track changes and make available code.json records for OMB and the public, we want to make sure agencies can create code.json type harvest sources, and the records will be stored and tracked in our harvest system.
This will include metadata validation using https://github.com/DSACMS/gov-codejson/tree/main/schemas, which should allow choosing 1.0 and 2.0 validation levels (since we are unfamiliar with the versions and tracking). A ticket should be created to analyze and decide what schemas (there look to be 7) overlap, or which ones should be utilized.
Harvest errors and warnings should be reported per normal.
The type of record should be new, something like code-metadata, or something.
It should be confirmed that these record types shouldn't be synced (or attempted to be synced) to openSearch at this time, that part is TBD.
In order to track changes and make available code.json records for OMB and the public, we want to make sure agencies can create code.json type harvest sources, and the records will be stored and tracked in our harvest system.
This will include metadata validation using https://github.com/DSACMS/gov-codejson/tree/main/schemas, which should allow choosing 1.0 and 2.0 validation levels (since we are unfamiliar with the versions and tracking). A ticket should be created to analyze and decide what schemas (there look to be 7) overlap, or which ones should be utilized.
Harvest errors and warnings should be reported per normal.
The type of record should be new, something like code-metadata, or something.
It should be confirmed that these record types shouldn't be synced (or attempted to be synced) to openSearch at this time, that part is TBD.