tum-gis / ckan-docker Goto Github PK

• https://github.com/ckan/ckan/releases/tag/ckan-2.9.11

Feature description

Currently used basemap (Stamen Terrain) is not going to be avaliable from 31. October 2023 (see attached image).

Suggested solution

It should be used other basemap which is supported. Possible configuration could be found here.

Code snippets

No response

The following issues are opened in their repositories:

• Main category Preview in Dataset view
• On the Start Page of the catalog should be just Main Category visible
• Remove „Add to group“ button
• #21
• Spatial Attirbute when Dataset is Created - remove (+) symbol and show dataset extent with map when Dataset is created
• remove "visibility" attribute and if the "Custom Field" is not defined, then don't show this as attribute when the dataset is created
• mandatory fields update in ckanext-scheming

When one of the bugs from the list is solved, it will be marked and the issue will be updated.

We are open for extending this repo with other images, that address the needs of your municipality/organizations/anything else.
This fact should be documented more cleary in README.md.

• Describe the structure of the repo and why we chose this structure more clearly
• Describe the conditions we have to add you own image/folder
  • The images needs to use the base image provided in this repo
  • Proper documentation
  • Move any documentation of custom images and base image to subfolders
• Describe the process of how getting your folder with you own image
  • Add folder
  • Add docs on what extensions are included
  • Add/adapt workflow, if CI/CD features are desired

Please document each version in the CHANGELOG.

This has never been completed and has never been used. Do we really need it @MarijaKnezevic?

Currently, we build dev images for each commit to a PR and publish them at https://github.com/tum-gis/ckan-docker/pkgs/container/ckan-sddi-dev. This should be cleaned up, e.g. when a PR is merged/released.

Feature description

Currently, on a few settings, e.g. the about text are expose via configuration variables.

Other important customizations are not accessible via variables, e.g.:

• Default groups and organizations
• Background image (see below)
• Text below intro text (see below)

Suggested solution

Expose these options as config variables. This has to be done in the ckanext-grouphierarchy-sddi:

• Default groups and organizations: Path to groups_orga.json. This might require to have separate files for main categories + topics and organizations, hence two different config parameters. The default value should point to the SDDI default config files.
  • It should be possible to specify the config files path as a) URL to an external file somewhere on the web, b) as file path inside the ckan container. The file needs to be structured like this.
  • Is a similar mechanism possible for the icons of groups, topics usw.?
• Background image (see below): Path to background.jpg
• Text below intro text (see below): Text to be show.

Upstream tasks

• tum-gis/ckanext-grouphierarchy-sddi#8

What happened?

There is no LICENSE file in this repository.

Steps to reproduce

irrelevant

Configuration

_irrelevant_

Versions and environment

irrelevant

If applicable, what browsers are you seeing the problem on?

No response

Relevant log output

No response

Additional information and comments

No response

Feature description

In the current version, the Spatial Dataset extent preview is part of the Additional Info table.
The whole potential of the preview is not used and it is required to move the Spatial Dataset extent preview as separate section (as marked in the following image):

On the left side of the image with red color is marked position of Spatial Dataset extent preview as part of Additional Info table. On the right side of the image with green is marked position of Spatial Dataset extent preview right as separate section after Data and Resources section.

Suggested solution

No response

Code snippets

No response

As shown below, in the packages, a lot of images are tagged with the commit SHA, that triggered the build workflow.
This clutters the packages, is not used and should be removed.