Property talk:P8532
Documentation
identifier of a papyrus or an epigraphic text on Tresmegistos
List of violations of this constraint: Database reports/Constraint violations/P8532#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P8532#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P8532#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P8532#Type Q87167, Q1640824, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P8532#Entity types
List of violations of this constraint: Database reports/Constraint violations/P8532#Scope, SPARQL
Domain "written work", should be "manuscript" and "inscription"[edit]
As of now, this property has a subject type constraint to class written work (Q47461344). This does not comply with the nature of the Trismegistos database nor its use on Wikidata. The text IDs refer to exemplars, not works. Accordingly the constraint should be for instances of manuscript (Q87167) and inscription (Q1640824).
Notified participants of WikiProject Antiquity: What do you think? Jonathan Groß (talk) 09:26, 6 October 2023 (UTC)
- Support, I agree of course. --Epìdosis 09:28, 6 October 2023 (UTC)
- As long as these two are the only possible types, I support DerHexer (talk) 09:32, 6 October 2023 (UTC)
- Support --Jahl de Vautban (talk) 16:50, 6 October 2023 (UTC)
Thanks for the prompt feedback, guys! I'll go ahead then as proposed. Jonathan Groß (talk) 07:53, 7 October 2023 (UTC)
- Has this change been implemented? If so, the description should be updated, eg "identifier of a manuscript (papyrus, codex, fragment, palimpsest) or an inscription on Tresmegistos.org". atb CRolker (talk) 13:47, 15 May 2024 (UTC)
Add exceptions to 'distinct-value constraint' or remove constraint[edit]
Hello! For the work I'm doing for Wikidata:WikiProject IDEA I am experiencing an issue with the distinct-value constraint.
Trismegistos assigns text IDs according to its own specific criteria (which can be found on their how-to-cite page) which don't necessarily match how texts are identified elsewhere. As they note here, their text IDs are sometimes associated with multiple items on other sites.
For our project, the issue arises from discrepancies between the Trismegistos ID and the individual items catalogued by the Beinecke. The items we have created for the Dura-Europos papyri were based on inventory numbers in the Beinecke and sometimes fragments that were published together have separate inventory numbers, but only one Trismegistos ID - we therefore have multiple items sharing the same TM text id which are currently in violation of this constraint (as you can see here in the constraint violation report, there are 6 items with this issue).
I would like to either add an exception to constraint (P2303) qualifer listing these specific exceptions, or to propose that the constraint is removed, since it could become an issue again in the future as more manuscripts and inscriptions are added to Wikidata. JASHough (talk) 16:16, 24 February 2024 (UTC)
Notified participants of WikiProject Antiquity
Notified participants of WikiProject IDEA JASHough (talk) 16:16, 24 February 2024 (UTC)
- All Properties
- Properties with external-id-datatype
- Properties used on 100+ items
- Properties with format constraints
- Properties with unique value constraints
- Properties with single value constraints
- Properties with constraints on type
- Properties with entity type constraints
- Properties with scope constraints
- Archive WikiProjects