Currently I have digested a STAC catalog onto a resto instance and in the process of learning to use the uploading scripts, and some changing of names and the STAC structure ended up creating persistant data(metadata) for my STAC catalog. There were some items that became duplicated after changing the name of my catalog and even after browsing the STAC hosted on catalog.edito-infra.mercator-ocean.eu/catalogs/catalogs, and seeing that all the collections and the items from within have been deleted. The catalogs have stayed present, and thus will prevent an organized upload of a renewed catalog, that has the same title as the catalogs that stay on the resto instance.
Much in the same way as to delete a collection, with the right authorization, deleting a catalog should also be possible.
Currently I have digested a STAC catalog onto a resto instance and in the process of learning to use the uploading scripts, and some changing of names and the STAC structure ended up creating persistant data(metadata) for my STAC catalog. There were some items that became duplicated after changing the name of my catalog and even after browsing the STAC hosted on catalog.edito-infra.mercator-ocean.eu/catalogs/catalogs, and seeing that all the collections and the items from within have been deleted. The catalogs have stayed present, and thus will prevent an organized upload of a renewed catalog, that has the same title as the catalogs that stay on the resto instance.
Much in the same way as to delete a collection, with the right authorization, deleting a catalog should also be possible.