Property talk:P4517
Documentation
identifier for a work, in the ctext database. ctext is a database of pre-modern texts in Chinese languages (works and editions have separate identifiers)
Description | identifier for a work, in the ctext database. ctext is a database of pre-modern texts in Chinese languages. Works and editions have separate identifiers. | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Associated item | Chinese Text Project (Q5100670) | |||||||||
Applicable "stated in" value | Chinese Text Project (Q5100670) | |||||||||
Data type | External identifier | |||||||||
Domain | According to this template:
works
According to statements in the property:
When possible, data should only be stored as statementswritten work (Q47461344) | |||||||||
Allowed values | ctp:work:[-a-z\d]+ | |||||||||
Example | According to this template:
Analects (Q276015) → analects
According to statements in the property:
When possible, data should only be stored as statementsAnalects (Q276015) → ctp:work:analects Shuowen Jiezi (Q1072348) → ctp:work:shuo-wen-jie-zi | |||||||||
Source | http://ctext.org/ (note: this information should be moved to a property statement; use property source website for the property (P1896)) | |||||||||
External links | Use in sister projects: [ar] • [de] • [en] • [es] • [fr] • [he] • [it] • [ja] • [ko] • [nl] • [pl] • [pt] • [ru] • [sv] • [vi] • [zh] • [commons] • [species] • [wd] • [en.wikt] • [fr.wikt]. | |||||||||
Formatter URL | https://ctext.org/searchbooks.pl?if=en&searchu=$1 https://ctext.org/searchbooks.pl?if=gb&searchu=$1 | |||||||||
Related to country | People's Republic of China (Q148) (See 128 others) | |||||||||
See also | ctext data entity ID (P9613) | |||||||||
Lists |
| |||||||||
Proposal discussion | Proposal discussion | |||||||||
Current uses |
| |||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P4517#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4517#Type Q47461344, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4517#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P4517#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P4517#Entity types
List of violations of this constraint: Database reports/Constraint violations/P4517#Scope, SPARQL
Identifiers and formatter URL
[edit]The ctext system and API uses CTP URNs to refer to textual objects including particular editions of a work, and worksets with corresponding work URNs to refer to all editions of a particular work. I would suggest using the work URNs as the most relevant and stable identifiers, and using the following formatter URL to transform e.g. the work URN ctp:work:huangdi-neijing into the URL http://ctext.org/searchbooks.pl?if=en&searchu=ctp:work:huangdi-neijing listing all editions of that work: http://ctext.org/searchbooks.pl?if=en&searchu=$1 D.sturgeon (talk) 23:26, 14 November 2017 (UTC)
- @D.sturgeon: You can actually edit the formatter URL yourself. The URL is a statement on each property. You can find it in the user interface by going to the property-page (ctext work ID (P4517)) and edit the formatter URL statement (one of the boxes at the bottom of the page). How about using http://ctext.org/searchbooks.pl?if=en&searchu=ctp:work:$1 or is double prefix useful? --Tobias1984 (talk) 10:38, 17 November 2017 (UTC)
- @Tobias1984: Thanks Tobias. Yes, I did find the location and realized that in principle I should be able to edit it myself, but in practice because my account is new I cannot do this as attempting to do so gets me a "Disallow new editors from changing formatter URL" error - so if someone else could make this change for me that would be very helpful. The main motivation for including the "ctp:work:" prefix is that the complete identifiers including this part are used in many other contexts (e.g. can be searched directly within the ctext.org user interface, used to load textual objects into other tools, etc.), and so it seems to me preferable to use the complete meaningful and well-defined identifiers rather than removing the prefix and recording something new and potentially ambiguous. There are also ctext URNs that do not begin with "ctp:work:", but they refer to different objects, and it is generally the case that if there exists an identifier "ctp:work:xxxx", there will also exist a corresponding identifier "ctp:xxxx", though these conceptually refer to quite different things. So I think it would be less confusing to include the prefix, particularly as in contrast to the initial examples, the majority of URNs are not human readable (e.g. "ctp:work:wb601464"). D.sturgeon (talk) 13:53, 17 November 2017 (UTC)
- @D.sturgeon: I changed the formatter URL now and changed the values that I added so far. --Tobias1984 (talk) 13:49, 18 November 2017 (UTC)
如何获取ID?
[edit]我发现Q30007056对应的标识符不符合 正则表达式,但在www.ctext.org 又找不到对应的标识符,请教一下,是如何找到对应原本的标识符?--Bangbang.S 01:27, 26 February 2022 (UTC)
- People's Republic of China-related properties
- All Properties
- Properties with external-id-datatype
- Properties used on 100+ items
- Properties with format constraints
- Properties with constraints on type
- Properties with single value constraints
- Properties with unique value constraints
- Properties with entity type constraints
- Properties with scope constraints
- China-related properties