Property talk:P6760

Latest comment: 2 days ago by Shisma in topic Numeric IDs no longer exposed in redesign

Documentation

Know Your Meme ID
identifier for a Know Your Meme article
[create Create a translatable help page (preferably in English) for this property to be included here]
Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Trumpwave (Q80724407)
List of violations of this constraint: Database reports/Constraint violations/P6760#Unique value, SPARQL (every item), SPARQL (by value)
Single value: this property generally contains a single value. (Help)
List of violations of this constraint: Database reports/Constraint violations/P6760#Single value, hourly updated report, SPARQL
Format “[1-9][0-9]*: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P6760#Format, hourly updated report, 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/P6760#Entity types
Scope is as main value (Q54828448), 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/P6760#Scope, SPARQL
Format “([1-9][0-9]*|[a-z\-]+): 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/P6760#Format, SPARQL
Item “instance of (P31): Items with this property should also have “instance of (P31)”. (Help)
List of violations of this constraint: Database reports/Constraint violations/P6760#Item P31, hourly updated report, search, SPARQL
Conflicts with “instance of (P31): single (Q134556), album (Q482994), song (Q7366): this property must not be used with the listed properties and values. (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/P6760#Conflicts with P31, SPARQL
Label required in languages: en: Entities using this property should have labels in one of the following languages: en (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/P6760#Label in 'en' language, search, SPARQL

Updating m'n'm catalog edit

@Trivialist: I tried adding the property number to the mix'n'match catalog, without success. So far I couldn't use it for that reason. How can we fix it? NMaia (talk) 11:26, 16 May 2019 (UTC)Reply

Usage instructions no longer working edit

The current usage instructions no longer worked for me as there's no longer the substring data-item-id in the source code. However, I was able to get the ID from the social network preview picture as declared in the og:image-meta-tag. The following JavaScript snippet did the trick for me:

(function(){
const parts = document.querySelector("meta[property='og:image']").attributes.content.value.match(/facebook\/(\d{3})\/(\d{3})\/(\d{3})\//);
alert(parseInt(`${parts[1]}${parts[2]}${parts[3]}`));
})();

--Nw520 (talk) 20:21, 16 January 2021 (UTC)Reply

@Nw520: You can find it in the source code after "<article class='entry' id='entry_" gobonobo + c 14:46, 21 January 2021 (UTC)Reply

Incorrect format? edit

It seems that at least one KYM entry, I accidentally (Q114969188)) has a numeric ID that doesn't actually lead to the correct entry. The data item ID for "I accidentally" is 57, but the URL https://knowyourmeme.com/memes/57 leads to a different KYM entry. --Veikk0.ma (talk) 21:09, 23 January 2023 (UTC)Reply

Fixed. Infrastruktur (talk) 07:20, 24 January 2023 (UTC)Reply

numeric IDs no longer appear on page edit

Numeric IDs for KYM pages are now no longer included in the page source code in any place. They still work for links, but I don’t know how to find them anymore besides looking at web archives from before the change. I’ll try to update the English usage instructions soon. I feel like there must be a way to find IDs without resorting to archives, but I don’t know what it might be. — gabldotink [ talk | contribs ] 22:30, 23 January 2024 (UTC)Reply

I am still finding the numeric ID with the element inspector or by class='entry' id='entry_ or data-item-id=" in the source code. Regards Kirilloparma (talk) 04:49, 24 January 2024 (UTC)Reply
That’s weird, I still can’t see it. I checked on multiple pages (including the page you linked) and searched for both the HTML attributes and the ID directly, but they weren’t there. — gabldotink [ talk | contribs ] 05:06, 26 January 2024 (UTC)Reply

Numeric IDs no longer exposed in redesign edit

It seems that I received a redesign on Know Your Meme, and the numeric IDs we use here are no longer exposed in the source code. Anybody know an easy way around it? -wd-Ryan (Talk/Edits) 21:02, 25 April 2024 (UTC)Reply

I've made a userscript that changes to url in the address bar of the browser to show the id in the format of the formatter url property:
User:Shisma/userscript-knowyourmeme.js
Shisma (talk) 11:40, 11 May 2024 (UTC)Reply
Return to "P6760" page.