@tgoprince, can you please review this proposal for a new structure for the catalog content?
My intention with this proposal is to keep the structure as simple as possible, cleaning the root folder. I created only two folders: a first one named datasets/ and containing all dataset folders, and a second one named resources/ for all other files provided by the catalog. We should keep only the license and readme file in the root folder.
A second option was to create specific (sub)directories for each different type of resources (in the main folder or inside the resources folder), like metadata, shapes, etc. However, keeping them in a same location and adding the corresponding documentation will make it easy for the user to find the resources and, in addition, reduces the files’ full paths.
I have already prepared the corresponding htaccess file for the generation of the permanent URLs of each file considering the structuration here proposed. I’ll publish it as soon as you approve this request.
@tgoprince, can you please review this proposal for a new structure for the catalog content?
My intention with this proposal is to keep the structure as simple as possible, cleaning the root folder. I created only two folders: a first one named
datasets/and containing all dataset folders, and a second one namedresources/for all other files provided by the catalog. We should keep only the license and readme file in the root folder.A second option was to create specific (sub)directories for each different type of resources (in the main folder or inside the resources folder), like metadata, shapes, etc. However, keeping them in a same location and adding the corresponding documentation will make it easy for the user to find the resources and, in addition, reduces the files’ full paths.
I have already prepared the corresponding
htaccessfile for the generation of the permanent URLs of each file considering the structuration here proposed. I’ll publish it as soon as you approve this request.