Just trying out Metabase - clicked x-ray for a table. Just wow.
On closer inspection I saw two of the first cards both titled “My_things added in the last 30 days”. Numbers were different.
Clicked them and found out that one was base on a column “redigeret” where the other was based on “tilføjet”.
Is there a way to customize this behaviour?
Can I supply some form of term-mapping?
I should note that I turned of the helpful formatting (or similarly named) because it was very much not helpful.
Also of note is that many terms in our DW are Danish, and I found that Metabase isn’t (yet) localized for Denmark.
You can change how x-rays behave via Admin > Data Model by setting the closest matching Field Type for your columns of data.
Yes, if your database columns are not in English, then the Friendly Names are not very useful.
You are more than welcome to help translating Metabase in Danish - that can be done via https://poeditor.com/join/project/ynjQmwSsGh
(Jeg burde måske ha’ gjort det allerede, men det er et større projekt og kræver en del tid)
I see it.
I’m surprised to see that there is nothing resembling “edit date”. In fact the Field Type > Date and Time options sound like something that would be specific to certain types of data. “Cancelation”, “Join”, e.g. sound like subscription-oriented words.
Is there any way to add your own categories?
If we end up deciding to continue with Metabase, translating (or at least taking part in translating ) might be within reach - starting from scratch on 24K words and only being included when coverage is 100% is somewhat daunting, though.
Yeah, the types are a bit specific currently. There are several reason for that, legacy being one of them, but also that it wouldn’t be possible to do “smart” x-rays on custom field types, since x-rays are currently structured based on the know field types.
It’s a tricky subject you’re getting into, but you can have a look at how x-rays are generated by looking at these files: https://github.com/metabase/metabase/tree/master/resources/automagic_dashboards
Translating entire Metabase sounds like a great Christmas project, when you’re enjoying lock-down
I remember translating Thunderbird by myself during a long weekend. It was 12k strings - not words.
I tried x-raying two more tables, where Metabase seems to begin building the dashboard, then it disappears to be replaced by a splash screen, and then I am returned to home.
Seems like some process is crashing behind the scenes.
The main thing I can think of that the two x-ray-failing tables have in common, and which is “un-common” to the succeeding table I was referencing before, is the presence of a jsonb column (which doesn’t follow a single schema, in case that matters).
@aalasso That sounds like it probably crashed during the generating process.
Post “Diagnostic Info” from Admin > Troubleshooting.
And then all the lines from the time it causes the crash - Admin > Troubleshooting > Logs.
Perhaps it’s choking on something like jsonb like you say, but without the stacktrace, then it’s difficult to say.
@aalasso True dat, but the Mac App is fairly limited compared to other ways of running Metabase. It’s fine for a quick test run, but cannot be used for anything more than that.
I definitely weren’t planning on taking it to production
Anyway, a few more thoughts regarding the original topic of labels:
I totally get that Metabase is trying to be friendly here. But, especially when I have disabled Friendly Names, I would argue that it was more user friendly (no pun intended ) to choose a formatting that doesn’t try to guess a better name for a column.
When clicking through, I can see the applied filter pill, and its formatting (e.g. “lukket Previous 30 Days”).
In fact, in this case at least, it would be perfectly legible, in stead of actually quite misleading, to display:
“Opgave lukket in the last 30 days”
rather than
“Opgave added in the last 30 days”
And making it even more techy (like opgave.lukket) might even be preferable, in that it highlights the origin of the data even more.
Auto-generating anything is hard - doing it across many database types and languages is harder.
It’s not perfect - no auto-magic is - and if you think you have found a bug, or have ideas to a new specific functionality, then you are more than welcome to open an issue: https://github.com/metabase/metabase/issues/new/choose
I’m sure it doesn’t help that your data structure is Danish, while the UI is English - that makes mixed strings a lot harder to read.
) might be within reach - starting from scratch on 24K words and only being included when coverage is 100% is somewhat daunting, though.
