Wikidata:Property proposal/Clavis Historicorum Antiquitatis Posterioris author ID

Clavis Historicorum Antiquitatis Posterioris author ID edit

Originally proposed at Wikidata:Property proposal/Authority control

Descriptionauthor identifier in the Clavis Historicorum Antiquitatis Posterioris database
Data typeExternal identifier
Domainitem
Allowed values\d{1,3}
Example 1Gaius Asinius Quadratus (Q563283)CHAP ID1
Example 2Ablabius (Q322053)CHAP ID100
Example 3Gildas (Q352995)CHAP ID500
Sourcehttps://www.late-antique-historiography.ugent.be/
Planned useassociation through the corresponding Mix'n'Match catalog
Number of IDs in source824
Expected completenesseventually complete (Q21873974)
Implied notabilityWikidata property for an identifier that suggests notability (Q62589316)
Formatter URLhttps://www.late-antique-historiography.ugent.be/database/authors/$1/
See alsoTrismegistos author ID (P11252), where it is used as external ID
Applicable "stated in"-valueClavis Historicorum Antiquitatis Posterioris (Q87125491)
Single-value constraintyes
Distinct-values constraintyes
Wikidata projectWikiProject Ancient Rome (Q6337458), WikiProject Ancient Greece (Q6497946)

Motivation edit

  Notified participants of WikiProject Ancient Rome

  Notified participants of WikiProject Ancient Greece

This database is specialised in late antique historians, who don't get much love nor interest anywhere else. With more than 800 IDs, it is extensive and cover names (with aliases), dates, confession and works. It is already used by Trismegistos author ID (P11252) among other IDs, so we'd be well inspired to do the same. As it cover also a lot of anonymous authors, it will also be useful to create items for them and more generally it will increase Wikidata strengh in covering ancient authors. --Jahl de Vautban (talk) 12:06, 16 April 2023 (UTC)[reply]

Discussion edit

@Jahl de Vautban, Epìdosis, Tolanor, DerHexer, Marcus Cyron, JBradyK:   Done Clavis Historicorum Antiquitatis Posterioris author ID (P11790) Midleading (talk) 02:34, 17 May 2023 (UTC)[reply]