User Details
- User Since
- Jan 6 2015, 3:55 PM (479 w, 6 d)
- Availability
- Available
- IRC Nick
- Kai_WMDE
- LDAP User
- Kai Nissen (WMDE)
- MediaWiki User
- Kai Nissen (WMDE) [ Global Accounts ]
Mon, Mar 4
Wed, Feb 28
Tue, Feb 27
Thu, Feb 22
Feb 14 2024
Feb 13 2024
Needs a configuration change deployment after deploying the FOC
Feb 6 2024
I can't find anything on a naming convention in the documentation. @Ottomata Can you point us to the respective doc page if there is one? It may be a good idea to put it in a folder with a general name, so it might also be used by others. The schema itself should also have a general name, so we can reuse it for community engagement campaigns. I'd suggest analytics/banner/wmdebanners. Or analytics/banner/wmdefundraising, if we want to introduce a different schema for community engagement banners.
- Check with PM for additional fields needed (can be included with a $ref, see other schemas in the repo). The schema page makes it look like /fragment/analytics/common/2.0.0# would be required/a good choice, but then we may also need PM-mandated values for stream and domain. At least stream should be defined.
Is this for the custom_data field (last table row in the description of the parent task)? If so, and we decide to use it, we can name the stream similar to the schema (e. g. banner.wmde_fundraising). I doubt, that anything will ever consume the stream, though.
Not sure about the domain. If possible, we shouldn't bind this to a domain. We could use a general wikipedia.org, but would that block us from ever triggering events from banners on commons.wikimedia.org?
Looks all good to me.
@gabriel-wmde
The FOC doesn't seem to know the newly introduced moderation reason, yet. Apart from that it works as expected.