[EPIC] Code.json UI and searchability
- Dominant language
- Python
- Stars
- 1.1k
- Forks
- 200
- Avg merge
- 4h 56m
- Merged PRs (30d)
- 5
Description
In order to make Code.json harvested results available for discovery and reporting, OMB wants the metadata searchable and filterable for code.json metadata.
We need to define whether these metadata records should exist in catalog.data.gov, or in a separate place.
The functionality (if not the metadata fields) should be similar to today's catalog:
- Search page with searchable/filterable fields
- Repository/record display page
- OpenSearch index of the metadata from the harvester
Need to work with OMB and other stakeholders (ie CDOC) to determine if these records should live alongside of metadata records concerning data assets or not. If not, should create new application similar to catalog but with customized filters and search criteria. If yes, then edit catalog to support these new metadata record types.
Recommend first ticket is a pros/cons analysis of in catalog versus new application, make recommendation, and circulate with OMB and/or CDOC.
Once the pathway is determined, new architecture should be designed and approved and development tasks created.
Contributor guide
Assessment
This issue has not been assessed yet.