But this is not always desired. Often, only updates related specifically to the javascript and html components are needed, and one would want to specify this.
A catalog-update command could form the basis of new functionality to specify updates more granularly. Or otherwise the existing -create can be amended to include such functionality.
@mslw it would be great if you can share your experience in terms of what you typically want to achieve when updating a catalog (not its metadata), and how the existing commands and complexities currently prevent you form achieving that.
Currently, running
catalog-create --force
on an existing catalog will overwrite a bunch of files:https://github.com/datalad/datalad-catalog/blob/main/datalad_catalog/webcatalog.py#L78-L106
But this is not always desired. Often, only updates related specifically to the javascript and html components are needed, and one would want to specify this.
A
catalog-update
command could form the basis of new functionality to specify updates more granularly. Or otherwise the existing-create
can be amended to include such functionality.@mslw it would be great if you can share your experience in terms of what you typically want to achieve when updating a catalog (not its metadata), and how the existing commands and complexities currently prevent you form achieving that.