Property talk:P1323

Documentation

Terminologia Anatomica 98 ID
Terminologia Anatomica (1998 edition) human anatomical terminology identifier

Description

Terminologia Anatomica (1998 edition) identifier. Unique identifier for human anatomical terminology.

Applicable "stated in" value

Terminologia Anatomica (Q286567)

Data type

External identifier

Template parameter

"TA98" in en:Template:infobox bone, en:Template:infobox brain, en:Template:infobox muscle.

Domain

According to this template: elements (parts) of the human body

According to statements in the property:
anatomical entity (Q27043950) or activity of anatomical entity (Q96482377)

When possible, data should only be stored as statements

Allowed values

A\d{2}\.\d\.\d{2}\.\d{3}[FM]? (letter 'A' followed by 8 numbers, separated by 3 dots)

Example

tibia (Q178366) → A02.5.06.001
human heart (Q2419844) → A12.1.00.001

Source

https://www.unifr.ch/ifaa/Public/EntryPage/ViewTAOnLine.html
https://www.unifr.ch/ifaa/Public/EntryPage/TA98%20Tree/Alpha/All%20KWIC%20EN.htm

Formatter URL

https://wikidata-externalid-url.toolforge.org/?p=1323&url_prefix=https:%2F%2Fwww.unifr.ch%2Fifaa%2FPublic%2FEntryPage%2FTA98%20Tree%2FEntity%20TA98%20EN%2F&url_suffix=%20Entity%20TA98%20EN.htm&id=$1

Tracking: usage

Category:Pages using Wikidata property P1323 (Q26697454)

See also

TA98 Latin term (P3982), TA2 ID (P7173), Terminologia Embryologica (P1693), Terminologia Histologica (P1694), Foundational Model of Anatomy ID (P1402)

Lists

Proposal discussion

Current uses

Total	5,247
Main statement	5,239 out of 7,444 (70% complete)	99.8% of uses
Qualifier	4	<0.1% of uses
Reference	4	<0.1% of uses

Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Format “A\d\d\.\d\.\d\d\.\d\d\d[FM]?”: 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/P1323#Format, 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/P1323#Unique value, 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/P1323#Single value, SPARQL

Type “anatomical entity (Q27043950), activity of anatomical entity (Q96482377)”: item must contain property “subclass of (P279)” with classes “anatomical entity (Q27043950), activity of anatomical entity (Q96482377)” 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/P1323#Type Q27043950, Q96482377, SPARQL

