Property talk:P4705
Documentation
identifier in the videogame database ZXDB
List of violations of this constraint: Database reports/Constraint violations/P4705#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4705#Type Q7889, Q40056, Q62651817, Q416, Q121504207, Q383826, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4705#Item P400, search
List of violations of this constraint: Database reports/Constraint violations/P4705#Item P400, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4705#Entity types
List of violations of this constraint: Database reports/Constraint violations/P4705#Scope, SPARQL
![]() |
This property is being used by: Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
|
Value format
[edit]@Thierry Caro: Hi, during data import (example), value was not zero padded. If you click on ZXDB ID (P4705) of 1942 (Q55532) the link doesn't work. The value must be "0009297", not "9297". --Rotpunkt (talk) 23:53, 8 January 2018 (UTC)
- @Rotpunkt: Comes from this. Thierry Caro (talk) 06:59, 9 January 2018 (UTC)
- @Rotpunkt: This was my mistake: when I requested the property, I was under the impression that there were always three superfluous leading zeroes (led astray by the fact that spectrumcomputing.co.uk, which has the same underlying database, does not need zeroes). After creation, when making the Mix’n’match catalogue, I realised this was not the case − eg this does not work − and edited the Property accordingly. We would however need to fix all existing values to pad them with zeroes − not sure how to best do that :/ Jean-Fred (talk) 09:55, 9 January 2018 (UTC)
Ok, I gave this a try: SPARQL quary, CSV export, padding the number to 7 characters in a spreadsheet, slap into Quick Statements:
Q55534 P4705 "0001206"
Q2252569 P4705 "0000004"
Q6116890 P4705 "0004311"
...
QuickStatements does run (« # Processing Q55534 (Q55534 P4705 "0001206") ») but nothing happens :-( Jean-Fred (talk) 11:42, 26 January 2018 (UTC)
- With the help of VIGNERON, I got it working :) All values should now have been updated. After syncing, this is also reflected in the mix'n'match catalogue. Jean-Fred (talk) 12:37, 26 January 2018 (UTC)
- Thanks for the fixes. --Rotpunkt (talk) 18:04, 3 March 2018 (UTC)
P400 constraint
[edit]As many other video game sites, World of Spectrum also lists games that were not really released. The site also contains Timex Sinclair games, books, peripherals... Items may correctly not have P400 = ZX Spectrum --Bultro (talk) 20:57, 5 April 2018 (UTC)
URL match pattern
[edit]I've switched the main URL from "World of Spectrum" to "Spectrum Computing" website, because Spectrum Computing has become much more complete and also includes links to WoS. It did quite some time ago, and also external sites like Lemon64 and CPC-Power switched from linking WoS to linking Spectrum Computing long time ago. Bultro (talk) 15:20, 2 December 2023 (UTC)
- Thanks for posting an explanation on the talk page! I agree with the change. I had been wondering about switching to SpectrumComputing as 'canonical' target too (most recently in Wikidata:Property proposal/Spectrum Computing). The WoS.org / WoS.net schism is also a bit of a problem − I was always wondering whether people might get confused. Thanks :) Jean-Fred (talk) 19:57, 2 December 2023 (UTC)
- All Properties
- Properties with external-id-datatype
- Properties used on 1000+ items
- Properties with format constraints
- Properties with single value constraints
- Properties with unique value constraints
- Properties with constraints on type
- Properties with constraints on items using them
- Properties with entity type constraints
- Properties with scope constraints
- Games properties