Wikidata:Property proposal/MeSH qualifier ID
MeSH qualifier ID edit
Originally proposed at Wikidata:Property proposal/Authority control
| Description | identifier of a MeSH (Medical Subject Headings) qualifier |
|---|---|
| Represents | Medical Subject Headings (Q199897) |
| Data type | External identifier |
| Domain | item; medicine (Q11190) |
| Allowed values | Q[0-9]{6} |
| Example 1 | epidemiology (Q133805) → Q000453 (MeSH Browser), Q000453 (MeSH RDF) |
| Example 2 | surgery (Q40821) → Q000601 (MeSH Browser), Q000601 (MeSH RDF) |
| Example 3 | mortality rate (Q58702) → Q000401 (MeSH Browser), Q000401 (MeSH RDF) |
| Example 4 | anatomy (Q514) → Q000033 (MeSH Browser), Q000033 (MeSH RDF) |
| Example 5 | histology (Q7168) → Q000033 (MeSH Browser), Q000033 (MeSH RDF) |
| Example 6 | cerebrospinal fluid (Q54196) → Q000134 (MeSH Browser), Q000134 (MeSH RDF) |
| Example 7 | prevention (Q13466133) → MESH Qualifier Q000517 (MeSH Browser), Q000517 (MeSH RDF) |
| Example 8 | violence prevention (Q104733130) → MESH Descriptor D014754, qualified by MESH Qualifier Q000517 |
| Source | https://meshb.nlm.nih.gov/search (MeSH Browser) and https://id.nlm.nih.gov/mesh/ (MeSH RDF) |
| Planned use | will add to medical topics as encountered |
| Number of IDs in source | 79 |
| Expected completeness | eventually complete (Q21873974) |
| Formatter URL | https://meshb.nlm.nih.gov/record/ui?ui=$1 (MeSH Browser) and http://id.nlm.nih.gov/mesh/$1 (MeSH RDF) |
| See also | MeSH descriptor ID (P486), MeSH concept ID (P6694), MeSH term ID (P6680), MeSH tree code (P672) and proposal MeSH descriptor/qualifier ID |
| Applicable "stated in"-value | Medical Subject Headings (Q199897) |
| Distinct-values constraint | no; some qualifiers cover two or more separate concepts, e.g. Q000033: anatomy & histology |
Motivation edit
MeSH qualifiers are the one MeSH controlled vocabulary that do not yet have a Wikidata property. These qualifiers are used in cataloging and indexing to further refine a subject by combining a MeSH descriptor with a qualifier. UWashPrincipalCataloger (talk) 20:58, 28 February 2021 (UTC)
Discussion edit
Support but you should probably use formatter URI for RDF resource (P1921) for the RDF links, and have the regular formatter URL provide the web links. ArthurPSmith (talk) 19:23, 1 March 2021 (UTC)
- @ArthurPSmith: Thanks for the suggestion. There doesn't seem to be a way to put formatter URI for RDF resource (P1921) into the proposal itself as a separate formatter property, so this would just have to be added to the property once it is created, right? UWashPrincipalCataloger (talk) 20:27, 1 March 2021 (UTC)
- Yes, I think so. ArthurPSmith (talk) 21:50, 1 March 2021 (UTC)
- @ArthurPSmith: Thanks for the suggestion. There doesn't seem to be a way to put formatter URI for RDF resource (P1921) into the proposal itself as a separate formatter property, so this would just have to be added to the property once it is created, right? UWashPrincipalCataloger (talk) 20:27, 1 March 2021 (UTC)
- Support Thank you for setting this page up! Should we add in the description the best practice suggestion about the URIs also being included? Also, can we note that it can be used as a Qualifier for MeSH descriptor ID (P486)? Not really sure how all of this works yet, so we might not be able to add these yet. Pullen255 (talk) 11:54, 2 March 2021 (UTC)
- Support EJPlantz (talk) 14:18, 2 March 2021 (UTC)
- Support
- Should be usable both as main statement and as qualifier, see last 2 examples
- @UWashPrincipalCataloger, ArthurPSmith, Pullen255, EJPlantz: Let's also vote for Property_talk:P486#MeSH_descriptors_+_qualifiers --Vladimir Alexiev (talk) 19:31, 6 March 2021 (UTC)
- @Vladimir Alexiev: Were you referring to MeSH_descriptor/qualifier_ID? UWashPrincipalCataloger (talk) 20:18, 6 March 2021 (UTC)
