For a NADA catalog administrator, the process of publishing data and metadata consists of:
Documenting a dataset, i.e. generating structured metadata compliant with one of the standards and schemas used in NADA. These standards and schemas are documented at https://ihsn.github.io/nada-api-redoc/catalog-admin/# (opens new window) (and in the Schema Guide). The metadata can be generated using specialized software (metadata editors), using programming languages (like R or Python), or directly in NADA using the administrator interface (for all data types except geospatial). For microdata and for geographic datasets, it is highly recommended to make use of a specialized metadata editor, due to the complexity of the metadata standard. For other types of data, the use of a programming language like R or Python offers a powerful and higly-flexible option, recommended for automating tasks and when there is a need to "augment" metadata for example using machine learning solutions. The NADA administrator interface provides a user-friendly option to generate metadata, but should not be the preferred option as it does not provide (in its current version) the advanced functionalites of specialized metadata editors (especially for microdata), and the flexibility and reproducibility that the API option provides.
Publishing the metadata in the NADA catalog, using the NADA administrator interface or programmatically with the NADA API and NADAR or PyNADA.
Uploading data and other files (or providing links) for the resources to be made accessible on-line from the catalog, with a brief description. These resources must be uploaded with a brief description based on the simple external resources schema.
Defining an access policy that applies to the dataset, if and when relevant. This will determine how users can obtain access to the data (direct access, access from another repository, licensed access, no access, or other). This typically applies to microdata and geographic datasets.