Property talk:P6366

From Wikidata
Jump to navigation Jump to search

Documentation

Microsoft Academic ID
identifier for an object or topic in the Microsoft Academic Graph (until 31 December 2021)
Applicable "stated in" valueMicrosoft Academic (Q28136779)
Data typeExternal identifier
Domainentity (Q35120)
Allowed values[1-9]\d{3,9}
ExampleDoping silica beyond limits with laser plasma for active photonic materials (Q58420606) → 2206799855 (RDF)
Networks, Complexity and Internet Regulation (Q58622482) → 1498221862 (RDF)
International Conference on Communications (Q6049597) → 1130451194 (RDF)
Paul Emery (Q19859634) → 2144675545 (RDF)
University of Leeds (Q503424) → 130828816 (RDF)
Goethe University Frankfurt (Q50662) → 114090438 (RDF)
Massachusetts Institute of Technology (Q49108) → 63966007 (RDF)
IBM (Q37156) → 1341412227 (RDF)
Computational analysis of deposition and translocation of inhaled nicotine and acrolein in the human body with e-cigarette puffing topographies (Q58132177) → 2792937454 (RDF)
Nature (Q180445) → 137773608 (RDF)
lupus nephritis (Q1621830) → 2779912601 (RDF)
Formatter URLhttps://web.archive.org/web/*/https://academic.microsoft.com/v2/detail/$1
Related to country United States of America (Q30) (See 761 others)
See alsocurriculum vitae URL (P8214), OpenAlex ID (P10283)
Lists
Proposal discussionProposal discussion
Current uses
Total280,884
Main statement280,606>99.9% of uses
Qualifier12<0.1% of uses
Reference266<0.1% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Single value: this property generally contains a single value. (Help)
Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: anthrax lethal factor endopeptidase (Q4773866), demersal (Q2734949)
List of violations of this constraint: Database reports/Constraint violations/P6366#Single value, SPARQL
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).
List of violations of this constraint: Database reports/Constraint violations/P6366#Unique value, SPARQL (every item), SPARQL (by value)
Format “[1-9]\d{3,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/P6366#Format, SPARQL
Conflicts with “instance of (P31): Wikimedia category (Q4167836), Wikimedia disambiguation page (Q4167410)”: 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/P6366#Conflicts with P31, SPARQL
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/P6366#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/P6366#Entity types
Type “entity (Q35120)”: item must contain property “instance of (P31), subclass of (P279)” with classes “entity (Q35120)” or their subclasses (defined using subclass of (P279)). (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/P6366#Type Q35120, SPARQL
This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

MAG Data Access[edit]

Volumetrics

Microsoft Relational dump:

University of Freiburg: MAG as RDF

Open Academic Graph:

  • https://www.openacademic.ai/oag/, dump in simple json format. Integrates the following:
  • 166M papers from Microsoft Academic Graph (MAG): snapshot of 2017-06-09 (MAG is updated weekly). 104GB
  • 154M papers from Arnet Miner: snapshot of 2017-03-22. 39GB
  • 64M common (linking relations) with 99.7% precision. 1.6GB

Microsoft Graph API:

--Vladimir Alexiev (talk) 08:55, 18 January 2019 (UTC)[reply]

@Vladimir Alexiev: I have uploaded ids for institutions by matching them using the GRID ID (P2427) provided in http://ma-graph.org/ (https://tools.wmflabs.org/editgroups/b/OR/59c3cc81/), but Jklamo noticed that this GRID mapping is not always reliable − sometimes they picked the GRID ids of national subsidiaries of international companies. I am fixing this now. − Pintoch (talk) 14:10, 20 January 2019 (UTC)[reply]

Duplicates[edit]

Many IDs are now being added to chemical substances and I see a lot of duplicates in Microsoft Academic website, e.g. [1], [2]. Both are in one item lead(II) chromate (Q367871). What should be done about it as we have single-value constraint (Q19474404) constraint here? Is it possible to mark two entries in Microsoft Academic as duplicates and maybe MS Academic staff would merge them? Or maybe we should deprecate one ID? Add an item as exception to constraint (P2303)? Pinging Nikola Tulechki as I see you're currently adding many IDs via QS. Wostr (talk) 13:52, 13 February 2020 (UTC)[reply]

@Wostr: IMHO the best option regarding the example you give is the merge the items at the MAG end. Given that I am currently importing all the 230K FOS from the latest MAG dump through the Wikipedia links, I suggest that we wait until the import finishes and produce a report with which to engage the MAG people. This way we can also incite them to add direct mapping to Wikidata on their app in complement of (or instead of) the Wikipedia links they currently have. Nikola Tulechki (talk) 14:08, 14 February 2020 (UTC)[reply]
Constraint violation reports will be generated automatically and can serve as lists of duplicates fir MAG staff to merge. So please don't add Exception to constraint. --Vladimir Alexiev (talk) 14:37, 14 February 2020 (UTC)[reply]
It cannot serve as a duplicate list without checking the list first. There are situations like this (from my watchlist from today):
  1. Some IDs are not functional: cholesteryl ester (Q415555) with [3] and [4] (which redirects to the home page)
  2. Some IDs are not 1:1 equivalents of the WD items, like in D-mannopyranose (Q335208): [5] and [6] – there are many such situations, the last should be probably in mannose metabolic process (Q21121642). I don't know what is the scale of that issue (everyday I see at least several cases like this only on my watchlist), but it seems it would require much effort to correctly map these to the WD items, before it would be possible to have a list of real duplicates.
Wostr (talk) 17:17, 14 February 2020 (UTC)[reply]
  • Okay, as all the IDs are imported now, how to deal with (real) duplicates? With over 9k violations of 'single value' constraint it's not possible to leave them as they are, because it will disrupt checking the constraint violations list (on which there are not only real duplicates but also IDs that are not equivalent to WD items). Maybe using deprecated rank for one ID with duplicate entry (Q1263068) as a reason for deprecation? Or using mapping relation type (P4390)? Or maybe MS Academic staff could check our list of constraint violations, merge the IDs on their end and provide a list of merged IDs? Wostr (talk) 20:14, 24 June 2020 (UTC)[reply]
@Wostr: Actually I think the single value constraint should be removed because the entries at Microsoft are not checked for aliases themselves. They just take strings and make them entries. --SCIdude (talk) 08:10, 2 September 2020 (UTC)[reply]

Microsoft Academic Website: No longer accessible after Dec. 31, 2021[edit]

Microsoft have announced that they will be retiring this service: [7]. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:00, 14 May 2021 (UTC)[reply]

This has now come to pass. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:28, 1 January 2022 (UTC)[reply]

Worth noting here that while the MAG project is retired, openalex has effectively continued the project, under a new more permissive license (CC Zero). In particular, Openalex was seeded with the MAG metadata, using the same old MAG integer identifiers, and there is a related wikidata property for Openalex IDs (https://www.wikidata.org/wiki/Property:P10283). One difference is that Openalex IDs have a letter prefix (like 'W' for works), which the MAG identifiers did not, so you need to know the entity type to map from old MAG identifiers to new Openalex identifiers. Blnewbold (talk) 01:20, 13 September 2022 (UTC)[reply]

formatter url not available[edit]

Apparently this doesn't work on archive.org (see discussion on project chat and properties for deletion). Accordingly I deprecated the formatter url. --- Jura 14:49, 7 January 2022 (UTC)[reply]

Just as an update for posterity: Those discussions have been archived and are located here: Project chat/Archive/2022/01 and Properties for deletion/Archive/2022/2. – desoda (T | C) 19:04, 26 December 2022 (UTC)[reply]
Retrieved from "https://www.wikidata.org/w/index.php?title=Property_talk:P6366&oldid=1963328637"