Wikidata:Property proposal/Filceolaire
Wikidata glossary edit
Wikidata glossary entry edit
Originally proposed at Wikidata:Property proposal/Generic
Not done
| Description | description of a concept, feature, term or tool as used for Wikidata (in English) |
|---|---|
| Represents | Project:Glossary (Q1389361) |
| Data type | String |
| Domain | items relevant to a glossary for Wikidata |
| Allowed values | generally 2-3 sentences, maybe 7. Start with term in bold. Formatting should be limited and text readable without the formatting: e.g. bolding ("'''"); anchors to other entries: sample [[#Q123456|crossreference]]. Do not use {{Q}} or {{P}}. |
| Example 1 | Cradle (Q55933452) → '''Cradle''' is an editing tool to create new Wikidata items based on a form with predefined properties and values. |
| Example 2 | Help:Dates (Q87066524) → '''Date''' (or '''time''' or '''timeValue''') is a [[#Q19798645|datatype]] for property values. It allows to enter dates in different precisions and enables date calculations in queries. Hour or minute precision isn't supported. The Wikidata property for the date of foundation ([[Property:P571]]) has such values |
| Example 3 | Wikimedia disambiguation page (Q4167410) → '''Disambiguation item''' is a Wikidata item with sitelinks to disambiguation pages. This is its only purpose. Generally, it has a claim with "instance of" (P31)="Wikimedia disambiguation page" (Q4167410). |
| Planned use |
|
| Expected completeness | eventually complete (Q21873974) |
| See also |
|
Wikidata glossary anchor edit
Originally proposed at Wikidata:Property proposal/Generic
Not done
| Description | unique name of term, concept, tool being described in the glossary entry, including related terms or synonyms |
|---|---|
| Data type | String |
| Template parameter |
|
| Domain | items with property proposed above |
| Allowed values | values should be unique names in English |
| Example 1 | Cradle (Q55933452) → "Cradle" |
| Example 2 | Help:Dates (Q87066524) → "Date" |
| Example 3 | Help:Dates (Q87066524) → "TimeValue" |
| Example 4 | Help:Dates (Q87066524) → "Time" |
| Planned use | avoid duplicate entries and provide stable named links to the glossary. Add unique constraint |
| Number of IDs in source | at least one per entry |
| Expected completeness | eventually complete (Q21873974) |
Wikidata glossary mentioned entries edit
Originally proposed at Wikidata:Property proposal/Generic
Not done
| Description | other glossary entry linked in entry |
|---|---|
| Data type | Item |
| Domain | items with property proposed above including a reference to another entry |
| Allowed values | items with property proposed above |
| Example 1 | Help:Dates (Q87066524) → Wikibase datatype (Q19798645) (see full sample above) |
| Example 2 | MISSING |
| Example 3 | MISSING |
| Planned use | add if applicable |
| Expected completeness | eventually complete (Q21873974) |
| See also |
|
Motivation edit
Some time ago, Filceolaire re-wrote the Wikidata glossary (User:Filceolaire/Draft:Glossary). Given the format of Wikidata:Glossary, only some got included in the glossary. Wikidata:Glossary has changed a bit since, but, in the last two years, it may well be that other users additions are limited to "Lexeme", "Sense", "Form", duplicating what's in another glossary.
So we currently have a page that doesn't seem to be much used (looking at pageviews), updated (looking at edits) or expanded.
Wikidata:Glossary is somewhat hard to maintain:
- Ideally every help page would have at least one short glossary entry associated with it.
- One can't easily find what has or doesn't have an entry.
- Duplication with other glossaries happens.
- The relation to Wikidata items about the described concepts is missing, making it rather unstructured.
- There is a risk of anchor duplication.
- Section editing isn't available.
- Entries may be out of sync from the help page they point to, as editors of the help page may not be aware of the glossary entry.
This proposes a somewhat different, more structured, approach:
- entries are added to items
- similar to scope and content (P7535), we can provide a short specialist written summary
- users could query the items directly with WQS
- users could generate a glossary for their needs on the fly
- to get translations, one will be able to retrieve conveniently named pages like Translations:Wikidata:Glossary/15397819/fr (identified by the number of the QID the entry is on)
- duplication with other glossaries would be less likely
- the value of the property could be displayed on the relevant help page
Other things don't change:
- A page like Wikidata:Glossary could still be generated.
- Translators could still use the translation extension (main advantage of the current format).
- Sample: test list (see Special:Translate)
- It's still the English version that is the primary edition
Editing will be similar:
- Formatting should/might be simpler
- As users edit entries one by one that wouldn't change much.
- To change several at once, one can use TABernacle or a spreadsheet with QS.
- The sample above still needs a link to the edit the underlying item .. or to go through Bridge.
Other ways for some of the above may be possible, but this structured approach has its advantages. Please help complete the above proposal.
Dedicated to Filceolaire (Add your motivation for this property here.) --- Jura 13:45, 27 March 2020 (UTC)
Discussion edit
Comment I'm not sure I completely follow what you're trying to do, but shouldn't the glossary entries be monolingual text rather than string datatype, so that translations can be added also? The glossary as it stands is (in principle) translated into a number of different languages. ArthurPSmith (talk) 17:54, 27 March 2020 (UTC)
- Wikidata glossaries are currently written in English and translated through the Translation Extension. The extension is a convenient way to translate text and keep it in sync (not really efficiently possible with multiple monolingual strings at Wikidata). The more detailed explanation above shows how this wouldn't change with this proposal. The property value is in English, translations can be retrieved from pages like Translations:Wikidata:Glossary/15397819/fr (for an entry on Q15397819). --- Jura 00:27, 28 March 2020 (UTC)
- @Jura1:
Not done Stale proposal. I suggest if you create new proposals for these properties that you label them with their intent; I think people may have avoided commenting here in support or otherwise due to the (honorary) label. ArthurPSmith (talk) 16:55, 11 January 2021 (UTC)
