Currently erddapper uses its own internal dataset id, which is potentially distinct from the ERDDAP dataset id in the generated ERDDAP config. While this was intentionally implemented to allow for flexibility, it is confusing in practice and can also allow for situations where multiple erddapper datasets have the same ERDDAP id, which will produce an ERDDAP datasets.xml with redundant dataset ids (only one will be loaded).
Proposal is to update erddapper to use a single dataset id for its own dataset management and the ERDDAP dataset id, conceptually simplifying the dataset management process and eliminating duplicate ERDDAP dataset id scenario described above.
Currently erddapper uses its own internal dataset id, which is potentially distinct from the ERDDAP dataset id in the generated ERDDAP config. While this was intentionally implemented to allow for flexibility, it is confusing in practice and can also allow for situations where multiple erddapper datasets have the same ERDDAP id, which will produce an ERDDAP datasets.xml with redundant dataset ids (only one will be loaded).
Proposal is to update erddapper to use a single dataset id for its own dataset management and the ERDDAP dataset id, conceptually simplifying the dataset management process and eliminating duplicate ERDDAP dataset id scenario described above.