Wikidata:Property proposal/Arachne entity ID
Arachne entity ID
[edit]Originally proposed at Wikidata:Property proposal/Authority control
Description | identifier for an entity in the archaeological database Arachne |
---|---|
Represents | Arachne (Q624540) |
Data type | External identifier |
Allowed values | [1-9]\d* |
Example 1 | Athens (Q1524) → 770 |
Example 2 | Temple of Hera, Olympia (Q633572) → 5607 |
Example 3 | Archaeological Museum of Thessaloniki (Q2658285) → 1241674 |
Example 4 | Venus de Milo (Q151952) → 1074675 |
Source | https://arachne.dainst.org/ |
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]. |
Planned use | convert present values from Arachne building ID (P6787), Arachne collection ID (P7020), Arachne object ID (P7021) (probably to be deleted); then slow manual match; eventually maybe Mix'n'match |
Number of IDs in source | 4621488 (growing) |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://arachne.dainst.org/entity/$1 |
Applicable "stated in"-value | Arachne (Q624540) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Wikidata project | Archaeology |
Motivation
[edit]Notified participants of WikiProject Archaeology Back in 2019 we started the connection to Arachne (Q624540), one of the most important existing archaeological databases, through Arachne building ID (P6787) (proposed by @Alexmar983:), Arachne collection ID (P7020) and Arachne object ID (P7021) (proposed by @Christelle Molinié:); in fact, the uses of these properties have remained significantly low (fewer than 400 in total) and in the meanwhile Arachne has undergone a significant renewal from https://arachne.uni-koeln.de/arachne/ to https://arachne.dainst.org/, so the old IDs are still working but link to an obsolete version of the database; the API of the new database allow converting the old IDs into the new one, which has the positive effect of unifying all the parts of the database (buildings, collections, objects etc.) into one single entity ID. I thus propose to create the new ID, convert the old ones and then delete the old properties. I thank @JBradyK: for informing me about this important renewal of Arachne, which opens new interesting perspectives for more intense connection with Wikidata. Epìdosis 14:06, 9 March 2022 (UTC)
Discussion
[edit]- Strong support - more than one time I've tried to link to Arachne. In the moment, this is, even with all problems it has, the most important database of ancient greaco-roman art in the world. All linkable possibilities shoul be used here. -- Marcus Cyron (talk) 14:32, 9 March 2022 (UTC)
- Strong support - Very rich on Greek collections, buildings, and artwork, and I will work to capture them... JBradyK (ToposText) (talk) 14:49, 9 March 2022 (UTC)
- Strong support - very rich and would provide ideal integration to other parts of the DAI-linked data ecosystem... Amalaswintha08 (talk) 20:07, 9 March 2022 (UTC)
- Strong support ; Comment what will happen of the previous properties ? --Jahl de Vautban (talk) 20:54, 9 March 2022 (UTC)
- @Jahl de Vautban: In my opinion they should be deleted (after their values have been converted into this new property), but this will be discussed afterwards. --Epìdosis 11:43, 10 March 2022 (UTC)
- Support - PKM (talk) 00:20, 10 March 2022 (UTC)
- Strong support --Fthierygeo (talk) 10:08, 10 March 2022 (UTC)
- Strong support --Awmees (talk) 11:14, 10 March 2022 (UTC)
- Strong support - of course we must adapt to the evolution of Arachne --Christelle Molinié (talk) 18:06, 10 March 2022 (UTC)
- Strong support —MasterRus21thCentury (talk) 06:24, 13 March 2022 (UTC)
- Strong support - I'm planning on using links to Arachne for a large set of Aegean seals; Comment IMHO the 'old' Arachne IDs were intended to be permanent and I would not remove them until they really don't work anymore. It seems that the old ID is included in the current database as Old serial number (Alte Seriennummer), see e.g. CMS XII 087 with 'old' Arachne IDs 167798 & 167799 and new Arachne IDs 1160613 & 1160614. This example also shows that in Arachne one object is not necessarily one physical object and it might be worthwile to lift the restriction of only applying one Arachne ID to an item in Wikidata. Mtrognitz (talk) 12:54, 15 March 2022 (UTC)
- To distinguish the old from the new IDs the major version numbers (3 and 4 respectively, see About - Technology) of Arachne could be used. Mtrognitz (talk) 12:56, 15 March 2022 (UTC)
- @Epìdosis, Marcus Cyron, JBradyK, Amalaswintha08, Jahl de Vautban, PKM: @Fthierygeo, Awmees, Christelle Molinié, MasterRus21thCentury, Mtrognitz: Notified participants of WikiProject Archaeology Done as Arachne entity ID (P10510).UWashPrincipalCataloger (talk) 20:37, 18 March 2022 (UTC)