Property talk:P1055

From Wikidata
Jump to navigation Jump to search

Documentation

NLM Unique ID
identifier in the catalog of the National Library of Medicine
DescriptionCatalog of the United States National Library of Medicine (Q611833).
Associated itemUnited States National Library of Medicine (Q611833)
Applicable "stated in" valueNational Library of Medicine classification (Q986957)
Data typeExternal identifier
Domaincreative work (note: this should be moved to the property statements)
Allowed values\d{6,19}(A|R|\d)
ExampleThe Journal of the American Medical Association (Q1470970)7501160
Radiochimica Acta (Q2126419)0050556
Sourceexternal reference, Wikipedia list article (either infobox or source) (note: this information should be moved to a property statement; use property source website for the property (P1896))
Formatter URLhttps://catalog.nlm.nih.gov/discovery/search?vid=01NLM_INST:01NLM_INST&query=lds04,exact,$1
Tracking: usageCategory:Pages using Wikidata property P1055 (Q55923208)
Lists
Proposal discussionProposal discussion
Current uses
Total35,930
Main statement35,71199.4% of uses
Qualifier2<0.1% of uses
Reference2170.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/P1055#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)
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).
List of violations of this constraint: Database reports/Constraint violations/P1055#Single value, SPARQL
Format “\d{6,8}(A|R|\d): value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P1055#Format, hourly updated report, 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/P1055#Item P31, hourly updated report, search, 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/P1055#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/P1055#Scope, SPARQL


A couple of questions about this property[edit]

Hi, I am new to Wikidata. I work as a contractor for the NLM, so this property caught my eye. I have a couple of questions.

  • Why was it changed to string? AFAIK, these identifiers are integers. I'm not 100% sure of that, but I could check. Wouldn't it be better to have the datatype match, if, in fact, these are integers?
  • Is there guidance anywhere on how this should be discovered / used, other than the JAMA example? If not, where would just documentation usually go? Here on the talk page? If it would be worthwhile, I could write some.
  • I see that the domain is "creative work", and I'm wondering if that's right. JAMA is a journal, which is a container of creative works, but is it a creative work itself? Sorry if that's a dumb question.
  • Related to that, where, on the The Journal of the American Medical Association (Q1470970) page, can I find that this item is a "creative work"? Is there an "is-a" property, that points to a class? If so, I can't find it.

Thanks! Klortho (talk) 05:35, 22 December 2013 (UTC)[reply]

Klortho: I'm not sure if I'm 100% correct on some things, but this is what I think:
  • On bullet one, the property is using the string datatype so that it can later (thanks to the software) point to the URL of the NCBI, as shown on The Journal of the American Medical Association (Q1470970). This wouldn't be possible using the integer datatype, apart from the fact that we don't have yet an integer datatype available. Also, a FYI, the datatype of a property cannot be changed.
  • On bullet two: Well, actually you can add this property to any item which has such an ID. I have no idea which items need this property (I guess you could find it using the National Library of Medicine registry, just like you find a song's writer on the liner notes). About a proper documentation, I think that the box atop this page is such thing.
  • On bullet three: The domain was an internal classification used on Wikidata, now deprecated, named "main type" (P107 (P107)). The domain of the property was specified as to belong to one of the "types" (creative work, term, etc) in relation to that property. Since the property's fate was decided on an RfC, it doesn't matter anymore.
  • Since the main type property (P107 (P107)) is to be deleted, another property (instance of (P31)) is the one who takes over. This other property is way more flexible (for example, at The Journal of the American Medical Association (Q1470970), it would be instance of = journal).
Hope this helps. — ΛΧΣ21 07:01, 22 December 2013 (UTC)[reply]
Hi, thanks for the responses! Unfortunately, they just leave me with more questions:
  • Are you saying that the value of this property for JAMA is "[http://www.ncbi.nlm.nih.gov/nlmcatalog/7501160 7501160]"? If so, why don't I see it that way when I click "edit" on the JAMA page? There, I just see the integer value. Where is the URL template rule (how to turn the integer into a URL) stored? Is *that* editable?
  • If "Domain: creative work" is meaningless, why is it still in the documentation template? Can I take it out? I think, old and deprecated information should be cleaned up whenever possible.
  • So, is there any formal way to code the domain of a property according to instance of (P31)? For example, any way to specify that the domain of this property must be a *journal*?
I am thinking I will also leave some of these questions on Wikidata:Project_chat.
Thanks again!
Klortho (talk) 07:19, 22 December 2013 (UTC)[reply]

Change in formatter URL[edit]

I just changed the formatter URL as it was selective only for certain types of NLM entries. For example, Q19561861 wouldn't have worked, despite that the NLM ID was correct. The new one also searches the NLM catalog directory, rather than via the NCBI. I checked on multiple different files to be sure that it works before changing it. Of note, the query doesn't run correctly if all those arguments aren't there. It may look busy, but it is a library search. Hazmat2 (talk) 18:28, 12 March 2015 (UTC)[reply]

Noticed that the formatter URL was changed to one that didn't work for many of the IDs, so I checked the site and the catalog is still using the old search function so I reverted it back. Rehua (talk) 01:38, 13 June 2019 (UTC)[reply]
@Rehua: @Hazmat2: Note that https://www.ncbi.nlm.nih.gov/nlmcatalog/9422792, for example, is not identical with https://locatorplus.gov/cgi-bin/Pwebrecon.cgi?v2=1&ti=1,1&SEQ=20190925031111&Search%5FArg=9422792&Search%5FCode=0359&CNT=25&PID=Lsj0-1SSUUeHM8ZLDwQvsk&SID=1 which is the detailed view option (rather than the default summary view). The NCBI version has additional fields, such as Publication Start Year for inception (P571), Country of Publication for country of origin (P495) and Coden for CODEN (P1159). So even if people know to go to the detailed view, they are not getting the best data at present. Charles Matthews (talk) 07:31, 25 September 2019 (UTC)[reply]

NLM new catalog 2021[edit]

NLM has moved to a new catalog and all of these links will stop working soon as LocatorPlus is phased out of use. I have updated the formatter URL and format of regular expression to direct people to the new catalog through Primo. I wanted to explain the change here for anyone who was curious. Pullen255 (talk) 18:12, 11 August 2021 (UTC)[reply]