Item “TA98 Latin term (P3982)”: Items with this property should also have “TA98 Latin term (P3982)”. (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/P1323#Item P3982, 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/P1323#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/P1323#Scope, SPARQL

Pattern ^(\d\d\.\d\.\d\d\.\d\d\d)$ will be automatically replaced to A\1.
Testing: TODO list

This property is being used by:

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

Link syntax

Thank you for editing. Today, I realized that current links to TA Online seems not working. For example, ear (Q7362) has TA statements A01.1.00.005.

And its external link is as follows (this doesn't work)

http://www.unifr.ch/ifaa/Public/EntryPage/TA98%20Tree/Entity%20TA98%20EN/A01.1.00.005%20Entity%20TA98%20EN.htm

Actually the link should be as follows (without "A" shown in red at above. This works.)

http://www.unifr.ch/ifaa/Public/EntryPage/TA98%20Tree/Entity%20TA98%20EN/01.1.00.005%20Entity%20TA98%20EN.htm

Though I don't know how and at where the link settings are stored in Wikidata. In English Wikipedia, deletion of "A" is done by the code like this (see w:en:Template:TA98)

{{Str right|{{{1}}}|1}}

Thank you for reading.--Was a bee (talk) 06:53, 3 August 2014 (UTC)[reply]

@Was a bee: - The links are stored here: MediaWiki:Gadget-AuthorityControl.js - I will see if anyone knows how to remove the "A". -Tobias1984 (talk) 08:10, 3 August 2014 (UTC)[reply]

@Tobias1984: Any luck on the 'A' problem? BoH (talk) 15:29, 4 August 2015 (UTC)[reply]

@BoH: The formatter-URL is now stored in the statements of each property. If removing the A does not work we could also let a bot remove all the 'A's from the beginning of the strings. If every string starts with an 'A', we don't really need to store that. --Tobias1984 (talk) 16:50, 4 August 2015 (UTC)[reply]

@Tobias1984:, we should be able to just replicate what is done for P628. there, they strip off the leading 'E'. if you look in MediaWiki:Gadget-AuthorityControl.js there you will see the following lines for P628:

	case 628: // E Number
		linkValue = value.substring( 1, 16 ); // Skip initial letter
		break;

for this property, the same trick should work

	case 1323: // TA98
		linkValue = value.substring( 1, 16 ); // Skip initial letter
		break;

not exactly sure why they are using "16" for the maximum substring length, but if that works for P628, it should work here as well. Frietjes (talk) 17:04, 4 August 2015 (UTC)[reply]

@Frietjes: I didn't know about that! Thanks for already submitting the fix! --Tobias1984 (talk) 18:30, 4 August 2015 (UTC)[reply]

Thanks Frietjes! BoH (talk) 19:22, 4 August 2015 (UTC)[reply]

Multiple values

Some anatomy parts have more than one TA98 property. For example "ear" has one code in the category "Parts of human body" (A01.1.00.005) and in the category "Olfactory organ"(A15.3.00.001). So what do you think about allowing multiple values for this property? --Stiegenaufgang (talk) 07:42, 7 August 2014 (UTC)[reply]

@Stiegenaufgang: I think it is better to add the TA98-id to the specific items and use queries for other items. A query for "all TA98-IDs that are used for the ear" has to look for all the items that are "part of --> ear" and gather the IDs from those items. -Tobias1984 (talk) 08:00, 7 August 2014 (UTC)[reply]

@Stiegenaufgang, Tobias1984:. Today multiple TA-ID became available nicely in English Wikipedia (:en:Module_talk:Wikidata). I think it is OK and good adding all TAID to each page. As a background information, Terminologia Anatomica is not "tree like" ontology (like Foundational Model of Anatomy) rather a dictionary, which tries to list all terms in certain order. And certain organ appears multiple times in different context (means has multiple TAIDs). --Was a bee (talk) 02:59, 22 September 2014 (UTC)[reply]

See article Ear in English Wikipedia. You can see how multiple TAIDs are shown in articles. --Was a bee (talk) 03:02, 22 September 2014 (UTC)[reply]

@Was a bee: I think that is a good way of handling the TA IDs for a start. More problematic are for example the ICD codes in items like cancer (Q12078) Adding all the values is quite an effort and a lot of duplicates. Plus it messes a with the constraint violations. -Tobias1984 (talk) 11:07, 22 September 2014 (UTC)[reply]

@Tobias1984: Wow... I didn't know such case. At least TA IDs are not so many. I know some double TA IDs, but I have not yet seen triple TA IDs. (Surely that ICD codes are too many. I suppose value format like 'C00-C97' would be, perhaps, nice. Because their website affords such type of URL links [1] But this is another topic.) --Was a bee (talk) 07:50, 23 September 2014 (UTC)[reply]

Strange formatter URL

I'm not used to seeing a formatter URL (P1630) starting with http://tools.wmflabs.org/wikidata-externalid-url/?p=1323&url_prefix= then containing an encoded version of the external URL, in this case https:%2F%2Fwww.unifr.ch%2Fifaa%2FPublic%2FEntryPage%2FTA98%20Tree%2FEntity%20TA98%20EN%2F&url_suffix=%20Entity%20TA98%20EN.htm&id=$1. Why not just use the non-encoded URL? The regular external link was originally added by @KrBot, Ivan A. Krestinin: in Dec 2014, and then @ArthurPSmith: added the wmflabs prefix in June 2016. What are the pros & cons of doing this, and which one is preferred? —Tom.Reding (talk) 17:17, 25 November 2018 (UTC)[reply]

@Tom.Reding: I don't remember the details of this specific case, but generally the external-id redirector is added because the default Wikidata external id interpretation fails in some way. In particular it does not handle url-encoded terms in an id correctly, so that may be the problem here. ArthurPSmith (talk) 16:56, 26 November 2018 (UTC)[reply]

Property talk:P1323

Contents

Documentation

Link syntax

Multiple values

Strange formatter URL

Navigation menu