Hello Dhx1; Thanks for creating this. Looking for images on commons, I was wondering if a category or any reference tho this weather station should be in capitals. Thank you so much for your time.
User talk:Dhx1
Jump to navigation
Jump to search
The capitalised names are just coming from the source data (BoM weather station location list). I suspect it's not a hard and fast rule or standard, and it may be best to use title case instead for Wikidata labels.
If it helps, http://www.bom.gov.au/clim_data/cdio/metadata/pdf/siteinfo/IDCJMD0040.071003.SiteInfo.pdf (an alternative formatter URL for Bureau of Meteorology station ID (P3796)) has a diagram showing the location of where this weather station used to exist, seemingly between the bottom of Pulpit T-Bar and Spencers Creek (which is near the access road to Charlotte Pass ski resort).
I think I found it on https://commons.wikimedia.org/wiki/File:Charlotte_Pass_2008.jpg and have tagged the weather station as the small post in between Spencers Creek and Basin Poma (not visible in this picture)
You recently duplicated statements from powoduje (P1542) to występujące zagrożenie (P3335) . Both statements currently exist in items. Perhaps it would be a good idea to remove one of them?
Hi @Wostr
associated hazard (P3335) is a subclass of sorts of has effect (P1542) in that it describes a human safety/environmental damage effect involving the item that may occur in part due to the item, but is an effect not guaranteed nor necessarily likely to occur.
has effect (P1542) I think expects the effect to always occur as there are currently no listed allowed qualifiers that allow this always to be changed to may.
For example, swimming (Q6388) has effect (P1542) drowning (Q506616) implies that if you swim you will drown. swimming (Q6388) associated hazard (P3335) drowning (Q506616) on the other hand states that if you swim, you should be aware of the risk of drowning, even though it is an effect of rare incidence.
That's why it seems to me that these changes have been halfway completed. I agree that występujące zagrożenie (P3335) is better here, but the presence of both statements seems to be unnecessary.
See https://www.iana.org/assignments/ipv6-address-space/ipv6-address-space.xhtml for the mention of the IPv6 prefix. It is not mentioned within the RFC itself, but instead the prefix references the RFC.
Shouldn't the prefix be added to the RFC page then? What's the correct way to add this to wikidata?
I've just reverted https://www.wikidata.org/w/index.php?title=Q31856&diff=prev&oldid=2015239330 - presumably a script error? There's no way you should be adding 3.8MB of data to a single authority control ID! Thanks. Mike Peel (talk) 07:21, 29 January 2024 (UTC)
Can you please try to reduce the number of GenBank assembly accession number (P4333) statements on Q31856, Q140010, and Q310543? All three are currently among the 70 biggest Wikidata items. This makes it difficult to work with them and causes problems on Commons.
I think GenBank assembly accession number (P4333) should probably be changed so that it can only be used on genome assembly (Q55433859) (I think?), and cannot be used directly on taxon (Q16521)? And then there could be 100,000 genome assembly (Q55433859) for a single taxon (Q16521), linked via genome assembly (Q55433859) found in taxon (P703) taxon (Q16521). If this sounds correct I can propose the change to GenBank assembly accession number (P4333) so that there aren't 100,000 statements on a given taxon. There are quite a few taxons with no many genomic assemblies, they can't be added to Wikidata as the page size for the taxon item exceeds the maximum limit.
Hi Dhx1,
Jq (Q28801607) and Jq (Q115959735) are meddled together. Maybe I can pass the torch to somebody in another timezone and go to bed now?
Done :)
Hello,
You have set to withdrawn several education property proposal from Andrews Lartey. FYI Wikidata:Property proposal/ISCED-ALevel has not been commented by anybody and is not included in the main proposal page.
Thank you for proposing this Identifier. I just saw it in Wikidata weekly summary #543. I've noted my support for this proposal and tweeted to Wikimedia Australia as the Ping had not worked, or at least I didn't notice it. Hopefully, that will draw more response. ~~~~
Thank you @Oronsay:. I'm not sure why the project ping didn't work this time.
Hi Dhx1,
I noticed that the links in the properties JECFA database ID (P4852) and JMPR database ID (P4853), whose creation you had suggested, do not work anymore. Could you please have a look?
Thanks @Leyo: the link rot is impacting other property JECFA number (P9557) as well. It looks like all three properties had formatter or source URIs that are now dead, and seemingly don't have equivalent databases replacing them. JECFA number (P9557) is not a database identifier (an ID that is largely useless when the database dies) but rather a number similar to CAS Registry Number (P231) that is used and referred to elsewhere.
I have marked the old URIs as dead (link rot) and updated property descriptions to make it clear the properties are for former identification schemes.
It seems that links in the following form do work:
Could you please check, if this also applies to you?
Perfect, thanks for finding that new page! I've updated JECFA database ID (P4852) to use the new URL structure. The property lives on!
Thanks for updating! Could you please also have another look at JMPR database ID (P4853)? The original URLs seem to work again.
I have reset JECFA database ID (P4852) back to original state as the URLs are working again for JMPR. Thanks!
Hi, it seems your bot is living 1 day in the future… Could you please fix this?
Thanks for the heads up. I have fixed the problem at https://github.com/davidhicks/RfcBot/commit/900af95e95c784e106ee34c9f2fb8c01f1a99b92 so it won't have the off-by-1-day problem in the future.