Wikidata:Property proposal/TNHR&CE Temple ID

From Wikidata
Jump to navigation Jump to search

TNHR&CE Temple ID[edit]

Originally proposed at Wikidata:Property proposal/Place

Descriptionidentifier for temples, mutts, charitable endowments and specific endowments supervising by TNHR&CE
Data typeExternal identifier
Domaininstance or subclass of (Q30208840) : Hindu temple (Q842402) : Jain temple (Q2613100), Matha (Q2069741) (Mutt), Charitable Endowments (we don't have any specific item for it), Specific Endowments (we don't have specific any item for it) financial endowment (Q2620430)
Example 1Kapaleeshwarar Temple (Q1587164) → TM000001
Example 2Trilokyanatha Temple (Q26833741) → TM002710
Example 3Embar Jeeyar Mutt (Q124621722) → TM003452
Sourcehttps://hrce.tn.gov.in/hrcehome/temples_search.php?activity=temple_search
Number of IDs in sourceWithout endowments: 43,761
With endowments: 46,153

Motivation[edit]

The Goverment of Tamil Nadu (Q1445) Hindu Religious and Charitable Endowments Department supervising Temples and other Hindu and Jain religious buildings in Tamil Nadu. This IDs helps identify the Wikidata items of temples and mutts maintaining by Hindu Religious and Charitable Endowments Department (Q12974460). This contains Hindu temples, Jain temples and mutts, Additionally contains Charitable Endowments and Specific Endowments. We don't have much Endowments (for Tamil Nadu) items in Wikidata, So I think this not compulsory to include in the property, But I would like add this in the proposal. Thank you --Sriveenkat|talk/{PING ME} 17:36, 20 February 2024 (UTC)[reply]

Discussion[edit]

 Comment: Data type is correct. If there is no suitable/working formatter url, properties with the external identifier data type may not have one, see RCS number (P12321) or CRAB ID (P11406) as an example. Regards Kirilloparma (talk) 01:52, 4 March 2024 (UTC)[reply]
@Sriveenkat, ArthurPSmith, Kirilloparma: datatype should be 'string' instead of 'external-id'. See the examples PyPI trove classifier (P12468), Parpulov group (P12110), software version identifier (P348), HomoloGene ID (P593). Regards, ZI Jony (Talk)
No, it shouldn't. I have already explained that external identifier properties may not necessarily have a formatter URL. The properties you provided as an example are not external identifiers, probably except for HomoloGene ID (P593). Why P593 was originally created as a string is a question for its creator, who also created this property in violation, since you can't create your own properties.
Back to our case. If you create this property with string data type (which you certainly should not do), you will be challenged for this choice and the property will most likely be converted (here) from a string data type to an external ID sooner or later.
P.S. By the way we have exactly the same situation with another property marked as ready, but please don't tell me that it is also not an external identifier and there should be a string there... Regards Kirilloparma (talk) 14:30, 4 March 2024 (UTC)[reply]
@Kirilloparma, @ZI Jony We have without formatter URL External identifiers about India : Kerala state school code (P7065), ‎SEC Kerala code (P11817), Based on this identifiers I made this property proposal. Sriveenkat|talk/{PING ME} 17:38, 4 March 2024 (UTC)[reply]
@Sriveenkat: Well, yeah, that's exactly what I'm talking about, but another property creator thinks that the data type should be string and idk why. A great example of a string property is rating certificate ID (P2676) but certainly not this one. Regards Kirilloparma (talk) 01:00, 5 March 2024 (UTC)[reply]
This certainly seems like an identifier to me, it's not a classification string. Datatype is fine. ArthurPSmith (talk) 17:57, 4 March 2024 (UTC)[reply]
@Sriveenkat, ArthurPSmith, Kirilloparma: thanks for your clarification, I just want to make sure that I do the correct thing before creating the property. Regards, ZI Jony (Talk) 13:04, 5 March 2024 (UTC)[reply]