Property talk:P5769
Documentation
a publication's editorial leader who has final responsibility for its operations and policies and the selection of authors, translators, illustrators, and formats for publishing articles or books in collections or periodical papers
List of violations of this constraint: Database reports/Constraint violations/P5769#Type Q1002697, Q35127, Q5292, Q277759, Q8513, Q15416, Q1058914, Q1137109, Q96102601, Q2085381, Q3331189, Q23622, Q1320047, Q47461344, Q192283, Q14350, Q1331793, Q3918, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P5769#Value type Q5, Q95074, Q43229, SPARQL
if [item A] has this property (editor-in-chief (P5769)) linked to [item B],
then [item A] and [item B] have to coincide or coexist at some point of history. (Help)
List of violations of this constraint: Database reports/Constraint violations/P5769#Contemporary, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P5769#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P5769#Entity types
List of violations of this constraint: Database reports/Constraint violations/P5769#allowed qualifiers, SPARQL
(Help)
Violations query:
SELECT ?item ?value { ?item wdt:P5769 ?value. FILTER NOT EXISTS { ?value p:P106 [] } FILTER NOT EXISTS { ?value p:P39 [] } FILTER NOT EXISTS { ?value p:P214 [] } FILTER (ISBLANK(?value) = false) }List of this constraint violations: Database reports/Complex constraint violations/P5769#Properties
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Dictionaries[edit]
This should be allowed for dictionary (Q23622), or perhaps its parent, reference work (Q13136). —Michael Z. 2020-12-10 20:37 z 20:37, 10 December 2020 (UTC)
Confusion with director / manager (P1037)[edit]
The label in French "Dirigé par" creates a confusion with the dirigé par(P1037). I think it would be better to replace "dirigé par" with "responsable éditorial".
Notified participants of WikiProject France. What do you think? PAC2 (talk) 08:29, 21 November 2021 (UTC)
- @PAC2: there always could be confusion, but yes
Support for the replacement. Cheers, VIGNERON (talk) 08:33, 21 November 2021 (UTC) - Support more specific, better. GAllegre (talk) 12:02, 21 November 2021 (UTC)
- Support. Nomen ad hoc (talk) 17:19, 21 November 2021 (UTC).
Done It's done PAC2 (talk) 20:36, 23 November 2021 (UTC)
New type constraint[edit]
I suggest adding a new type constrain to this property: for each item that can have an editor-in-chief:
- publisher (Q2085381) (book publisher (Q1320047))
- version, edition or translation (Q3331189)
- dictionary (Q23622)
See the Constraint violations page: for most "bad" items, you can actually be the editor. ((@Daniel Baránek:) Palotabarát (talk) 08:41, 8 January 2022 (UTC)
Gender neutral labels[edit]
Following this request for comments, the French label now includes the male and the female form.
In this case, it could be relevant to use a short form such as "responsable éditorial(e)" or "responsable éditorial·e". I prefer the last one. And you? PAC2 (talk) 20:51, 18 June 2022 (UTC)
Allowed qualifiers constraint[edit]
@Jarnsax: Correct me if I'm wrong, but I understand that before you create an allowed qualifiers constraint (Q21510851) entry for a property, any and all qualifiers are allowed with that property...
When it comes to magazine (Q41298), periodical (Q1002697), and other work (Q386724) item types that are published over a long period of time (such as an encyclopedia (Q5292), a dictionary (Q23622), a map series (Q1734578) or some other series of creative works (Q7725310)), as well as a continuously operating news agency (Q192283) or editorial team (Q24354647), start time (P580) and end time (P582) surely need to be allowed qualifiers for editor (P98), editor-in-chief (P5769), illustrator (P110), contributor to the creative work or subject (P767) and possibly other author-like properties (also suggested by the property stability of property value (P2668) on editor (P98) saying that values can be added (Q23611840) over time as new editors join these teams).
Since the allowed qualifiers constraint is the same regardless of item type, I assume we don't have to enumerate those types, just the relevant properties. Qualifiers start time (P580) and end time (P582) seem to be the most common constraint violations with editor-in-chief (P5769) right now (searching for editor (P98) and illustrator (P110) statements keep timing out for me).
This is hardly an issue with author of foreword (P2679) or author of afterword (P2680), though. SM5POR (talk) 12:52, 16 October 2022 (UTC)
- @SM5POR My intent was not to specifically 'disallow' other qualifiers... I have no issue with people adding other stuff to address constraint violations that come up in how they use it, or 'obvious stuff' that I missed. My set of 'qualifiers' was just intended as a start, and I expected people to add stuff I missed.
- Actually having the qualifiers set, though, makes editing easier (the listed properties show up in the UI) and helps people enter data more consistently. We should probably "generally" set them on things that are widely used, to give people a hint as to how other people are doing it.
- If a specific "use case" is special enough to actually be unique (a legitimate constraint violation) you can use exception to constraint (P2303) to make an exception for the entity you're breaking it on (to make the warning go away).
- It makes it easier for people trying to clean stuff up to locate and check the "edge cases" and see if there was/is a better way to do it, or call it "not an edge case" and add the property to the list.
- By "regardless of item type" I assume what you mean is: regardless of what the entity it's placed on conceptually "is"... is it an instance, a class, a facet, etc. subject type constraint (Q21503250) deals with that by letting you require that some particular statement exist on the entity where you are using the property.
- For instance (I don't remember which, offhand) some of the properties for "identifiers", where the external database isn't English, have a constraint set that complains if you didn't add a label (cut paste it) in that language.
- If you actually "break" one (I mean, the constraint itself is broken or wrong), someone will revert you (which isn't a sign of hostility, here, it's the only way to leave a manual edit summary) and say something like "use this instead".
- ^ This makes adding and "maintaining" the constraints actually 'more useful' in that it draws more eyes to "how you are doing stuff" vs. "how other people are doing stuff" and helps us all get this database consistent.
- Just to made it clear that I agree "start time" and "end time" fall into the 'obvious stuff I missed' category, I went ahead and added them to the "author-like" things you mentioned. Jarnsax (talk) 20:49, 16 October 2022 (UTC)
- Thanks; neither do I object to listing just a few obvious qualifiers as a first approximation, but rather than charge ahead and start "fixing" things to my liking I wanted to bring up the issue for discussion just in case I had overlooked some aspect. By "item type" I was referring to the different classes of items where editor (P98) and the other properties apply, and since the whole range of creative works is a bit fluid I don't see much point in trying to define which kind of works should be allowed to have time-limited editors and which kind should not.
- Also, I don't want to overuse qualifiers; if and when an editorial team is dissolved, that also implies the end of the term of any editor still on that team without the need for an explicit end time (P582) qualifier on each editor's association with the team. Likewise with the author's death, I suppose. Only when both parties in a relationship remain in existence/alive after the relationship has ended do you need to indicate that event (resignation, dismissal etc) with an end time (P582) qualifier. SM5POR (talk) 23:15, 16 October 2022 (UTC)
- All Properties
- Properties with wikibase-item-datatype
- Properties used on 1000+ items
- Properties with constraints on type
- Properties with contemporary constraints
- Properties with scope constraints
- Properties with entity type constraints
- Properties with qualifiers constraints
- Properties with complex constraints