System Catalog exposed as a CKAN dataset

There are several mechanisms like DCAT and data.json to expose the catalog metadata. Why not have some system-generated datasets as well exposed in the CKAN catalog?

This echoes system catalog tables popular in relational databases - pg_class in PostgreSQL, information_schema in MySQL, etc. where you can use the same CKAN API commands to interrogate the CKAN system catalog.

This also helps with common developer issues like looking up the table_id of a dataset in the datastore, etc.

Start by reviewing CKAN's catalog and API entry points, then compare the proposed behavior with the PostgreSQL and MySQL system-catalog examples named in the issue. Done would require a defined set of system-generated datasets that can be interrogated through the existing CKAN API, but the issue does not specify the datasets, files, or tests involved.

Written by the indexing model from the issue text.