Property talk:P3267

From Wikidata
Jump to navigation Jump to search

Documentation

Flickr user ID
identifier for a person or organisation, with an account at Flickr
Associated itemFlickr (Q103204)
Applicable "stated in" valueFlickr (Q103204)
Data typeExternal identifier
Domainhuman (Q5) or organization (Q43229)
Allowed values\d{5,11}@N\d{2}
Usage notesTurn a username into a user ID with the webform found at https://www.webfx.com/tools/idgettr/
ExampleIan Emes (Q5981474)47978897@N06
SpaceX (Q193701)130608600@N05
Sourcehttps://www.flickr.com/
Formatter URLhttps://www.flickr.com/people/$1
Tracking: usageCategory:Pages using Wikidata property P3267 (Q28973087)
Related to country United States of America (Q30) (See 762 others)
See alsowebsite username or ID (P554)
Lists
Proposal discussionProposal discussion
Current uses
Total2,949
Main statement2,90098.3% of uses
Qualifier30.1% of uses
Reference461.6% of uses
Search for values
[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)
List of violations of this constraint: Database reports/Constraint violations/P3267#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)
Conflicts with “website account on (P553): Flickr (Q103204): this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P3267#Conflicts with P553, hourly updated report, search, SPARQL
Scope is as main value (Q54828448), as qualifier (Q54828449), as reference (Q54828450): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P3267#Scope, hourly updated report, SPARQL
Format “\d{5,11}@N\d{2}: 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/P3267#Format, SPARQL
Allowed entity types are Wikibase item (Q29934200), Wikibase MediaInfo (Q59712033): 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/P3267#Entity types

Discussion[edit]

Find the actual ID[edit]

use this form 1Veertje (talk) 22:15, 6 June 2019 (UTC)[reply]

Thank you for posting this. It allowed me to realize that I was conflating ID with username. — Dcflyer (talk) 11:05, 14 June 2019 (UTC)[reply]
An alternative is this tool. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:39, 3 October 2019 (UTC)[reply]

Constraint violations: format[edit]

As of this writing, there are 753 format constraint (Q21502404) violations for format as a regular expression (P1793), out of 897 uses of Flickr user ID (P3267). After looking at the history of this property, it doesn’t appear that the regular expression (Q185612) was subject to any changes; however the overwhelming number of Flickr account usernames do not match this regex.

Dcflyer (talk) 10:41, 14 June 2019 (UTC)[reply]

SOLVED — see above, to obtain the actual ID from the username: Property talk:P3267#Find the actual ID

Dcflyer (talk) 10:57, 14 June 2019 (UTC)[reply]

How to record corresponding username and its changes?[edit]

Flickr usernames can be changed, hence why the unique ID is used here instead. For example, SpaceX (Q193701) had the username 'spacexphotos' until sometime in 2016 or early 2017 (based on Wayback Machine snapshots), when it was changed to 'spacex' instead. What would the best way of recording this be? (The current situation seems very poor to me.) One idea that comes to mind is having two entries with the same ID value but a different website username or ID (P554) qualifier and giving the current one a preferred rank. –JustTheRealArchivist (talk) 23:29, 26 January 2022 (UTC)[reply]

Converting existing entities to use the user ID[edit]

Since Dcflyer’s post in 2019, the number of entities which use a text string rather than a user ID has risen to a little over ~1000.

As part of the data modelling for Flickypedia, I’d quite like to use this field! In particular, when linking to a Flickr photographer in creator (P170), I want to link to the Wikidata entity where it exists. And in turn, I’d rather my code only had to query for the canonical user ID, and not look for the text versions as well.

I’ve got a script which can do bulk lookups of the "username ~> user ID", so I’m going to do that and gradually clean up the existing data in this field. I won’t be able to get everything, because some of these entities are protected or semi-protected, but hopefully I can make it a little better! Alexwlchan (talk) 15:35, 10 November 2023 (UTC)[reply]