Ongoing discussions

HiI’m working on accessibility fixes for a client who is using a portal theme.Apparently, many of the issues originate from the portal theme. So I would need to edit the HTML in many places, and in some cases even add JavaScript.Currently, I can’t find any way to change the HTML, and I saw in the documentation that adding JavaScript isn’t allowed for security reasons, which I understand.So I was looking into how I can contribute to the theme, but I can’t seem to find how to do that. That’s why I opened this topic.Thanks for the feedback.Matthias

We are evaluating our move to the marketplace experience and support have been wonderful in helping achieve some of our goals that we’ve always wanted.One, is to have a couple of feeds on the front page showing the latest datasets but also latest publications (a new asset category we have created).Supports suggestion was to setup a couple of new contexts fed from a dataset of datasets. Which weve done and got so far but realised a dataset of datasets is just that. datasets only. Not assets. Also looking at the API I cannot see a way to actually query the asset catalogue. Question is: Has anyone successfully implemented a feed of various assets powered by the catalogue itself and not having to maintain a separate dataset? Attached is my current code block that reads from a dataset of datasets and incorporates the suggestions from support. Although the refine.category doesnt work as dataset of datasets doesnt include anything but datasets and also no category. Also the Asset slug wont wo

Dear Support Team,we have received the following request from a user regarding dataset https://data.bs.ch/explore/dataset/100120/, which we would like to forward to you for further investigation.The user reports an inconsistency in the handling of the field vu_jahr: The field is defined as a date in the dataset schema. However, when exporting the dataset, the field appears to be delivered as a string. When querying the dataset via ODSQL (using a SELECT vu_jahr GROUP BY vu_jahr query), the result returns proper datetime values (e.g. 2011-01-01 00:00:00+00:00, etc.). This inconsistent behavior causes issues in the user’s synchronization process. While they have implemented a workaround on their side, they asked whether this could be fixed at the platform level.Example query used by the user:https://data.bs.ch/api/explore/v2.1/catalog/datasets/100120/exports/csv?lang=de&timezone=Europe%2FBerlin&use_labels=false&delimiter=%3B&select=vu_jahr&group_by=vu_jahrCould you