Looking at the recent update to the readme describing the developer process of rendering new datasets in the catalog, there are still several manual steps that would all ideally be scripted and automatic.
The following list items can eventually all have their own tracking issues:
Validating completed metadata sheets
Turning completed metadata sheets into tabby TSV files
Adding tabby import statements to the dataset tabby file
Deal with the name and version field automatically based on specified dataset type
Looking at the recent update to the readme describing the developer process of rendering new datasets in the catalog, there are still several manual steps that would all ideally be scripted and automatic.
The following list items can eventually all have their own tracking issues:
datasettabby filenameandversionfield automatically based on specified datasettype