Property talk:P9078

Documentation

• Start a query
• Properties using this qualifier (statistics)
• Count

Discord invite ID
identifier for the subject's official Discord server; use as qualifier for P9345 "Discord server numeric ID"

Represents	Discord server invite (Q111602914)
Applicable "stated in" value	not applicable
Data type	External identifier
Allowed values	[a-zA-Z0-9][a-zA-Z0-9-]*[a-zA-Z0-9]
Usage notes	Use P9345 (Discord server numeric ID) as the main statement, and instead add the invite ID as a qualifier. If the numeric ID is not known, set it to unknown value.
Example	Destructive Creations (Q33255668) → 4MquGQY Running with Scissors (Q498812) → rws Grand Theft Auto Online (Q14594724) → gtao
Source	https://discord.com
Formatter URL	https://discord.com/invite/$1 https://discord.gg/$1
See also	Skype username (P2893), Discord username (P9101), Twitch channel ID (P5797), Discord server numeric ID (P9345)
Lists	Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P9078
Proposal discussion	Proposal discussion
Current uses	Total 1,325 Main statement 441 out of 6,700,000 (0% complete) 33.3% of uses Qualifier 872 65.8% of uses Reference 12 0.9% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Scope is as qualifier (Q54828449), as reference (Q54828450): the property must be used by specified way only (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P9078#Scope, SPARQL

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P9078#Entity types

Format “[a-zA-Z0-9][a-zA-Z0-9-]*[a-zA-Z0-9]”: value must be formatted using this pattern (PCRE syntax). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P9078#Format, SPARQL

Citation needed: the property must have at least one reference (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P9078#citation needed

This property is being used by: ja:Template:Discord Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

has quality documentation

Possible values for Discord invite ID (P9078)has characteristic (P1552) are unofficial Discord server (Q105222350), verified Discord server (Q105192287), Discord Partner (Q105197552), and verified and partnered Discord server (Q105222072). Verified servers have a green check mark next to their name—partners have a blue badge. According to the usage instructions you do not need to specify Q105222345.

Feel free to edit the paragraph above. Maybe we should create a new property so that this documentation is not necessary. I only figured this out with a query. —Dexxor (talk) 08:48, 5 February 2021 (UTC)

There are servers that are official (in that they were created by people representing the subject) but not verified (in that they haven't pursued verification or have been unsuccessful). In those cases, is one of the aforementioned values appropriate? Overcast07 (talk) 10:53, 21 February 2021 (UTC)

Use No quality @Overcast107:--Trade (talk) 09:03, 24 February 2021 (UTC)

@Overcast07:--Trade (talk) 09:08, 24 February 2021 (UTC)

@Trade: @Dexxor: If the Discord server numeric ID property is created, should the "has quality" required qualifier constraint be moved to the new property? To me it would make sense to use the new property as a qualifier on this property, keep only the qualifiers/references specific to the invite (i.e. point in time) on the statements for this property, and then move qualifiers referring to the server itself (start time, number of members, etc) to a statement for the new property. This would prevent information from being duplicated for servers with multiple valid invite IDs. Overcast07 (talk) 09:32, 15 March 2021 (UTC)

@Trade: @AntisocialRyan: Is this a good idea? Now that Discord server numeric ID (P9345) exists, it seems it would be the right time to transfer the data about the servers to the new property. Overcast07 (talk) 13:41, 9 April 2021 (UTC)

 Support @Trade: @Overcast07: Thanks for the ping, I think Discord server numeric ID (P9345) should be the main property for servers instead of Discord invite ID (P9078) because of the multiple invites, so yes, I support this. Seems like a lot of work though. Also, I think you meant to say numeric ID instead of invite ID. AntisocialRyan (talk) 23:35, 9 April 2021 (UTC)

Yeah, that's what I meant. Overcast07 (talk) 16:40, 11 April 2021 (UTC)

It's nothing a QS batch can't deal with @Overcast07: --Trade (talk) 07:44, 12 April 2021 (UTC)

Is Q33255668#P9345 what you had in mind? @Overcast07, AntisocialRyan: --Trade (talk) 22:28, 20 May 2021 (UTC)

Yes I believe that's what we both meant, since there can be multiple invites but just one ID. AntisocialRyan (talk) 00:49, 21 May 2021 (UTC)

@Trade: I used SiIvaGunner (Q96419348) to try it out, so I would say your idea of what it should be like matches what mine was. Overcast07 (talk) 16:30, 25 May 2021 (UTC)