Update webpage

gammacat/catalog.py

@@ -69,7 +69,7 @@ def __init__(self, data, path):
 
     @classmethod
     def read(cls):
-        path = gammacat_info.base_dir / 'input/gammacat/gamma_cat_dataset.yaml'
+        path = gammacat_info.base_dir / 'input/gamma_cat_config/gamma_cat_dataset.yaml'
         data = load_yaml(path)
         return cls(data=data, path=path)
 
@@ -513,7 +513,7 @@ class CatalogSchema:
     """Helper class to apply the schema."""
 
     def __init__(self):
-        self.colspecs = load_yaml(gammacat_info.base_dir / 'input/gammacat/gamma_cat_columns.yaml')
+        self.colspecs = load_yaml(gammacat_info.base_dir / 'input/gamma_cat_config/gamma_cat_columns.yaml')
 
     def format_table(self, in_table):
         """Make a new table, formatting things according to this schema.

webpage/data/catalog.rst

@@ -16,4 +16,7 @@ Why multiple formats?
   It supports vector columns, which we use for spectral points.
 * The ECSV and YAML variant are more for us working on gamma-cat,
   to have a text-based, version control friendly format where it's
-  easy to see which changes occurred from one version to the next.
+  easy to see which changes occurred from one version to the next.
+
+We recommend to have a look at `gamma_cat_columns <https://github.com/gammapy/gamma-cat/blob/master/input/gamma_cat_config/gamma_cat_columns.yaml>`__ in which all columns of the catalog are defined together with additional information, e.g. description and datatype of the entry.
+Moreover, in `gamma_cat_dataset <https://github.com/gammapy/gamma-cat/blob/master/input/gammacat/gamma_cat_dataset.yaml>`__ for each source the reference_id of the data in the catalog is given (more precicely, this file tells the python scripts which references are used to create the catalog).