User talk:Albertoleoncio
Metabase Office Hours, March 2025
Hi! Thank you for joining Metabase.
We'd like to invite you to the Metabase Office Hours, a virtual meeting with the Wikimedia Sverige team, where you'll have an opportunity to talk to us, ask any questions or share ideas for how Metabase could be improved.
The next meeting is scheduled for Monday, March 10, 2025. Register and access the meeting link and more info here.
Looking forward to seeing you! Alicia Fagerving (WMSE) (talk) 13:37, 26 February 2025 (UTC)
Metabase Office Hours, April 2025
Hi! Thank you for joining Metabase.
We'd like to invite you to the Metabase Office Hours, a virtual meeting with the Wikimedia Sverige team, where you'll have an opportunity to talk to us, ask any questions or share ideas for how Metabase could be improved.
The next meeting is scheduled for Wednesday, April 9, 2025. Register and access the meeting link and more info here.
Looking forward to seeing you! Alicia Fagerving (WMSE) (talk) 13:00, 1 April 2025 (UTC)
Wikimedia-specific descriptions on generic items
Hi, you might have noticed I have reverted a bunch of English descriptions for items with Capacity Exchange ID (P91). Me and User:Andreas_Kettelhoit_(WMSE) have discussed it a bit, and we decided it's better that if an item has same as on Wikidata (P1), we should make sure the items actually are equivalent. For example technical support (Q25780) links to Wikidata's technical support which is a general term, and not specifically Assistance provided for MediaWiki software, Wikimedia tools, and community tech issues. If we have Wikimedia world-specific descriptions for some items in Metabase, then they are not equivalent to their Wikidata equivalents, if that makes sense :)
On another note, I've been working on setting up some documentation for past and current data uploads in Projects, to highlight some structured work initiatives on specific types of items in Metabase. I wonder if you'd like to write a couple words about Capacity Exchange there? Specifically about the role Metabase plays for Capacity Exchange (the things we talked about on our last call), and the role of the Capacity Exchange ID (P91) property. Would be cool to highlight it in our documentation! --Alicia Fagerving (WMSE) (talk) 11:10, 2 April 2025 (UTC)
- Andreas, Alicia: In this case, do you have any suggestions on how to model these items? These descriptions, more wikimedia-specific than those in Wikidata, are essential for us. I could suggest substituting, in these created items, a new property such as "generically associated on wikidata" in place of "same as on wikidata". Albertoleoncio (talk) 18:55, 2 April 2025 (UTC)
- Hi Albertoleoncio, and thanks for the input! We will discuss this at our regular work meeting tomorrow afternoon, and as soon as we have found a long-term sustainable solution, we will of course communicate it back to you. If there is anything else you would like us to take into account, do not hesitate to contact us. As mentioned, our internal work meeting will take place tomorrow shortly after lunch CEST (UTC+2). Happy editing! -- Andreas Kettelhoit (WMSE) (talk) 07:57, 3 April 2025 (UTC)
- Hi User:Albertoleoncio, you say that these items are very important for Capacity Exchange, I would like to understand some more about this :) Like, how are you going to use them? I've looked around the CapX platform, and in the capacity directory, the capacities have their Wikidata ID's and descriptions. If I put myself in the perspective of a user, that looks okay to me. Is there some particular reason why you need different descriptions? As I said, I'm trying to understand your point of view better so that we can figure out a good solution together. --Alicia Fagerving (WMSE) (talk) 12:45, 4 April 2025 (UTC)
- Andreas, Alicia: We are migrating our description source from Wikidata to Metabase. The reason is that while Wikidata is a more established database, its descriptions are often too generic for our specific use case on Capacity Exchange, which is a platform built for the Wikimedia movement. Our goal is to have more tailored descriptions that better align with how these capabilities are specifically used within the Wikimedia movement. That's why we were hoping that Metabase would be the place to store these descriptions. Albertoleoncio (talk) 17:38, 4 April 2025 (UTC)
- User:Albertoleoncio: I see, I understand your point, and it makes total sense. I think what we're dealing with is the question of how tightly our platforms should be interconnected, and how to best indicate what's relevant to CapX. I've got an idea: What about creating a new property here, Capacity Exchange description or something like that, where you would have control over what's there? A concern I have is that even if we do change the descriptions of our items to more CapX-compatible ones, later on some other editor will change them again, either to the Wikidata description or something completely else, not aware of the fact that CapX is using them. And then you won't even notice it unless you're actively watching all changes. So a separate property would make it clear that the description is used by another project. Would that be helpful? --Alicia Fagerving (WMSE) (talk) 12:17, 8 April 2025 (UTC)
- Andreas, Alicia: We are migrating our description source from Wikidata to Metabase. The reason is that while Wikidata is a more established database, its descriptions are often too generic for our specific use case on Capacity Exchange, which is a platform built for the Wikimedia movement. Our goal is to have more tailored descriptions that better align with how these capabilities are specifically used within the Wikimedia movement. That's why we were hoping that Metabase would be the place to store these descriptions. Albertoleoncio (talk) 17:38, 4 April 2025 (UTC)
- Hi User:Albertoleoncio, you say that these items are very important for Capacity Exchange, I would like to understand some more about this :) Like, how are you going to use them? I've looked around the CapX platform, and in the capacity directory, the capacities have their Wikidata ID's and descriptions. If I put myself in the perspective of a user, that looks okay to me. Is there some particular reason why you need different descriptions? As I said, I'm trying to understand your point of view better so that we can figure out a good solution together. --Alicia Fagerving (WMSE) (talk) 12:45, 4 April 2025 (UTC)
- Hi Albertoleoncio, and thanks for the input! We will discuss this at our regular work meeting tomorrow afternoon, and as soon as we have found a long-term sustainable solution, we will of course communicate it back to you. If there is anything else you would like us to take into account, do not hesitate to contact us. As mentioned, our internal work meeting will take place tomorrow shortly after lunch CEST (UTC+2). Happy editing! -- Andreas Kettelhoit (WMSE) (talk) 07:57, 3 April 2025 (UTC)
Andreas, Alicia: It could work for English, but we also intend to localize these descriptions for other languages, including inviting CapX users to come to the metabase to create and review translations. Keeping the descriptions as properties would be a bit limiting. However, I was wondering how to accommodate these needs and figured it might be interesting to create new items, since Wikidata items and CapX capabilities are actually different things. For example, reporting (Q34240) could be modeled like this:
| Property | Value |
|---|---|
| instance of (P5) | index term (Q12) |
| same as on Wikidata (P1) | Q60050485 |
| Description | producing a report (oral or written) |
| Property | Value |
|---|---|
| instance of (P5) | CapX capacity |
| facet of (P67) | reporting (Q34240) |
| Capacity Exchange ID (P91) | 19 |
| Description | Documentation of activities, outcomes, and impact within Wikimedia projects, often required for grants and community initiatives |
What do you think? Can we work like this? Albertoleoncio (talk) 13:05, 8 April 2025 (UTC)
- Hi Albertoleoncio! Alicia and I have come to the conclusion that your proposed modelling – which was similar to an idea we had ourselves – is the easiest way to solve the problem.
- To make your work easier, I have made four items, so you can see the structure "live": Wikidata (Q34532), workshop (Q34533), GLAM (Q34534), tutorials (Q34535). Note that I have given each item an alias, this is because we need to be able to easily distinguish CapX items from their "parent item". It's also important that you move the Capacity Exchange ID (P91) to the CapX capacity (Q34531) items.
- If you have any thoughts, questions or need help with anything, don't hesitate to write back to us. -- Andreas Kettelhoit (WMSE) (talk) 13:20, 9 April 2025 (UTC)
Metabase Office Hours, August 2025
Hi! We'd like to invite you to the Metabase Office Hours, a virtual meeting with the Wikimedia Sverige team, where you'll have an opportunity to talk to us, ask any questions or share ideas for how Metabase could be improved.
The next meeting is scheduled for Wednesday, August 27, 2025. Register and access the meeting link and more info here.
Looking forward to seeing you! Alicia Fagerving (WMSE) (talk) 13:42, 19 August 2025 (UTC)