Wikidata:Property proposal/Authority control
Property proposal: | Generic | Authority control | Person | Organization |
Creative work | Place | Sports | Sister projects | |
Transportation | Natural science | Computing | Lexeme |
See also Edit
- Wikidata:Property proposal/Pending – properties which have been approved but which are on hold waiting for the appropriate datatype to be made available
- Wikidata:Properties for deletion – proposals for the deletion of properties
- Wikidata:External identifiers – statements to add when creating properties for external IDs
- Wikidata:Lexicographical data – information and discussion about lexicographic data on Wikidata
This page is for the proposal of new properties.
Before proposing a property
- Search if the property already exists.
- Search if the property has already been proposed.
- Check if you can give a similar label and definition as an existing Wikipedia infobox parameter, or if it can be matched to an infobox, to or from which data can be transferred automatically.
- Select the right datatype for the property.
- Read Wikidata:Creating a property proposal for guidelines you should follow when proposing your property.
- Start writing the documentation based on the preload form below by editing the two templates at the top of the page to add proposal details.
Creating the property
- Once consensus is reached, change status=ready on the template, to attract the attention of a property creator.
- Creation can be done 1 week after the creation of the proposal, by a property creator or an administrator.
- See property creation policy.
![]() |
On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2023/09. |
Encyclopedia Edit
AARoads Wiki page ID Edit
Description | numeric identifier of an article on the AARoads Wiki |
---|---|
Represents | AARoads Wiki (Q122452106) |
Data type | External identifier |
Domain | road (Q34442), road (Q34442), road transport term (Q122618571) |
Example 1 | U.S. Route 66 in Arizona (Q807338)→45338 |
Example 2 | Ontario Highway 402 (Q2872843)→51271 |
Example 3 | Iowa Highway 118 (Q122619427)→72106 |
Example 4 | Asotin County roads (Q122277478)→71325 |
Example 5 | Arizona Parkways, Historic and Scenic Roads (Q122619526)→61013 |
Source | https://wiki.aaroads.com/wiki/Special:AllPages |
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 | Import statements for existing articles and develop a gadget on the AARoads Wiki that makes it easier to access the linked Wikidata item |
Number of IDs in source | 15,224 and counting |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://wiki.aaroads.com/w/index.php?curid=$1 |
Robot and gadget jobs | Ideally someone would write a bot to keep these statements in sync with the AARoads Wiki |
See also | SABRE wiki ID (P11000) |
Applicable "stated in"-value | AARoads Wiki (Q122452106) |
Wikidata project | WikiProject U.S. Roads (Q1890587), WikiProject Canada Roads (Q21829688) |
Mục đích Edit
Members of WikiProject U.S. Roads (Q1890587) and WikiProject Canada Roads (Q21829688) recently forked the English Wikipedia's coverage of their subject area, setting up the AARoads Wiki (Q122452106) as an independent wiki. While the bulk of the content currently mirrors the English Wikipedia, they are continuing to develop articles about North American roads on the new wiki, including creating articles on subjects that easily meet Wikidata:Notability and the notability guidelines of various non-English Wikipedias but not those of the English Wikipedia.
Members of the local OpenStreetMap (Q936) community have expressed interest in linking their content, which also goes beyond English Wikipedia notability standards, to AARoads Wiki articles. Since OSM already links to Wikidata items (and vice versa), it would be more efficient to use Wikidata as a hub to get to AARoads Wiki content.
There's been some debate in the past about whether external references to MediaWiki wikis should be typed as strings (article titles) or numbers (page IDs). In this proposal, I've gone with page IDs for stability across page moves. The AARoads community is currently revisiting the article naming conventions they arrived at on the English Wikipedia many years ago, which could result in a significant number of page moves. For readability, I'm suggesting the use of subject named as (P1810) qualifiers to indicate page titles, but I would consider this optional.
– Minh Nguyễn 💬 20:40, 16 September 2023 (UTC)
Discussion Edit
Support --Rschen7754 21:01, 16 September 2023 (UTC)
Support—Imzadi 1979 → 03:10, 18 September 2023 (UTC)
Support Mike Linksvayer (talk) 15:08, 18 September 2023 (UTC)
Support TCN7JM 23:56, 18 September 2023 (UTC)
Library Edit
National Library of Colombia authority ID Edit
Description | numerical identifier for a person in the authority file of the National Library of Colombia (Q2901472) |
---|---|
Represents | no label (Q120198151) |
Data type | External identifier |
Domain | human (Q5) |
Allowed values | [1-9]\d* |
Example 1 | José María Salazar (Q114232578) → 91142 |
Example 2 | Manuel Pombo (Q98768265) → 77847 |
Example 3 | José Vicente Castro Silva (Q105651707) → 29603 |
Example 4 | José Camacho Carrizosa (Q106561769) → 24905 |
Source | https://autoridades.bibliotecanacional.gov.co/ |
Planned use | Mix'n'match (ready) |
Number of IDs in source | 124857 (growing) |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://autoridades.bibliotecanacional.gov.co/cgi-bin/koha/opac-authoritiesdetail.pl?marc=1&authid=$1 |
See also | BNMM authority ID (P3788), National Library of Chile ID (P7369) |
Applicable "stated in"-value | no label (Q120198151) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Wikidata project | Authority control |
Motivation Edit
Notified participants of WikiProject Authority control highly authoritative source for the coverage of Colombian authors. --Epìdosis 18:05, 2 July 2023 (UTC)
Discussion Edit
Support --Kolja21 (talk) 19:09, 2 July 2023 (UTC)
Support - PKM (talk) 19:55, 2 July 2023 (UTC)
Support -- Bargioni 🗣 20:59, 2 July 2023 (UTC)
Support --Uomovariabile (talk) 09:16, 6 July 2023 (UTC)
Support -- Jason.nlw (talk) 12:47, 6 July 2023 (UTC)
Support -- Silva Selva (talk) 23:24, 9 July 2023 (UTC)
Support Atakhanli (talk) 20:47, 19 August 2023 (UTC)
Comment I thank you @Kolja21, PKM, Uomovariabile, Jason.nlw, Silva Selva:. In these days, while revising the Mix'n'match catalog with @Bargioni:, we unfortunately discovered that this website seems to be somehow outdated: a new one exists and it has 253765 entries (more than double of the 124857 entries in this one), but unfortunately this new authority file doesn't offer good URIs for the authority records. The fact that is website is older is a just deduction, because we didn't find any explicit statement of its obsolescence; ideally, if someone is able to contact the National Library, having their confirmation about the relationship between these two websites would be the best way to have a clear picture of the situation. As of now, I put the property "on hold". --Epìdosis 07:28, 10 July 2023 (UTC)
- I contacted the library. They will improve their authority records. So let's wait. Bargioni 🗣 15:50, 23 July 2023 (UTC)
Law Edit
Register Edit
register in Germany Edit
Description | register located in Germany |
---|---|
Data type | Item |
Domain | items with instance of Registration court (Q2138576) (for modelling the German companies) and possibly other classes for other registers |
Example 1 | BASF (Q9401) → Local Court Ludwigshafen (Q480859) |
Example 2 | National Research Data Infrastructure (Q61658497) → Local Court Mannheim (Q480871) |
Example 3 | Air Berlin (Q156829) → Local Court Charlottenburg (Q480608) |
Example 4 | ISC Mannheim (Q1654576) → Local Court Mannheim (Q480871) |
Planned use | First, adding them as qualifiers to German companies together with the properties "identifier in a register in Germany" and "type of a register in Germany" |
Wikidata project | Wikidata:WikiProject_Authority_control |
Motivation Edit
This property should be used together with Wikidata:Property_proposal/type_of_register as qualifiers to a statement with Wikidata:Property proposal/identifier in a register. I've described examples with the same identifiers (and different registers and types of registers) in the discussion at Wikidata:Property_proposal/type_of_register:
- Maas Beteiligungsgesellschaft mbH is registered at "register in Germany" Local Court Hamburg (Q480732) with the "type of a register in Germany" Section B of the Commercial Register (Q110609503) and "identifier in a register in Germany" 47394.
- MIA.Ticket & Merch OHG is registered at Local Court Charlottenburg (Q480608) with Section A of the Commercial Register (Q110609501) and 47394.
- Fanfarenzug Tilleda e.V. is registered at Local Court Stendal (Q15783176) with register of associations (Q110619518) and 47394
As mentioned in the discussion at Wikidata:Property_proposal/type_of_register, these properties are not limited to registers related to organizations. See all types of registers at https://www.xrepository.de/api/xrepository/urn:xoev-de:xjustiz:codeliste:gds.registerzeichen_3.1/download/GDS.Registerzeichen_3.1.md. RShigapov (talk)
Discussion Edit
Support,
Notified participants of WikiProject Germany —MasterRus21thCentury (talk) 06:24, 13 March 2022 (UTC)
Support, an important property for Germany.--Arbnos (talk) 20:20, 23 April 2022 (UTC)
- @RShigapov: Your intended use depends on Wikidata:Property proposal/identifier in a register, but I don't see that being created soon. Would this property serve any purpose without the associated "identifier" (it seems to me it could be useful as a main statement rather than a qualifier). ArthurPSmith (talk) 15:25, 16 June 2022 (UTC)
- It depends on our agreement regarding modelling these three properties together. We could in principle add this property as a main statement with qualifiers "identifier" and "code of register". By the way, may be it makes also sense to rename this property to "registration authority in Germany". Registration authorities in Germany can host multiple registers which we describe via "type of register in Germany" RShigapov (talk) 13:13, 23 June 2022 (UTC)
Oppose Hi @RShigapov:! I commented at the end of https://www.wikidata.org/wiki/Wikidata:Property_proposal/type_of_register with 3 objections. Taking your first example, I'd reformat it as follows:
- Maas Beteiligungsgesellschaft mbH has identifier "47394"; with qualifiers "type of identifier" Section B of the Commercial Register (Q110609503) and "registry (aka "issuer" aka "registrationn authority") Local Court Hamburg (Q480732)
- Or if we use the existing props "catalog code" and "catalog" (where "identifier" and "registry" are added as aliases of these props:
- Maas Beteiligungsgesellschaft mbH catalog code "47394"; with qualifiers "type of identifier" Section B of the Commercial Register (Q110609503) and "catalog" Local Court Hamburg (Q480732)
- As you see, in both variants there's no mention of Germany. The same phenomenon happens in many countries (for many RAL IDs), not just in Germany --Vladimir Alexiev (talk) 14:47, 23 September 2022 (UTC)
- @RShigapov: It feels to me like the present property description of "register located in Germany" is not helpful for people who want to understand what the property does. Please provide a more detailed description.
Comment @RShigapov: Seems to me it's better to use a German company ID that reflects both the court and identifier within that court. See how OpenCorporates have done it: https://opencorporates.com/companies/de?q=air+berlin&type=companies&utf8=%E2%9C%93 shows IDs like this one: https://opencorporates.com/companies/de/F1103R_HRB183145 --Vladimir Alexiev (talk) 11:19, 23 June 2023 (UTC)
Oppose Seems like that would be a sub-property of issued by (P2378). Although nice for constraints, I still prefer using the super-property. --Nw520 (talk) 13:48, 2 September 2023 (UTC)
French trademark registry entry number Edit
Description | identifier for a trade mark registered in France |
---|---|
Data type | External identifier |
Domain | trademark (Q167270) |
Allowed values | (FR|EM)\d+ |
Example 1 | Tropico (Q16681299) → FR1535804 |
Example 2 | Hygiaphone (Q3143844) → FR1498691 |
Example 3 | Vico (Q3556968) → FR99774555 |
Example 4 | COCA-COLA (Q111097379) → FR1054448 |
Example 5 | COCA-COLA (Q111097379) → FR1094094 |
Source | https://data.inpi.fr/ |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://data.inpi.fr/marques/$1 |
See also | Australian Trade Mark Number (P10120), U.S. trademark serial number (P10482) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Wikidata project | WikiProject France (Q10816832) |
Motivation Edit
Le numéro d'inscription est l'identifiant officiel d'une marque française inscrite au Registre national des marques tenu par l'INPI. Son utilisation permettra d'étendre et de fiabiliser nos informations sur les marques.
Notified participants of WikiProject France : Le numéro d'inscription pour les marques pourra avoir un usage équivalent au numéro SIREN pour les entreprises.
- @Lectrician1, Nepalicoi, MasterRus21thCentury: : This is the equivalent of Wikidata:Property proposal/US trademark serial number for France.
Arpyia (talk) 09:46, 30 July 2022 (UTC)
Discussion Edit
Comment @Arpyia: le lien semble cassé. Et quand je fais une recherche dans l'interface avec l'identifiant "1535804" j'ai deux résultats, un FR1535804 (Tropico) et un WO1535804 (Zero Heroes), il faudrait peut-être intégrer le préfixe dans l'identifiant non ? PS: tu as laissé de nombreux champs non remplis dans la demande, notamment le format de l'URL ou ce que tu comptes faire de cette propriété, pourrais-tu les remplir ? Enfin https://w.wiki/5WyH ne renvoie que 114 résultats (dont en plus un grand nombre où la marque et l'entreprise sont confondus visiblement). Cdlt, VIGNERON (talk) 09:58, 30 July 2022 (UTC)
Comment is this database free and compatible with Wikidata? https://data.inpi.fr/content/editorial/mentions_legales states « Sont notamment interdites l'extraction et la réutilisation, quantitativement ou qualitativement substantielles, du contenu des bases de données contenues sur ce site Internet. » (In particular, the extraction and reuse, quantitatively or qualitatively substantial, of the content of the databases contained on this website are prohibited.) VIGNERON (talk) 10:00, 30 July 2022 (UTC)
Support Property proposal updated with missing fields: domain, allowed values regex, source URI, more examples, see also (related properties), English description, etc. – The preceding unsigned comment was added by Dhx1 (talk • contribs) at 23:43, 13 novembre 2022 (UTC).
Question Why are there two entries for "COCA-COLA"? Otherwise this looks fine to me. ArthurPSmith (talk) 19:28, 21 November 2022 (UTC)
- @Arpyia, Dhx1: is there a reason this property is named "French trademark registry entry number" and not "French trademark registry ID". ID is how we typically name our external ID properties unless there are reasons to do otherwise. The label is already long as it is. ChristianKl ❪✉❫ 18:35, 7 December 2022 (UTC)
- Bonjour, thank you for your interest in this property. « Dès sa réception à l'Institut national de la propriété industrielle, le dépôt donne lieu à l'attribution d'un numéro national. Lorsqu'il n'a pu être mentionné sur le récépissé du dépôt, ce numéro est notifié au déposant. » https://www.legifrance.gouv.fr/codes/section_lc/LEGITEXT000006069414/LEGISCTA000006146391/ See also https://data.inpi.fr/recherche_avancee/marques Arpyia (talk) 20:02, 7 December 2022 (UTC)
- @Arpyia, Dhx1: is there a reason this property is named "French trademark registry entry number" and not "French trademark registry ID". ID is how we typically name our external ID properties unless there are reasons to do otherwise. The label is already long as it is. ChristianKl ❪✉❫ 18:35, 7 December 2022 (UTC)
RCS number Edit
Description | identifier in the trade register of Luxembourg |
---|---|
Represents | RCS number (Q121298042) |
Data type | External identifier |
Domain | organization (Q43229) |
Allowed values | [A-Z][0-9]+ |
Example 1 | ArcelorMittal (Q27893) → B82454 |
Example 2 | SES S.A. (Q333025) → B81267 |
Example 3 | Luxembourg Basketball Federation (Q3741114) → F2301 |
Source | https://www.lbr.lu/mjrcs/jsp/DisplayConsultDocumentsActionNotSecured.action |
Number of IDs in source | 158023 (2022) |
See also | Norwegian organisation number (P2333), Enterprise number (Belgium) (P3376) |
Motivation Edit
This number is used to identify all organizations in the trade register of Luxembourg. --1-Byte (talk) 09:18, 8 August 2023 (UTC)
Discussion Edit
Notified participants of WikiProject Authority control
Notified participants of WikiProject Companies
Social networking service Edit
Stage Edit
Description | Link to the account from a German authority on the social media platform Stage (https://stage.bio) |
---|---|
Data type | External identifier |
Example 1 | Baden-Württemberg (Q985) → baden-wuerttemberg |
Example 2 | Baden-Baden (Q4100) → baden-baden |
Example 3 | Heidelberg (Q2966) → heidelberg |
Motivation Edit
English: In Germany exists a social media platform called Stage. Only German authorities may create an account. Stage imports content from social media platforms (e.g. Twitter, Facebook, Instagram …) centrally in Stage. Users can see all content from different platforms as a summary centrally on the Stage account from an authority.
German: Mit dem Eigenschaftsnamen Stage soll ein Link zur neuen deutschen Social-Media-Plattform Stage generiert werden. Bei Stage können sich Behörden Profile zulegen, bei denen Nutzer sämtliche Inhalte der gängigen Social-Media-Plattformen, bei denen eine Behörde ein Profil hat, anzeigen lassen kann.
Discussion Edit
Sessionize speaker ID Edit
Description | URL slug of the person's speaker profile on Sessionize |
---|---|
Represents | Sessionize (Q117525230) |
Data type | External identifier |
Domain | item, human (Q5) |
Example 1 | Emery David Berger (Q102317400)Sessionize speaker IDemery-berger |
Example 2 | Simon Thompson (Q57606204)Sessionize speaker IDsimon-thompson |
Example 3 | Brian L. Gorman (Q116897512)Sessionize speaker IDbrian-gorman |
Example 4 | Helen Lavretsky (Q61072164)Sessionize speaker IDhelen-lavretsky |
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 | Add to some existing items about conference speakers |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://sessionize.com/$1/ |
See also | participant (P710), speaker (P823), participant in (P1344) |
Applicable "stated in"-value | Sessionize (Q117525230) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Mục đích Edit
Sessionize is an abstract management system for conferences (for their calls for papers). Users who submit session proposals through the site can optionally enable a publicly accessible speaker profile. This profile is useful for corroborating a person’s claimed participation in a conference, though it isn’t authoritative, more like a social networking profile. The user can optionally list the Sessionize-managed events that they have or will attend, as well as the specific sessions that they have or will present. The user can add external events, as well as sessions that have not been submitted to a Sessionize-managed event; these events and sessions are indistinguishable from Sessionize-managed ones. The profile’s URL is intentionally discoverable via a URL slug, which the user can customize at any time. Sessionize identifies each user more durably by their e-mail address, which is kept private, making the URL slug the most suitable identifier for statements about Sessionize users. – Minh Nguyễn 💬 09:18, 11 April 2023 (UTC)
Discussion Edit
Comment I'd suggest a shorter name. Perhaps just "Sessionize speaker ID"? --99of9 (talk) 05:17, 8 August 2023 (UTC)
- @99of9: OK, done. – Minh Nguyễn 💬 22:03, 24 August 2023 (UTC)
WhatsApp channel Edit
Description | item's channel on WhatsApp |
---|---|
Represents | WhatsApp (Q1049511) |
Data type | External identifier |
Example 1 | The Straits Times (Q498921) → 0029VZzIPtoFXUuS8frj520t (linked from official website [1]) |
Example 2 | CNA (Q40238) → 0029VZzLRrhC6Zvj21eniB12 (linked from official website [2]) |
Example 3 | Ukraine (Q212) → 0029VZzb5gV77qVXJHJHaK1S (linked from verified Instagram account [3]) |
See also | Discord invite ID (P9078) & Telegram username (P3789) |
Motivation Edit
Similar to Telegram channel. This feature currently available in 9 countries and will expand to other countries. Hddty (talk) 06:12, 27 July 2023 (UTC)
Discussion Edit
Support I was about to suggest: https://imgur.com/q4LfOnx --Devrim ilhan (talk) 16:59, 23 September 2023 (UTC)
Magazine Edit
Latindex 2022 ID Edit
Description | Latindex ID from 2022 |
---|---|
Represents | Wikidata property for authority control for academic journals (Q57589544) |
Data type | External identifier |
Domain | periodical (Q1002697) |
Allowed values | numbers |
Example 1 | Bulletin Hispanique (Q23739791) → 3239 |
Example 2 | Acta Biologica Venezuelica (Q3229252) → 208 |
Example 3 | Avances en Química (Q24935648) → 1963 |
Planned use | replace Latindex ID (P3127) (to deprecate) |
Implied notability | Wikidata property for an identifier that suggests notability (Q62589316) |
Formatter URL | https://www.latindex.org/latindex/ficha/$1 |
See also | Latindex ID (P3127) (to deprecate) |
Motivation Edit
Apparently in last April, the Latindex Portal (https://latindex.org/latindex/) changed its whole indexing system. Not only the url scheme, but also the identifiers themselves, without any redirection. Moreover, the new identifiers remain simple integers, so the old regexp remains valid and we have no way to distinguish between old and new identifiers.
In Wikidata, Latindex ID (P3127) has been updated for the url scheme formatter URL (P1630), but no update made for the identifiers. So, Wikidata now provides false links. For example, Nuevo Mundo, Mundos Nuevos (Q3346085) links to https://www.latindex.org/latindex/ficha/15703 instead of https://www.latindex.org/latindex/ficha/11055. The big deal is the confusion between old and new identifiers (numbers) if we update the current property, so I think the only solution is to create a new one, then slightly fix and deprecate Latindex ID (P3127).
FYI, a colleague of mine fixed the Mir@bel database (https://reseau-mirabel.info/) using the Latindex API. I plan to do the same if we create the new property.
- Retrieve the JSON data from the export of advanced research with no criteria (~15 MB) : https://www.latindex.org/latindex/exportar/busquedaAvanzada/json/%7B%22idMod%22:%220%22%7D.
- For each json block, retrieve the numeric identifier and ISSNs (ISSN-E and ISSN-P) as the external key. GAllegre (talk) 17:46, 17 September 2022 (UTC)
Discussion Edit
- what a disaster. i suppose this is the right way to fix this. can we set the old format url to an internet archive link for some past date? BrokenSegue (talk) 03:48, 26 October 2022 (UTC)
Authority file Edit
- See also wikidata:property proposal/Pending for approved items awaiting the deployment of currently unavailable datatypes
- Already approved properties: list
IdnaMapping Edit
Description | technical regulations for mapping according to Internationalizing Domain Names in Applications (IDNA), see |
---|---|
Represents | IdnaMapping (Q115434932) |
Data type | Item |
Domain | Q29654788 |
Allowed values | hypothetically (Q18603603), replacement (Q23009439), "disallowed_STD3_valid", "disallowed_STD3_mapped", "disallowed", "deviation", "ignored |
Example 1 | A (Q87496158) → replacement (Q23009439) (Qualifier should provide a (Q87496268)) |
Example 2 | a (Q87496268) → hypothetically (Q18603603) |
Example 3 | ß (Q87496914) → (new object "deviation", Qualifier should provide "ss") |
Example 4 | ˘ (Q87498208) → (new object "disallowed_STD3_mapped") |
Example 5 | [ (Q87496254) → (new object "disallowed_STD3_valid") --> |
Expected completeness | eventually complete (Q21873974) |
Motivation Edit
URLs should be evaluated and later automatically recoded if necessary Vollbracht (talk) 18:23, 25 November 2022 (UTC)
Discussion Edit
Specialities and qualifications classification code (Belarus) Edit
Description | specialty and qualification identifier according to OKRB 011-2022 |
---|---|
Represents | Specialities and qualifications (OKRB 011-2022) (Q113355971) |
Data type | External identifier |
Domain | academic discipline (Q11862829), academic major (Q4671286) |
Allowed values | \d-\d{2}-\d{4}-\d{2}(-\d{2})? |
Example 1 | software engineering (Q80993) → 6-05-0612-01 |
Example 2 | composed musical work (Q207628) → 7-07-0215-02 |
Example 3 | endocrinology (Q162606) → 9-09-0911-65 |
Example 4 | veterinary medicine (Q170201) → 5-04-0841-01 |
Example 5 | foreign-language pedagogy (Q2696615) → 7-06-0231-01 |
Source | [5] |
Number of IDs in source | 1555 |
Expected completeness | eventually complete (Q21873974) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation Edit
Adding a code field to link an academic discipline to the standardised one in the Republic of Belarus. Each academic discipline in Belarus has a standard code assigned by the Ministry of Education. The complete list of codes is available at the National Legal Internet Portal Aestrum (talk) 13:55, 19 October 2022 (UTC)
Discussion Edit
Notified participants of WikiProject Authority control —Aestrum (talk) 14:31, 24 October 2022 (UTC)
WikiProject Properties has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead. —Aestrum (talk) 14:31, 24 October 2022 (UTC)
Support —MasterRus21thCentury (talk) 13:04, 2 November 2022 (UTC)
- @Laftp0: Given that this property has no English description it does not feel ready. ChristianKl ❪✉❫ 14:50, 20 January 2023 (UTC)
- @ChristianKl Currently, I have translated into three languages - Russian, Belarusian and English. MasterRus21thCentury (talk) 17:11, 20 January 2023 (UTC)
Support classification system for academia in belarus. looks fine to me. Infrastruktur (talk) 23:33, 12 March 2023 (UTC)
Wait The current name seems to be very long and there's no justification for why the name is supposed to be so long in the motivation section. "OKRB 011-2022 code" would be shorter and better fit into most places where property names are displayed. ChristianKl ❪✉❫ 12:14, 19 March 2023 (UTC)
Jiten Online kanji ID Edit
Motivation Edit
Jiten Online is a Japanese online dictionary. It has a large amount of kanji data sometimes including hanzi or hanja. – The preceding unsigned comment was added by Laftp0 (talk • contribs).
Discussion Edit
Comment Do you know what the different prefixes signify? I.e. is there a systematic difference between
,kanjiy
, etc.? --Nw520 (talk) 09:55, 25 November 2022 (UTC)kanjib
- It just seems to move to next alphabet every 500 entries like 001~500 is "kanji" and 501~1000 is "kanjib". But it doesn't move from "kanjiy" which has more than 15000 entries. Also kanji[b-y] can be replaced with "kanji_". e.g: https://kanji.jitenon.jp/kanji_/26151.html Laftp0 (talk) 10:30, 25 November 2022 (UTC)
Support looks like a useful site. does this site just catalogue kanji? if so i think "kanji" can be dropped from the identifier, leaving either a number or an ID in the form "b/670". Infrastruktur (talk) 11:37, 25 November 2022 (UTC)
Notified participants of WikiProject Japan --Nw520 (talk) 09:57, 25 November 2022 (UTC)
Support
formatter URL |
| |||||||||||||||||||||||||
add value |
Is this not allowed?
Syunsyunminmin (talk) 12:53, 25 November 2022 (UTC)
Support --Okkn (talk) 05:50, 26 November 2022 (UTC)
- I support Syunsyunminmin's formatter. "kanji" prefix is really unnecessary, but it's a little unnatural that identifiers start with /. Laftp0 (talk) 06:36, 26 November 2022 (UTC)
Weak oppose I also find that site useful. However, the operating company is small and there are concerns about permanence.(私もサイトは有用だと思います。しかし、運営会社が小さく永続性に不安があります。)--Camillu87 (talk) 15:10, 27 November 2022 (UTC)
- @Camillu87:As per consensus rules, the closing property creator is free to disregard claims that are not substantiated. Do you have a reference that supports the claim that the company might be in trouble? Infrastruktur (talk) 19:20, 28 November 2022 (UTC)
- The operating company was established in 2020 with capital of 3 million yen and 4 employees.([14],[15]) It is an unnamed company and website where no useful mention can be found even if you search on google etc., so it is doubtful whether it will still be in operation 5 or 10 years from now. I have no further information.(運営会社は2020年に設立され、資本金300万円、従業員4人の会社です。googleなどで検索しても有益な言及が見つからない無名の会社、webサイトですので、5年先、10年先も運営されてるかは疑問があります。それ以上の情報は持っていません。)--Camillu87 (talk) 13:44, 29 November 2022 (UTC)
- @Camillu87:As per consensus rules, the closing property creator is free to disregard claims that are not substantiated. Do you have a reference that supports the claim that the company might be in trouble? Infrastruktur (talk) 19:20, 28 November 2022 (UTC)
- If there are no objections, I'll apply the Syunsyunminmin's formatter above. Laftp0 (talk) 12:47, 3 December 2022 (UTC)
- @Syunsyunminmin: There is a bug in it, the first formatter should be "https://kanji.jitenon.jp/kanji$1.html", and the regex should be fixed up to match. Infrastruktur (talk) 14:42, 3 December 2022 (UTC)
- @Infrastruktur: There seems to be a misunderstanding between you and me. I expect the value of this property to be numeric only. ex,
26151
Syunsyunminmin (talk) 14:59, 3 December 2022 (UTC)
- @Infrastruktur: There seems to be a misunderstanding between you and me. I expect the value of this property to be numeric only. ex,
- What Syunsyunminmin suggested won't work, Wikidata doesn't support applies if regular expression matches (P8460) (the property was created without any input from the Wikidata developers). - Nikki (talk) 18:55, 31 March 2023 (UTC)
- @Syunsyunminmin: There is a bug in it, the first formatter should be "https://kanji.jitenon.jp/kanji$1.html", and the regex should be fixed up to match. Infrastruktur (talk) 14:42, 3 December 2022 (UTC)
Boosty author ID Edit
Description | author profile slug on boosty.to |
---|---|
Data type | External identifier |
Domain | person or organization (Q106559804) |
Allowed values | [a-z_]+ |
Example 1 | Alai Oli (Q4033661) → alaioliband |
Example 2 | Ilya Varlamov (Q4103885) → vrlmv |
Example 3 | Tamara Eidelman (Q17377888) → eidelman |
Implied notability | Wikidata property for an identifier that does not imply notability (Q62589320) |
Formatter URL | https://boosty.to/$1 |
Applicable "stated in"-value | Boosty (Q116821121) |
Wikidata project | WikiProject Russia (Q10803886) |
Motivation Edit
Mostly Russian crowdfunding Patreon (Q15861362)/OnlyFans (Q61707579) like platform owned by My.Games (Q106171121) (part of VK (Q1885456)). Quite popular in RuNet.
Discussion Edit
Notified participants of WikiProject Authority control. —putnik 21:57, 18 February 2023 (UTC)
Notified participants of WikiProject Russia. —putnik 21:58, 18 February 2023 (UTC)
Oppose The item for the website Boosty (Q116821121) was created by you just today and there is no external perception so far. --Kolja21 (talk) 22:03, 18 February 2023 (UTC)
- See this list. Might be a good start. Regards Kirilloparma (talk) 07:00, 12 March 2023 (UTC)
- It's a small Russian version of Patreon allegedly flourished after Patreon itself was banned in Russia a year ago. Before voting for this relatively new and relatively unknown service I'd like to have a general idea of how many notable persons might really use it (for the record: we currently have 1269 WD items with Patreon ID). Андрей Романенко (talk) 22:15, 18 February 2023 (UTC)
- I expect to have up to 10% of Patreon values, and the Patreon property is still not filled in many items right now. So it should be something like few hundreds in total. —putnik 20:46, 19 February 2023 (UTC)
Support Facenapalm (talk) 11:48, 22 February 2023 (UTC)
Support --Deansfa (talk) 00:19, 5 March 2023 (UTC)
Support. @putnik: I managed to scrape a little over 50 identifiers from the start page. Not sure how many of these are notable, but it could be a good start. I also see some Russian video game related news websites using this platform. If no one has any further objections, I'll mark this proposal "as ready" right tomorrow, and then about 24 hours after the "ready" status, I'll create this property. Regards Kirilloparma (talk) 07:00, 12 March 2023 (UTC)
Oppose Just because someone has the equivalent of a Patreon page does not make them notable. The site can have a great number of profiles on it to make up for it, but I don't see any content creator counts here. Edit: 50 random people is nowhere near enough. For a proposal to pass it needs 100 notable people minimum. As an example if you assume 2% of the people on the site would qualify for a page on russian wikipedia, that would still mean you need to show there is 5000 content creators on the site. The numbers aren't that important, you get the idea. Infrastruktur (talk) 23:42, 12 March 2023 (UTC)
stock keeping unit Edit
Motivation Edit
We (including me Photocyte (talk) 20:16, 17 March 2023 (UTC)) are working on a Scientific Labware ontology + database (https://github.com/Bioprotocols/labware-databank/issues/3), and it would be useful to represent the company-specific stock keeping units & keep them in sync with Wikidata. Generally speaking, stock keeping units are used everywhere in global physical and electronic commerce. Would be worth representing in Wikidata.
An alternative approach is to make project proposals for vendor-specific SKUs, but that would be extremely laborious to implement for all companies on Wikidata. (some millions?)
But here are some large vendors, at least in the scientific space, where it might make sense to have independent Property proposals:
Some past discussion happened here: https://www.wikidata.org/wiki/Wikidata_talk:WikiProject_Ontology?markasread=883442226&markasreadwiki=wikidatawiki#c-Lectrician1-20230317181100-Photocyte-20230317180400
I expect there are some "real" ontologies out there with an equivalent stock keeping unit term, so would love feedback on how to rigorously tie this property into those ontologies.
It might be useful to have a format constraint of: [A-Z\d]{200} (could represent sha512 hashes in base36, in the unlikely event any company is using that) Photocyte (talk) 15:42, 25 March 2023 (UTC)
On second thought, a purely alphanumeric format constraint may exclude non-western scripts which do not use arabic numerals. So, perhaps there should be no constraints. Photocyte (talk) 14:41, 27 March 2023 (UTC)
Discussion Edit
WikiProject Ontology has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
Notified participants of WikiProject Companies
WikiProject Properties has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
Comment The datatype should not be external identifier but string - similar to ticker symbol (P249) this is an identifier only with respect to the issuer, not universal. ArthurPSmith (talk) 19:34, 28 March 2023 (UTC)
@ArthurPSmith: , If taking https://www.wikidata.org/wiki/Wikidata:Property_proposal/Amazon.com_ID and https://www.wikidata.org/wiki/Wikidata:Property_proposal/part_number as examples, both those properties use External Identifier, rather than string. So I guess before I change it to string on this particular property proposal, I'd like to clarify if it should also be changed on those other accepted & in progress property proposals? Also pinging the properties group. I'm starting to realize that there are many similar concepts: model code, part number, SKU, and I want to be sure they are kept appropriately harmonized with external ontologies & uses of these terms Photocyte (talk) 18:32, 29 March 2023 (UTC)
- @Photocyte: The Amazon ID uniquely identifies a product, as it is a code specific to Amazon, so there's no problem calling that an external id. The part number proposal was not done, but if it had been it should not have been an external identifier as it does not uniquely identify items (the same part number could be used by different vendors to identify different things). ArthurPSmith (talk) 12:11, 30 March 2023 (UTC)
IndExs Exsiccata Editor ID Edit
Description | identifier in the IndExs online database for an editor of exsiccatae or exsiccata-like series |
---|---|
Data type | External identifier |
Domain | item |
Allowed values | [0-9]+ |
Example 1 | Elias Magnus Fries (Q15405)→42057 |
Example 2 | Ferdinand Christian Gustav Arnold (Q2460005)→41766 |
Example 3 | Karl Wilhelm Gottlieb Leopold Fuckel (Q66899)→42064 |
Example 4 | Dagmar Triebel (Q21339093)→42846 |
Example 5 | Teofil Wojterski (Q109833617)→42937 |
Source | https://www.botanischestaatssammlung.de/DatabaseClients/IndExs/index.jsp |
Planned use | linking persons to information in Index of Exsiccatae online database |
Number of IDs in source | 1400 |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://services.snsb.info/indexs/api/v1/agents/$1 |
Motivation Edit
- Connecting IndExs Editors and exsiccata IDs with Wikidata for Disambiguation of People Names and Work in Botanical and Mycological Collections, see https://doi.org/10.3897/biss.6.93585.
- Having this property the users of services will have additional information on the role of persons working on and distributing of herbarium material by the system of well documented series called exsiccatase (see Q114554807)
– The preceding unsigned comment was added by TriebelD (talk • contribs) at 14:27, April 25, 2023 (UTC).
Discussion Edit
Comment Looks interesting. Can you improve the examples (e.g. add the suggested values)? TiagoLubiana (talk) 18:06, 11 May 2023 (UTC)
- Reformated the examples to show the links and suggested values. 141.84.65.170 11:08, 17 May 2023 (UTC)
- I improved the examples in June. Could the Wikidata team please proceed. Thanks TriebelD (talk) 12:49, 26 July 2023 (UTC)
- Having this property the users of services will have additional information on the role of persons working on and distributing of herbarium material by the system of well documented series called exsiccatase (see Q114554807)
Support seems ok to me. ArthurPSmith (talk) 18:48, 27 July 2023 (UTC)
Archiefpunt curator ID Edit
Represents | Archiefpunt (Q2472944) |
---|---|
Data type | External identifier |
Example 1 | Argos, Centrum voor Kunst en Media (Q47144231) → BH06-ED37-9779-5996-BABD3953BW9A |
Example 2 | Stadsarchief Ronse (Q52217418) → 9332d1e9-b960-4dd8-9f75-e2d8db6048b0 |
Example 3 | Éditions Labor (Q3579388) → BHFA-C4C3-D3E6-9960-ED565303BW9A |
Planned use | import identifiers to items about people from database |
Formatter URL | https://archiefpunt.be/beheerder/$1 |
See also | [16] [17] |
Motivation Edit
Flanders Arts Institute is the database for private archives in Brussels and Flanders. They have built a database with all kinds of data about these archives, and one part of the database is for curators. – The preceding unsigned comment was added by JhowieNitnek (talk • contribs) at 10:04, 23 June 2023 (UTC).
Discussion Edit
Notified participants of WikiProject Museums Jonathan Groß (talk) 14:31, 14 September 2023 (UTC)
Archiefpunt archive ID Edit
Represents | Archiefpunt (Q2472944) |
---|---|
Data type | External identifier |
Example 1 | Jacques Obozinski (Q3159685) → B0DC-4B21-BCF8-1960-B87210619AE9 |
Example 2 | De Koninck Brewery (Q2684279) → 7C01-67EB-9EDE-1960-57D122694AE9 |
Example 3 | De Zangfaculteit (Q99390815) → 12AD-A911-9188-D196-4EE220557AE9 |
Planned use | import identifiers to items about people from database |
Formatter URL | https://archiefpunt.be/archief/$1 |
See also | [18] [19] |
Motivation Edit
Flanders Arts Institute is the database for private archives in Brussels and Flanders. They have built a database with all kinds of data about these archives. – The preceding unsigned comment was added by JhowieNitnek (talk • contribs) at 14:20, 23 June 2023 (UTC).
Discussion Edit
Notified participants of WikiProject Museums Jonathan Groß (talk) 14:31, 14 September 2023 (UTC)
Archiefpunt compiler ID Edit
Represents | Archiefpunt (Q2472944) |
---|---|
Data type | External identifier |
Example 1 | André Goudbeek (Q2552378) → SS4D-D0CC-D709-D960-B7AF87400AR9 |
Example 2 | Het Brussels Kamertoneel, Brussel (Q49426721) → SS7E-EE28-E409-D960-B7AF87607AR9 |
Example 3 | De Antwerpse Morgen (Q47458076) → SSFF-77C1-3F61-9960-57D11644AR9A |
Source | https://archiefpunt.be/bladeren# |
See also | [20] [21] |
Motivation Edit
Flanders Arts Institute is the database for private archives in Brussels and Flanders. They have built a database with all kinds of data about these archives, and one part of the database is for the people/organization who created the archive. – The preceding unsigned comment was added by JhowieNitnek (talk • contribs) at 14:18, 23 June 2023 (UTC).
Discussion Edit
Notified participants of WikiProject Museums Jonathan Groß (talk) 14:31, 14 September 2023 (UTC)
Capitolium Art artist ID Edit
Description | identifier for an artist on the Capitolium Art website. |
---|---|
Data type | External identifier |
Domain | human (Q5), organization (Q43229) |
Allowed values | ^(?=.*\/)(?=.*-)(?=.*[0-9a-z])[0-9a-z\/-]+$ |
Example 1 | Luigi Bartolini (Q172346) → bartolini-luigi-1892-1963/xar-4915 |
Example 2 | Robert Capa (Q152524) → capa-robert-1913-1954/xar-5954 |
Example 3 | Giorgio de Chirico (Q156622) → de-chirico-giorgio-1888-1978/xar-2117 |
Source | https://www.capitoliumart.it/it/artisti |
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]. |
Number of IDs in source | several thousand |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://www.capitoliumart.it/it/artista/$1 |
See also | Artnet artist ID (P3782) |
Motivation Edit
This is the website of a well-known Italian auction house established in 1988 with branches in Brescia (owning the Palazzo Cigola Fenaroli (Q96095753)), Rome, Turin, and Ospitaletto. According to their website, they have conducted more than 400 auctions in just the last 10 years. For each artist whose work has been sold, there is a page containing a detailed biography, a list of any available works (past or present), and their relevant details/photos. There are already several thousand biographies available (and some inbound links/quotes in it.wiki and fr.wiki). The website is pretty much useful also for adding reliable references for lesser known artists, since they provide biographies written by the auction house's experts and good photos which can sometimes be uploded on Commons (mainly with PD-italy, PD-old-100-1923, or PD-art tags).
Note: the site also uses URLs which provide a basic English translation with the same pattern (eg: https://www.capitoliumart.it/en/artista/de-chirico-giorgio-1888-1978/xar-2117 ) with "EN" instead of "IT" in the middle of it. I guess the basic URLs could/would be more stable over the years, but maybe the English version would be more usable?... Unfortunately using URLs with that "xar" code only doesn't work, otherwise they were definitely cleaner. --Teatroge (talk) 11:21, 22 July 2023 (UTC)
Discussion Edit
Support Seems useful. ArthurPSmith (talk) 18:18, 31 July 2023 (UTC)
Danacode Edit
Description | A property to encode the "Danacode" of a written work, which is a book identifier used extensively in Israel often in place of, or alongside the more international ISBN. |
---|---|
Represents | Danacode (Q113022438) |
Data type | External identifier |
Domain | instance of (P31)version, edition, or translation (Q3331189) |
Example 1 | Q113133917 → 32-11048 (or maybe the extended code: 003200110487) |
Example 2 | Q113278990 → 31-4090 (or maybe the extended code: 003100040907) |
Example 3 | Q113279156 → 40-51504 (or maybe the extended code: 004000515045) |
Example 4 | Q113360746 → 644-1031 (or maybe the extended code: 064400010311) |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://simania.co.il/searchBooks.php?searchType=tabAll&query=$1 |
See also | ISBN-13 (P212), ISBN-10 (P957) |
Distinct-values constraint | yes |
Motivation Edit
גורם מסבך אחד שיש בדאנאקוד (עם משווים עם מסת"ב) זה ייצוגו המרובה. במפורש, יש בעיקר שני ייצוגים לכל קוד. הייצוג המקוצר נמצא בשימוש נרחב במקומות שמיועדים לקריאה על ידי אנשים והארוך מיועד בדרך כלל למערכות מידע, כגון ברקודים וגם מסדי נתונים. ובכן, באתר של דאנאקוד אומרים (בתרגום חופשי מאנגלית) ש:
"במסדי נתונים, דאנאקוד מיוצג כטקסט, כ־12 תווים, המכילים את ספרת הביקורת. בכל זאת, אפשר לייצג אותו רק דרך 11 התווים הראשונים ואפשר לחשב את ספרת הביקורת לפי כשיהיה צורך. ייצוג חזותי שימושי מאוד זה הגרסה המקוצרת שבה שמים מקף אמצעי בין מספר המו"ל לבין מספר הפנימי של המו"ל, ובגרסה הזאת לא מכילים את האפסים המובילים בשני המספרים וגם לא מכילים את ספרת הביקורת. המאף האמצעי משמש לצרכים חזותיים בלבד ולא נחשב כחלק ממערכת המספרים של דאנאקוד. לכן, הדאנאקוד 080002610032 מקוצר חזותית ל־800-261003."
אתרי אינטרנט רבים שמכילים דאנאקוד מכילים את הגרסה המקוצרת הזאת. גם, לפעמים הספרייה הלאומית מכילה את הדאנאקוד ברשומות ה־MARC שלהם, ושם משתמשים בקוד המורחב בן 12 תווים. בגלל שאני לא מומחה גדול בויקינתונים, אני לא בטוח איך אנחנו מטפלים בייצוג המרובה שכזה בדרך כלל. לעכשיו, אני מציע שנכניס את ה קוד המורחב לתוך רשומותינו בוויקינתונים, אך אולי נרצה אופן אוטומטי להמיר בין הקוד המקוצר לקוד המלא שבן 12 תווים.
למי שמעוניין, קיים כאן גיליון (שנמצא באתר של מרכז הספר והספריות, ושמסופק על־ידי הספרייה הלאומית) שמחשב את הדאנאקוד המורחב מהדאנאקוד המקוצר.
חשוב לציין שה־formatter URL שנתתי לעיל הוא לצד שלישי, Simania (Q6680757) (ולא לDanalog (Q113688058) עצמו שלא הצלחתי למצוא בקלות דף ידידותי למשתמש שאפשר להשתמש בו כ־formatter URL). מערכת החיפוש של Simania (Q6680757) תומכת אך ורק בייצוג המורחב של הדאנאקוד. בין האופציות הסבירות האחרות נכלל https://merhav.nli.org.il/primo-explore/search?query=any,contains,$1&tab=blended&search_scope=NLI_Blend&vid=NLI&lang=iw_IL&offset=0 שהוא קישור לMerhav (Q108571985) מבית National Library of Israel (Q188915), וגם הוא תומך אך ורק בדאנאקוד המורחב (אבל זה יותר חיפוש חופשי ופחות כתובת URL ספציפי לחיפוש דאנאקוד).
מצד שני, קיימים גם https://www.am-oved.co.il/AllResults?bskeyword=$1 שיעבוד לספרים בהוצאת Am Oved (Q2840776) ו https://www.schocken.co.il/Book/Anything.aspx?code=$1 שעובד לספרים בהוצאת Schocken Books (Q1020343), אבל המערכות האלה משתמשות בדאנאקוד המקוצר ולא המורחב. עם זאת, עדיין לא ברור לי אם עדיף לאחסן את הייצוג המקוצר או המורחב במאפיין המוצע. אולי אפילו יהיה צורך בשני מאפיינים, אבל אני לא בטוח.
תודה רבה לכולם. לוכסן (talk) 17:48, 30 July 2022 (UTC)One complicating factor that Danacode has (compared to ISBN) is its multiple representations. Specifically, there are two to three major representations of the same code. Citing the Danacode website itself, they say:
"In Databases danacode is represented as text, 12 characters, including the check digit. Still it can be represented by 11 characters and the check digit can be calculated when needed. A very useful visual representation is a short version which puts a hyphen between Publisher and Publication numbers, ignores leading zeroes in both numbers and omits the check digit. The hyphen is used for visualization only and is not part of the danacode numbering system. Thus the danacode 080002610032 is reduced visually to 800-261003"
Many websites that contain a Danacode contain this short-version. Additionally, the National Library of Israel has Danacode listed often in their MARC records, and there it uses the 12 character full version with check digit. Not being an expert in Wikidata, I'm not entirely sure offhand how we generally handle this multiple representation nature. For now, I'm going to suggest we want the extended full code in Wikidata, though we may want some automated way to convert shortened codes to the full 12-digit code.
For those interested, here there is a spreadsheet on the website of the Israeli Center for Libraries (Q6959775) (which is said to be provided by National Library of Israel (Q188915)) which calculates the extended Danacode from the short, hyphenated form.
Note that the formatter URL that I gave is to a 3rd party service, Simania (Q6680757), whose search feature supports ISBN and Danacode for books in its catalog, but notably, it only supports the 12-digit extended Danacode format for searches. Other format URLs which can work include https://merhav.nli.org.il/primo-explore/search?query=any,contains,$1&tab=blended&search_scope=NLI_Blend&vid=NLI&lang=iw_IL&offset=0, which searches the index of the Merhav (Q108571985) by the National Library of Israel (Q188915), also with the extended Danacode, though this is more of a freeform search box than an exact lookup by Danacode.
On the other hand, https://www.am-oved.co.il/AllResults?bskeyword=$1 works for books published by Am Oved (Q2840776), and https://www.schocken.co.il/Book/Anything.aspx?code=$1 works for books published by Schocken Books (Q1020343), but both exclusively support the short-code. So, it seems to me that it isn't totally clear whether we should store the the long or the short form of the Danacode, or maybe we might even need two properties?
Thank you all. לוכסן (talk) 17:48, 30 July 2022 (UTC)Discussion Edit
Notified participants of WikiProject National Library of Israel לוכסן (talk) 19:13, 30 July 2022 (UTC)
- @Geagea: תודה על התשובה. למיטב הבנתי, כן. למשל, תראה את האתר של הוצאת נהר שמדבר על הספר Q113360746 ונרשם שם הדאנאקוד שלו, אך לא מזהה ה־ULI. זאת אומרת, יש המון מקומות בהם הדאנאקוד משמש כתעודת זהות עבור ספר (בדומה למסת"ב הבין־לאומי) ואז חשוב שנוכל לייצג את זה במערכת. ובדוגמה שנתתי, במערכת ה־ULI, אם מחפשים את שמו של ׳מותו של שאפתן׳, יש שתי תוצאות דומות (לי לא ברור מה ההבדל ביניהם), אך ברשומת ה־MARC של השני, הדאנאקוד נרשם שם, שאפשרי כי דאנאקוד נמצא בתקן פורמט MARC של ספריית קונגרס. לוכסן (talk) 06:11, 31 July 2022 (UTC)
- אני רואה את דאנאקוד בMARK של הספרייה הלאומית. ראה ב-Q113360746 יש מזהה רשומה בספרייה הלאומית. אם אתה נכנס לרשומת המארק הדאנאקוד אכן מופיע. מכאן שאני יכול לשלוף מהרשומות של הספרייה הלאומית את הדאנאקוד עבור הפריטים שכבר יש להם NNL item ID (P3959). הבעייה היא קישור רשת. האם יש קישור רשת לדאנאקוד. איזשהו אתר שבקישור שלו מופיע הדאנאקוד? Geagea (talk) 13:44, 1 August 2022 (UTC)
- @Geagea: לגבי אתרים שבכתובת ה־URL שלהם מופיע דאנאקוד, אני לא בטוח, אבל זה ברור שהאתרים האלה מבינים בדאנאקוד. למשל, באתר צומת הספרים, אם אני מכניס בתיבת החיפוש ״32-11048״, מופיע פופ-אפ קטן שמפנה לספר הראוי, ״1984״ (כתוב שם ״אלף תשע מאות שמונים וארבע״), אבל הדבר המוזר זה שאם אני מקיש אנטר, אני מגיע לדף תוצאות שאומר שאין תוצאות לחיפוש שלי. גם, אם אני מחפש שם את הדאנאקוד המורחב בעל 12 ספרות (כמוסבר לעיל), לא מופיע שום דבר. עם זאת, כתובת ה־URL עצמו של הספר 1984 באתר שלהם מכילה את הדאנאקוד המורחב (קישור ל־1984 בצומת הספרים). כמעט אותו הדבר קורה באתר bookme, בו משהו מופיע דרך הפופ-אפ אך לא אחרי לחיצת אנטר למרות שהדאנאקוד המקוצר מופיע ב־URL. חוץ מהבעיה המוזרה ההיא, לפחות לספרים ממו״לים ספציפיים, אפשר לחפש את הדאנאקוד שלהם באתר המו״ל (למשל, חיפוש ל־32-11048 באתר של עם עובד מחזיר את הפריט ל־1984). אולי אתה מומחה גדול ממני ותוכל לפענח את הפאזל הזה בצומת הספרים וב־bookme? :) לוכסן (talk) 14:55, 1 August 2022 (UTC)
- אני רואה את דאנאקוד בMARK של הספרייה הלאומית. ראה ב-Q113360746 יש מזהה רשומה בספרייה הלאומית. אם אתה נכנס לרשומת המארק הדאנאקוד אכן מופיע. מכאן שאני יכול לשלוף מהרשומות של הספרייה הלאומית את הדאנאקוד עבור הפריטים שכבר יש להם NNL item ID (P3959). הבעייה היא קישור רשת. האם יש קישור רשת לדאנאקוד. איזשהו אתר שבקישור שלו מופיע הדאנאקוד? Geagea (talk) 13:44, 1 August 2022 (UTC)
- @Geagea: תודה על התשובה. למיטב הבנתי, כן. למשל, תראה את האתר של הוצאת נהר שמדבר על הספר Q113360746 ונרשם שם הדאנאקוד שלו, אך לא מזהה ה־ULI. זאת אומרת, יש המון מקומות בהם הדאנאקוד משמש כתעודת זהות עבור ספר (בדומה למסת"ב הבין־לאומי) ואז חשוב שנוכל לייצג את זה במערכת. ובדוגמה שנתתי, במערכת ה־ULI, אם מחפשים את שמו של ׳מותו של שאפתן׳, יש שתי תוצאות דומות (לי לא ברור מה ההבדל ביניהם), אך ברשומת ה־MARC של השני, הדאנאקוד נרשם שם, שאפשרי כי דאנאקוד נמצא בתקן פורמט MARC של ספריית קונגרס. לוכסן (talk) 06:11, 31 July 2022 (UTC)
- מומחה או לאו, כל הנושא מצריך זמן לבדוק ולדייק את הכל, וזמן זה מצרך שאין לי אותו כרגע. צריך למלא את כל השדות וצריך קישור אחד טוב שבו אפשר להגיע לפריט. במקרה הזה צריך לחשוב מה לעשות. Geagea (talk) 15:01, 1 August 2022 (UTC)
- יש עניין לרשום את הדאנאקוד כי קיימים ספרים עם מספר זה שאינם ב-ULI (או שלא הגיעו לספרייה הלאומית או שהוחלט שהשינוי כל כך מינורי ששיני הדאנאקוד לא מהווה טריגר לחוק הפקדת ספרים). הקובץ באתר מרכז הספר והספריות אכן הוכן ע"י צוות רכש וקליטה בספרייה הלאומית. האם ניתן לקבוע שאתרי חנויות ספרים ומו"לים תמיד משתמשים בפורמט המקוצר של XX-XXXXX? אם כן, לא נראה לי בעיה לעשות קצת reverse engineering לאקסל ולהחזיר מהדאנאקוד המורחב את הקצר. --AhavaCohen (talk) 13:59, 2 August 2022 (UTC)
- אהבה, תודה על תשובתך. סלחי לי על העיכוב הגדול כאן. חקרתי את זה קצת יותר ועדכנתי את התיאור לעיל. ואז, יש לי קישורים לSimania (Q6680757) ולMerhav (Q108571985) מהספרייה הלאומית שמצריכים את הדאנאקוד המורחב, אבל יש גם קישורים לAm Oved (Q2840776) ולSchocken Books (Q1020343) שמצריכים את המקוצר. אז, ממש לא ברור לי מה עדיף לאחסן במאפיין עצמו. מה דעתך? תודה רבה! לוכסן (talk) 03:33, 11 June 2023 (UTC)
- יש עניין לרשום את הדאנאקוד כי קיימים ספרים עם מספר זה שאינם ב-ULI (או שלא הגיעו לספרייה הלאומית או שהוחלט שהשינוי כל כך מינורי ששיני הדאנאקוד לא מהווה טריגר לחוק הפקדת ספרים). הקובץ באתר מרכז הספר והספריות אכן הוכן ע"י צוות רכש וקליטה בספרייה הלאומית. האם ניתן לקבוע שאתרי חנויות ספרים ומו"לים תמיד משתמשים בפורמט המקוצר של XX-XXXXX? אם כן, לא נראה לי בעיה לעשות קצת reverse engineering לאקסל ולהחזיר מהדאנאקוד המורחב את הקצר. --AhavaCohen (talk) 13:59, 2 August 2022 (UTC)
- I read the above through google translate. Seems like this is distinct from ULI ID. We don't actually need a URL formatter to make the property. So generally I support. BrokenSegue (talk) 04:16, 14 September 2022 (UTC)
- @BrokenSegue: Thank you for taking a look (and sorry for the delay). It is good to hear that a URL formatter isn't necessary. I did manage to find a few options in the end, which I added above. The remaining question is if we should store the short-form or the extended-form of the Danacode in this proposed property, as both forms are equivalent, and there are potential formatter URLs that work with each of the two formats (more description at the end of the motivation section above). What would you suggest? Thank you! לוכסן (talk) 03:42, 11 June 2023 (UTC)
- I would prefer the short form but I'll leave that decision up to someone with more domain expertise. It's been a long time since I read this but one thing I would clarify is whether this should be used on works or editions of works. ISBNs go on editions. BrokenSegue (talk) 03:52, 11 June 2023 (UTC)
- @BrokenSegue The identifier is for the manifestation (what I assume you're calling the edition) -- a different edition or publisher would, if rules were followed, require a new danacode. AhavaCohen (talk) 05:53, 11 June 2023 (UTC)
- The disadvantage of the short form is that one needs to have the book in hand or have the short form listed on the publisher's website to find the specific short form used (if any). The long form is the form in use in all Israeli academic libraries and in the Union List of Israel catalog and so can be added after the fact by anyone who searches those catalogs. That means we have two issues here: 1) Getting the code into Wikidata (easier with the long form) 2) Linking out from Wikidata to another location (easier form depends on where you want to go) AhavaCohen (talk) 05:58, 11 June 2023 (UTC)
- I would prefer the short form but I'll leave that decision up to someone with more domain expertise. It's been a long time since I read this but one thing I would clarify is whether this should be used on works or editions of works. ISBNs go on editions. BrokenSegue (talk) 03:52, 11 June 2023 (UTC)
- @BrokenSegue: Thank you for taking a look (and sorry for the delay). It is good to hear that a URL formatter isn't necessary. I did manage to find a few options in the end, which I added above. The remaining question is if we should store the short-form or the extended-form of the Danacode in this proposed property, as both forms are equivalent, and there are potential formatter URLs that work with each of the two formats (more description at the end of the motivation section above). What would you suggest? Thank you! לוכסן (talk) 03:42, 11 June 2023 (UTC)
Support. I have read all again now. As a matter of fact it's works just like ISBN is working. I support the proposal per Dr. User:AhavaCohen. So few things:
- a. Just like ISBN we need two Properties for the short-code and the long. Even though we have a way to transcode from the short to the long code we should have both just like ISBN.
- ( transcode: (explained her) also we have explanation how to calculate the check digit her (ספרת ביקורת) (Hebrew)).
- b. The danacode id can be useful using this page (in English) (needed some adjustment).
- c. I'ts been mentioned her that: "Danacode is recognized and registered as Standard Identifier Source Code at The Library of Congress". As the id appears in the National Library of Israel database I can create mix-n-match catalog. Geagea (talk) 14:54, 12 June 2023 (UTC)
- @Geagea. Thank you for your response. I address each of your points separately:
- a. Two separate properties sounds like an acceptable solution to me if it's what everyone thinks is most appropriate. I will note that the link you gave for calculating the check digit is correct for ISBN, but not for Danacode. Please see the Wikipedia article דאנאקוד#ספרת הביקורת (Hebrew), where I described the calculation of the check digit (based on the Excel sheet provided by the National Library of Israel (Q188915) for converting from the short to long forms of the Danacode).
- b. I didn't know that we could make that page accept IDs other than ISBN. Yes, it would be great for us to add the Danacode there as well.
- c. Making a Mix-n-match sounds great. Please see here on the Danacode item which links to the specific place in the LoC vocabulary.
- לוכסן (talk) 16:00, 12 June 2023 (UTC)
BG EGN Edit
Description | Bulgarian government issued personal identifier |
---|---|
Represents | BG Unique Citizen Identifier (Q5453452) |
Data type | External identifier |
Domain | Bulgarian citizen and resident |
Example 1 | Nikola Tulechki (Q121239734) --> 8404236483 |
Example 2 | MISSING |
Example 3 | MISSING |
Planned use | Populate this property with identifiers from official government sources for public office holders. |
Expected completeness | always incomplete (Q21873886) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation Edit
EGN is the primary unique identifier for Bulgarian citizens used by the administration.
Currently it is not disclosed due to outdated policies and fear among the population that it can be used for identity theft. It is not communicated even for public figures, such as candidates in elections and acting politicians. This creates difficulties in working with individual level public datasets.
Moreover following several massive data leaks, millions of EGN are already disclosed. This makes the "secret" status of the identifier even more problematic. For example it is still sometimes used a a means for 2FA or (without a seconady PIN) to access personal data.
As a first step, adding the property to Wikidata and then voluntarily disclosing its value by its respective holders, will be part of an advocacy campaign to ultimately change the government's policy towards disclosing it for public office holders and election candidates as well as finally implementing the necessary measures to ensure that it ca no longer be misused to access personal information.
Once the administration is convinced that the identifier should be shared, we will use it for integrating data about PEPs on Wikidata.
Notified participants of WikiProject Bulgaria
See also: https://blog.bozho.net/blog/2778
--Nikola Tulechki (talk) 09:05, 7 August 2023 (UTC)
Discussion Edit
Support Boyan-bechev --Boyan-bechev (talk) 05:54, 7 August 2023 (UTC)
Support Dbalinov (talk) 09:12, 7 August 2023 (UTC)
Comment Hmm, I'm not sure using wikidata to try to force a policy change is a good approach. However, is this number valid for deceased persons? We have Social Security Death Index entry (P8002) that is the US SSN identifier but in principle in Wikidata it is only used for those who are deceased, in which case it's a very useful identifier for them. ArthurPSmith (talk) 17:08, 10 August 2023 (UTC)
- Thanks for the comment, @ArthurPSmith. Policy change is just the first step. Our goal is to be able to use the ID for data integration and matching individuals across data sources. It follows that it will be very usefull on wikidata.
For that to be possible, though we first need to dedramatize its usage in the eyes of the BG public and the fact that I can say "It's safe, mine is already on wikidata" is a very strong argument when the debate hits the media. To answer your question, yes the EGN is unique and not reused after a person's death and we hope that , amongst other things, this effort will ultimately result in a public endpoint, much like the one related to Social Security Death Index entry (P8002), listing whether a person with this ID exists and is alive. --Nikola Tulechki (talk) 10:21, 14 August 2023 (UTC)
With a point of view of another country in the EU, I think this is unacceptable private data to be keep in the public. Sorry. —Ismael Olea (talk) 16:45, 14 September 2023 (UTC)
protected heritage site in Brussels ID (web) (en) – (Vertaal dit alstublieft in het Nederlands.) Edit
Description | identifier of a protected heritage site in Brussels, Belgium |
---|---|
Represents | protected heritage site in Brussels (Q19346745) |
Data type | External identifier |
Domain | geographical feature (Q618123),geographic location (Q2221906),cultural heritage (Q210272) |
Example 1 | Royal Palace (Q635307) → buildings/30402 |
Example 2 | Stoclet Palace (Q239028) → buildings/25407 |
Example 3 | Place Royale - Koningsplein (Q1049313) → streets/10001095 |
Example 4 | Grand-Place (Q215429) → streets/10002053 |
Source | https://monument.heritage.brussels/nl/ |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://monument.heritage.brussels/nl/$1 |
Robot and gadget jobs | yes |
See also | protected heritage site in Brussels ID (P3600), Classified properties and protected areas of Wallonia ID (P1133), Flemish Heritage Object ID (P1764), Protected objects Ostbelgien ID (P5942), |
Single-value constraint | yes |
Motivatie Edit
This is a better property than what is currently in use. protected heritage site in Brussels ID (P3600)
Note: https://monument.heritage.brussels/fr in French.
Discussion Edit
archINFORM ID (awards) Edit
Description | identifier for an award on the archINFORM website |
---|---|
Represents | archINFORM (Q265049) |
Data type | External identifier |
Template parameter | |2= in Template:ArchINFORM (Q6611520) with |1= being "awards" |
Domain | award (Q618779) |
Allowed values | [1-9][0-9]{0,5} |
Example 1 | Fritz Schumacher Award (Q83980530) → 23 |
Example 2 | Q1257253 → 132 |
Example 3 | Aga Khan Award for Architecture (Q389808) → 48 |
Source | https://www.archinform.net/ |
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 | as a unique identifier and source for awards and prices related to architecture, especially those so far uncovered on Wikidata |
Number of IDs in source | ca. 200 |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://www.archinform.net/awards/$1.htm |
Robot and gadget jobs | will be synchronized with archINFORM's own authority relation table by a bot |
See also | archINFORM person or group ID (P5508), archINFORM project ID (P5383) |
Motivation Edit
see similar property proposal: https://www.wikidata.org/wiki/Wikidata:Property_proposal/archINFORM_project_ID
Discussion Edit
Notified participants of WikiProject Built heritage --Arch2all (talk) 10:36, 18 August 2023 (UTC)
Support Huh, I didn't know architecture had so many awards! ArthurPSmith (talk) 20:53, 23 August 2023 (UTC)
Internet Dictionary of Polish Surnames ID Edit
Description | identifier in the nazwiska.ijp.pan.pl dictionary of surnames used in Poland |
---|---|
Represents | Internet Dictionary of Polish Surnames (Q118130420) |
Data type | External identifier |
Domain | property, instance of family name (Q101352), masculine family name (Q18972245), and any other entity that is some form of a surname (male, female, toponymic and whatnot) |
Allowed values | [-A-Z]+ |
Example 1 | Kowalski (Q3199417) → KOWALSKI |
Example 2 | Nowak (Q15073902) → NOWAK |
Example 3 | Czeszejko-Sochacki (Q121880021) → CZESZEJKO-SOCHACKI |
Source | https://nazwiska.ijp.pan.pl/ |
Number of IDs in source | 29,997 (as of 2023-09-12) |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://nazwiska.ijp.pan.pl/haslo/show/name/$1 |
Robot and gadget jobs | Yes, it would be perfect to let a bot simply populate this field with data I've collected. |
Motivation Edit
https://nazwiska.ijp.pan.pl is an online dictionary of surnames used in Poland (chiefly "Polish" surnames). For each surname in the database (~30,000 items as of August 2023), there's information re: origins of the surname, its popularity, and alternative spelling variants. This is now a freely available "ground truth" version of what we know about surnames in use in Poland. The URL formatter is pretty straightforward. However, there are multiple links concerning the same surname that will resolve successfully for the same surname: https://nazwiska.ijp.pan.pl/haslo/show/id/4910 https://nazwiska.ijp.pan.pl/haslo/show/name/TARCZYŃSKI https://nazwiska.ijp.pan.pl/haslo/show/name/TARCZY%C5%83SKI And all the above resolve successfully no matter the capitalization. Then there's a link to a full-page printout, too: https://nazwiska.ijp.pan.pl/haslo/print/id/4910 The printout version is in HTML and is actually more convenient to read than the standard page version. I don't know what the unique and permanent URL structure is and there are no indicators on the website itself. I think it would make most sense to go by the actual surname string and default to all caps (that's how surnames are listed in the body of the page; this is how data in the PESEL registry is maintained; and this would also avoid dilemmas related to automatic injection and capitalization of compound surnames. It's my understanding that the ID would be more "unique" than the character string, but it would entail and extra step (i.e., go to the search box, look up the surname, copy the ID). Given the database is high-quality, there's little reason to believe IDs would be more stable than surname strings. Finally, I went through the whole site and only found two instances of double entries – and there the IDs were different, so it seems that if there's potential for duplication, it'll happen no matter the ID or surname trying. TL;DR I suggest we go with https://nazwiska.ijp.pan.pl/haslo/show/name/TARCZYŃSKI ([A-Z])
(moved from description ArthurPSmith (talk) 19:11, 5 September 2023 (UTC))
This would provide readers with a certain "ground" truth" on surnames in Poland. (Add your motivation for this property here and your signature)
Discussion Edit
I'm very sorry if this isn't sufficient. First time posting something like this; it's a bit overwhelming. Update: the path can contain - (hyphens).
--Itorokelebogile (talk) 16:07, 27 August 2023 (UTC)
- @Itorokelebogile: I fixed up the proposal a bit. The examples should look like what I did for example 1 - can you add 2 more to flesh this out a little? Otherwise it looks good to me. ArthurPSmith (talk) 19:16, 5 September 2023 (UTC)
- Bless you, kind Wikidata soul! Updated the remaining 2 examples. Itorokelebogile (talk) 09:51, 6 September 2023 (UTC)
Support ArthurPSmith (talk) 20:30, 6 September 2023 (UTC)
Support --Gymnicus (talk) 16:34, 10 September 2023 (UTC)
- I think this should use the numeric ID. That's what is used by the links on the site's main page (where do the URLs with the name even come from?). There are ~6000 links using the numeric ID already, using described at URL (P973) (query). The template Template:R:pl:ISNP (Q122438370) and links on the Polish Wikipedia also use the numeric ID. You could use subject named as (P1810) as a qualifier to store the name as shown on the site.
For "PACAN" (20266 and 30045), https://nazwiska.ijp.pan.pl/haslo/show/name/PACAN doesn't work at all. For "KRASNY" (10237, which seems to be the Czech name "Krásný", and 20797, which seems to be the Polish name "Krasny"), https://nazwiska.ijp.pan.pl/haslo/show/name/KRASNY shows data matching the first link. If we use the name, how would we link the entries 20266, 30045 and 20797?
- Nikki (talk) 14:51, 12 September 2023 (UTC)- I'm totally open to relying on IDs, here's a bit of context as to why I pitched the hack-y approach:
- The URLs are inconsistent across the site. When you run lookups on the home page, you get sent to pages with IDs in the URLs. However, if you start clicking through the descriptions, you'll notice that those links use "name" URLs (title capitalization, e.g., Nowak). Although the IDs are technically unique, there are two surnames that have double entries (more on that later). The URLs aren't case-sensitive, so—seeing the setup other similar tools have on Wikidata—going with all caps would be consistent with those, easy to read, and map 1-to-1 with entries in the PESEL registry, I think.
- The website's code base is a bit crappy, but it has its advantages: you can basically get all the URLs and basic information by accessing the search API:https://nazwiska.ijp.pan.pl/public/backend/nwp/ajax/hasla-tab.php and https://nazwiska.ijp.pan.pl/public/backend/nwp/ajax/hasla-tab-slownik.php (1) if you clean the output up a bit, you'll notice the dictionary has 29,997 entries; (2) like I said, two pairs are doubled—which is a confusing way of saying these guys are a bit of a problem: KRASNY (ID 10237) and KRASNY (ID 20797) as well as PACAN (20266) and PACAN (30045). I'm not sure if KRASNY was supposed to be written up twice (https://nazwiska.ijp.pan.pl/haslo/show/id/20797 and https://nazwiska.ijp.pan.pl/haslo/show/id/10237—I doubt two entires were created because of different etymologies; see https://nazwiska.ijp.pan.pl/haslo/show/name/BACH—it's got three etymologies listed, two Polish, one German; in the case of Pacan, there are no real differences other than the rank order of 4744 vs 4745 and the fact one of the entries just looks altogether incomplete). If you try to access info on these surnames via the "name in the URL" approach, you'll fail; but then again, it's not clear to what ID we should be linking anyway, so it's a matter of choosing the problem we prefer and dealing with the consequences. To be frank, 2 "unstable" links out of 29,997 doesn't feel bad. For those two guys, we could have the number ID URL added somewhere; or simply raise this issue with the authors of the dictionary, so that they can fix things on their end.
- I agree that IDs are technically safer, i.e., we can assume that IDs being numeric and assigned (arguably) automatically should be more stable, but I'd quite enjoy the convenience of understanding that—if I type in a surname at the end—I'll get a result (rather than force people to always go to the home page to look stuff up).
- I'm new, so I'll run with whatever you guys feels more appropriate; just thought I'd give you a bit of context. General convenience vs assuming the website developers always know better (which, even if not true, is a solid approach that's typically a bit more future-proof, so I'm down with this approach).
- Thanks for the feedback, and, again, totally open to IDs. Itorokelebogile (talk) 15:37, 12 September 2023 (UTC)
- Oh, forgot to add: is you look at this JSON file, https://nazwiska.ijp.pan.pl/public/backend/nwp/ajax/hasla-tab-slownik.php you'll notice that the listing there uses all caps for the surnames. I know it's not a "+1" in favor of links, but it does, I assume say something about their style guide (all surname-oriented entries have headings in all caps). Itorokelebogile (talk) 15:41, 12 September 2023 (UTC)
- I'm totally open to relying on IDs, here's a bit of context as to why I pitched the hack-y approach:
BioGRID Publication Edit
Description | Identifier on the BioGRID database |
---|---|
Represents | BioGRID (Q4914619) |
Data type | External identifier |
Domain | journal articles, (such as Protein kinase C switches the Raf kinase inhibitor from Raf-1 to GRK-2 (Q28580358)) genes, (such as SCG5 (Q18031470)) |
Allowed values | numeric |
Example 1 | Protein kinase C switches the Raf kinase inhibitor from Raf-1 to GRK-2 (Q28580358)→150930/publication |
Example 2 | SCG5 (Q18031470)→112345 |
Example 3 | subject→value |
Formatter URL | https://thebiogrid.org/$1 |
Motivation Edit
BioGRID holds curated data parsed from journal articles see https://thebiogrid.org/150930/publication, and also holds downloadable information about genes and proteins: https://thebiogrid.org/112345 (also links to the gene in other databases) – The preceding unsigned comment was added by BhamBoi (talk • contribs) at 17:00, August 28, 2023 (UTC).
Discussion Edit
Support seems useful to me. ArthurPSmith (talk) 19:07, 5 September 2023 (UTC)
DBpia author ID Edit
Description | identifier for an author in the DBpia database provided by Nurimedia |
---|---|
Data type | External identifier |
Example 1 | Geuntaek Kang (Q121063076) → 560302 |
Example 2 | Hyun Suk Kim (Q121407465) → 2988988 |
Example 3 | Hwang Woo-suk (Q482836) → 4122698 |
Example 4 | V. Narry Kim (Q7906149) → 1287932 |
Source | DBpia (Q115494266) |
Number of IDs in source | ~10000 |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://www.dbpia.co.kr/author/authorDetail?ancId=$1 |
Motivation Edit
DBpia is the largest digital journal library in South Korea ChoKukSuhoTemp (talk) 03:57, 3 September 2023 (UTC)
Discussion Edit
BookBrainz series ID Edit
Represents | BookBrainz (Q56100780) |
---|---|
Data type | External identifier |
Domain | book series (Q277759) |
Allowed values | [0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12} |
Example 1 | Hainish Cycle (Q2328396) → e9ff65d6-4b45-4a94-907b-a4417287016a |
Example 2 | Foundation series (Q1564644) → 8d44b797-a51f-43d0-a8fc-4ec888ddf80a |
Example 3 | Asterix (Q42490) → 0b18f455-74c2-4378-9b58-0a28ae6d5e4f |
Source | https://bookbrainz.org/help |
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]. |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://bookbrainz.org/series/$1 |
See also | BookBrainz author ID (P2607), BookBrainz work ID (P7823), BookBrainz publisher ID (P8063) |
Motivation Edit
Completing the existing BookBrainz (Q56100780)'s properties: BookBrainz author ID (P2607), BookBrainz work ID (P7823), BookBrainz publisher ID (P8063). -- Maxlath (talk) 18:59, 6 September 2023 (UTC)
Discussion Edit
Support Sure why not. ArthurPSmith (talk) 20:26, 6 September 2023 (UTC)
Support 👌 –Shisma (talk) 17:33, 22 September 2023 (UTC)
BookBrainz edition ID Edit
Represents | BookBrainz (Q56100780) |
---|---|
Data type | External identifier |
Domain | version, edition, or translation (Q3331189) |
Allowed values | [0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12} |
Example 1 | MISSING |
Example 2 | MISSING |
Example 3 | MISSING |
Source | https://bookbrainz.org/help |
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]. |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://bookbrainz.org/edition/$1 |
See also | BookBrainz author ID (P2607), BookBrainz work ID (P7823), BookBrainz publisher ID (P8063), Wikidata:Property_proposal/BookBrainz_series_ID |
Motivation Edit
Completing the existing BookBrainz (Q56100780)'s properties: BookBrainz author ID (P2607), BookBrainz work ID (P7823), BookBrainz publisher ID (P8063), and Wikidata:Property_proposal/BookBrainz_series_ID. It would require more work to find instance of version, edition, or translation (Q3331189) examples with corresponding pages on BookBrainz, but some very likely already exist. -- Maxlath (talk) 19:22, 6 September 2023 (UTC)
Discussion Edit
IGI Global affiliate ID Edit
Description | identifier for an author on the IGI Global website |
---|---|
Data type | External identifier |
Domain | human (Q5) |
Example 1 | Eileen Trauth (Q114961624) → 1 |
Example 2 | Carmen Lamagna (Q26465606) → 405095 |
Example 3 | Bolanle Olaniran (Q95985175) → 1878 |
Example 4 | Mohammad Kaykobad (Q6892122) → 239364 |
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]. |
Formatter URL | https://www.igi-global.com/affiliate/-/$1 |
See also | Google Scholar author ID (P1960), ResearchGate profile ID (P2038), IGI Global Dictionary ID (P9982) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation Edit
IGI Global (Q648724) is an international academic publisher. These pages index the publications of an individual author published by the IGI Global with a short bio of the author. — Haseeb (talk) 09:40, 8 September 2023 (UTC)
Notified participants of WikiProject Academic Publisher — Haseeb (talk) 09:00, 9 September 2023 (UTC)
Notified participants of WikiProject Authority control — Haseeb (talk) 09:00, 9 September 2023 (UTC)
Discussion Edit
Support but the prop should be renamed to "IGI Global author ID". BTW there are more props to make, do you want to add more proposals? --Vladimir Alexiev (talk) 19:44, 11 September 2023 (UTC)
- Article ID, eg Linked data – the story so far (Q29301445) -> https://www.igi-global.com/article/-/37496
- Book ID, eg "Research Anthology on Implementing Sentiment Analysis Across Multiple Disciplines" -> https://www.igi-global.com/book/-/300811
- Chapter ID, eg "Optimizing Water Quality Sampling Through Application Of Real Time Ionic Concentration Regression Models" -> https://www.igi-global.com/chapter/-/224394
- Journal ID (or Venue ID? check some conferences), eg International Journal on Semantic Web and Information Systems (Q15759214) -> https://www.igi-global.com/journal/-/1092
- @Vladimir Alexiev, I actually don't know how useful the article ID or book ID will be. But, as the identifiers are unique, these properties can be created. — Haseeb (talk) 20:05, 11 September 2023 (UTC)
BISAC Subject Heading Edit
Description | Used in the North American market to categorize books based on topical content. They serve as a guideline for shelving books in physical stores and browsing books in online stores. |
---|---|
Represents | BISAC Subject Headings List (Q56646988) |
Data type | External identifier |
Domain | item |
Allowed values | [A-Z]{3}[0-9]{6} |
Example 1 | stamp collecting (Q856075) -> ANT044000 (named as "ANTIQUES & COLLECTIBLES / Stamps") |
Example 2 | space exploration (Q180046) -> SCI098020 (named as "SCIENCE / Space Science / Space Exploration") |
Example 3 | I Ching (Q181937) -> OCC038000 (named as "BODY, MIND & SPIRIT / I Ching") |
Source | https://www.bisg.org/BISAC-Subject-Codes-main , https://www.bisg.org/complete-bisac-subject-headings-list, https://www.editeur.org/files/Thema/20230301_BISAC%202022%20to%20Thema%201.5%20Mapping.xlsx |
Number of IDs in source | 5239 |
See also | Dewey Decimal Classification (P1036), Library of Congress Classification (P1149) |
Applicable "stated in"-value | BISAC Subject Headings List (Q56646988) |
Single-value constraint | no |
Distinct-values constraint | yes |
Wikidata project | WikiProject Books (Q8487081) |
Motivation Edit
WikiProject Books has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.
This is a major classification system for books.
- There is no official formatter URL since BISG doesn't have per-subject pages, but higher-level pages, eg https://www.bisg.org/science
- There are many third-party formatter URLs. Eg here are books about I Ching from 3 online book stores:
- BISG doesn't provide a free dump, but a full list of subjects is in the EDItEUR mapping excel (see above). The BISAC subject name is not in there, but the meaning can be understood from the mapping to EDItEUR Thema (which I'll propose next)
--Vladimir Alexiev (talk) 14:34, 12 September 2023 (UTC)
Discussion Edit
Support This looks really useful, love those 3rd party formatters! ArthurPSmith (talk) 17:58, 25 September 2023 (UTC)
EDItEUR Thema id Edit
Represents | EDItEUR Thema (Q122440155) |
---|---|
Data type | External identifier |
Domain | item |
Allowed values | [A-Z0-9-]+ |
Example 1 | Solar System (Q544) -> PGS |
Example 2 | Solar System (Q544) -> 1ZM (object has role: qualifier) |
Example 3 | zydeco (Q245296) -> 6XZ |
Example 4 | Berlin (Q64) -> 1DFG-DE-BE |
Source | https://www.editeur.org/151/thema |
Number of IDs in source | 8646 (reference https://www.editeur.org/files/Thema/1.5/v1.5_en/20230707_Thema_v1.5_en.xlsx) |
Expected completeness | always incomplete (Q21873886) |
Implied notability | Wikidata property for an identifier that suggests notability (Q62589316) |
Formatter URL | https://ns.editeur.org/thema/en/$1 (search formatter: https://ns.editeur.org/thema/en?search=$1) |
See also | Dewey Decimal Classification (P1036), Library of Congress Classification (P1149), Wikidata:Property_proposal/BISAC_Subject_Heading |
Applicable "stated in"-value | EDItEUR Thema (Q122440155) |
Single-value constraint | yes (with separator "object has role") |
Distinct-values constraint | yes |
Wikidata project | WikiProject Books (Q8487081) |
Motivation Edit
EDItEUR Thema is the major subject classification in the book industry. Codes starting with a digit are qualifiers, i.e. should not be used alone to classify a book. Unlike MeSH qualifier ID (P9341), I think it's easier NOT to make a distinct property for "qualifier" but to use the WD qualifier "object has role" to distinguish them when needed (see the example about "Solar system").
Here is the complete list of identifier patterns (d=digit, A=uppercase alpha), with counts:
20 A 145 AA 1125 AAA 1503 AAAA 451 AAAAd 47 AAAAdd 6 d 57 dA 48 dA-AA- 156 dA-AA-A 284 dA-AA-AA 122 dA-AA-AAA 61 dA-AA-AAAA 332 dAA 95 dAA-AA-A 15 dAA-AA-AA 478 dAAA 456 dAAA-AA-A 837 dAAA-AA-AA 1100 dAAA-AA-AAA 283 dAAA-AA-AAAA 22 dAAA-AA-AAAAA 2 dAAA-AA-AAAAAA 454 dAAAA 189 dAAAA-AA-A 159 dAAAA-AA-AA 51 dAAAA-AA-AAA 111 dAAAAA 20 dAAAAA-AA-A 16 dAAAAAA
Vladimir Alexiev (talk) 15:27, 12 September 2023 (UTC)
Discussion Edit
Support seems good to me. I was unsure about your "qualifier" case but I think you explained it well enough, this seems like an adequate solution. ArthurPSmith (talk) 19:29, 14 September 2023 (UTC)
ONIX Subject Scheme id Edit
Motivation Edit
Notified participants of WikiProject Authority control
An important codelist of subject schemes and identifier types used in the ONIX standard in the Publishing industry.
While not as rich as BARTOC ID (P2689) (doesn't include descriptive info about these schemes), it's a good list of 130 schemes that we should aim to include completely in Wikidata as external-ids. Vladimir Alexiev (talk) 16:02, 12 September 2023 (UTC)
Discussion Edit
Comment Example links: "Whoops! That page could not be found." --Kolja21 (talk) 22:29, 12 September 2023 (UTC)
Support I replaced the example links with the ones for the formatter URL in the template, these seem to work. ArthurPSmith (talk) 19:32, 14 September 2023 (UTC)
Question Would it make sense to generalize this property to include other lists as well (e.g. https://ns.editeur.org/onix/en/44 seems useful)? --1-Byte (talk) 14:53, 17 September 2023 (UTC)
Newman Numismatics Portal ID Edit
Description | Identifier for a person on the Newman Numismatics Portal website |
---|---|
Data type | External identifier |
Domain | human (Q5) |
Allowed values | [1-9]\d* |
Example 1 | Walter Breen (Q7965022) → 323 |
Example 2 | Don Taxay (Q5293600) → 1892 |
Example 3 | William H. Key (Q122338769) → 1137 |
Example 4 | Farran Zerbe (Q5436227) → 2089 |
Source | https://nnp.wustl.edu/library/people |
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]. |
Number of IDs in source | More than 3700 |
Expected completeness | eventually complete (Q21873974) |
Formatter URL | https://nnp.wustl.edu/Library/PersonDetail/$1 |
Robot and gadget jobs | Mix'n'Match ? |
Single-value constraint | yes |
Distinct-values constraint | yes |
Wikidata project | WikiProject Numismatics (Q10858447) |
Motivation Edit
Significant and reliable site for the biographies of notable numismatists.
[Proposal created at the request of User:DragonflySixtyseven]. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:14, 12 September 2023 (UTC)
Discussion Edit
ADVN ID (nl) – (Please translate this into English.) Edit
Description | Identifier in the authority database of ADVN |
---|---|
Data type | External identifier |
Template parameter | Person, or organisation |
Domain | People and organisations related to the Flemish Movement.
Examples: Vic Anciaux (Q2342905) Rode Kruis-Vlaanderen (Q2690605) |
Allowed values | (per|org)-[0-9]{6} |
Allowed units | 6 digits, preceded by per- (for people) or org- (for organisations) |
Example 1 | Vic Anciaux (Q2342905)ADVN IDper-000157 |
Example 2 | Rode Kruis-Vlaanderen (Q2690605)ADVN IDorg-006883 |
Example 3 | subject→value |
Source | https://data.advn.be/id/per-000157 (Vic Anciaux) https://data.advn.be/id/org-006883 (Rode Kruis Vlaanderen) |
Planned use | Contribute to linked open data: allow searches for information and sources in the ADVN database + enrich (and update) the ADVN database with cross-refences to other sources. |
Number of IDs in source | At the date of 2023-09-13 there are more than 3000 items ready to be registered. |
Expected completeness | always incomplete (Q21873886) |
Implied notability | Wikidata property for an identifier that suggests notability (Q62589316) |
Formatter URL | https://data.advn.be/id/$1 |
Robot and gadget jobs | Verify consistency, data gatering, error correction, delta processing (insert/merge operations). Link with other authority databases. |
See also | ISNI (P213), Enterprise number (Belgium) (P3376), ORCID iD (P496) |
Applicable "stated in"-value | ADVN | archive for national movements (Q2210067) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Wikidata project | ADVN | archive for national movements (Q2210067) |
Motivatie Edit
This property will enable the Flemish database of people and organisations to publish its data in Wikidata using the new external identifier. It can then link also to other databases like ISNI, ORCID, Belgian enterprise KBO number, etc. The target database is not yet operational, but is in development. Geertivp (talk) 19:44, 13 September 2023 (UTC)
Discussion Edit
Support. Beireke1 (talk) 10:44, 14 September 2023 (UTC)
Support. PVanPamel (talk) 17:35, 17 September 2023 (UTC)
Support. LiesbethL (talk) 12:25, 18 September 2023 (UTC)
Support. Pcladvn (talk) 12:31, 18 September 2023 (UTC)
Support. Ingert2022 (talk) 08:12, 19 September 2023 (UTC)
Support. LabDom (talk) 10:46, 26 September 2023 (UTC)
National Register of Monumental Trees ID Edit
Description | ID in the registry of monumental trees in the Netherlands |
---|---|
Data type | External identifier |
Allowed values | number |
Example 1 | Anne Frank Tree (Q49057) → 1686124 |
Example 2 | Monumental common lime tree in Sambeek (NL) (Q3528520) → 1679463 |
Example 3 | Holy Oak (Q2654077) → 1680745 |
Example 4 | Doolhoflaan (Q19013413) → 1684865 |
Source | https://bomen.meetnetportaal.nl/ |
Number of IDs in source | 15000 |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://bomen.meetnetportaal.nl/index.php?c=portal&mm=claim&m=custom&options=monumentale_bomen/claimformulier.xml&boomnr=$1 |
Motivation Edit
The Landelijk Register van Monumentale Bomen (Dutch registry of monumental trees) (Q64515875) is the database/inventory for monumental trees, groups of remarkable trees and tree lanes in the Netherlands, maintained by the Bomenstichting (Q2757544), a well known organisation in the Netherlands and the authority on trees in the country. After the creation of the property, we will add this identifier to all existing items about remarkable trees and will add other missing remarkable trees to Wikidata (and preferably also to Wikipedia and Commons). Romaine (talk) 22:01, 13 September 2023 (UTC)
Discussion Edit
Support. Perhaps it would be a good idea to use "Dutch (National) Register etc." as a name for the property. It is a Dutch database, and all the trees are in Holland. --Dick Bos (talk) 08:25, 14 September 2023 (UTC)
Support. A good option for all the dutch monumental trees WeeJeeVee (talk) 15:16, 14 September 2023 (UTC)
Support. —Ismael Olea (talk) 16:46, 14 September 2023 (UTC)
National Library of Albania ID Edit
Description | identifier of books |
---|---|
Data type | External identifier |
Allowed values | [1-9]\d{0,6} |
Example 1 | Q115914886 → 1 |
Example 2 | Q121834228 → 20 |
Example 3 | Q122586070 → 1537 |
Source | https://www.bksh.al/ |
Number of IDs in source | 450000 |
Expected completeness | always incomplete (Q21873886) |
Formatter URL | https://www.bksh.al/details/$1 |
Motivation Edit
As part of Wikidata:WikiProject Albania/National Library of Albania I'm importing books & authors (creating also items for Albanian given names and family names) of Albanian literature, and a property will be very useful reference for Wikidata items.--Liridon (talk) 09:00, 16 September 2023 (UTC)
Discussion Edit
Support. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:18, 16 September 2023 (UTC)
Support but, according to the data model of Wikidata:WikiProject Books, all imported items containing this property need to be instance of (P31)version, edition, or translation (Q3331189) and not instance of (P31)written work (Q47461344); please correct the examples and other items already imported. Thanks! --Epìdosis 10:07, 16 September 2023 (UTC)
Support obviously (ideally, we should have all national libraries...). Cheers, VIGNERON (talk) 06:20, 20 September 2023 (UTC)
Support can't believe it's not already here... ;-) --Teatroge (talk) 02:30, 22 September 2023 (UTC)
BAN ID Edit
Description | identifier for a place on the BAN |
---|---|
Represents | National Address Base (Q19942326) |
Data type | External identifier |
Domain | physical location (Q17334923) |
Allowed values | [1-9AB]{5}(_[1-9]{4})* |
Example 1 | rue Bollac (Q110264581) → 30006_0025 |
Example 2 | Aimargues (Q243915) → 30006 |
Example 3 | Paris street (Q19346993) → 35238_7090 |
Formatter URL | https://adresse.data.gouv.fr/base-adresse-nationale/$1 |
Notified participants of WikiProject France. 92.184.99.184 21:24, 19 September 2023 (UTC)
Support. Ayack (talk) 07:21, 20 September 2023 (UTC)
Société de l'histoire du protestantisme français ID Edit
Represents | Société de l'histoire du protestantisme français (Q3487967) |
---|---|
Data type | External identifier |
Domain | propriété |
Allowed values | [1-9]{6} |
Example 1 | Protestant Faculty of Theology in Paris (Q3064314) → 57718 |
Example 2 | Fédération française des associations chrétiennes d'étudiants (Q21008415) → 107296 |
Example 3 | Théodore Monod (Q956408) → 2945 |
Example 4 | Philippe Delamain (Q27064212) → 83664 |
Example 5 | Clément Marot (Q108926) → 3 |
Example 6 | Theodore Beza (Q314981) → 4 |
Example 7 | Claude Goudimel (Q497713) → 10 |
Source | https://shpf-collections.fr |
Formatter URL | https://shpf-collections.fr/Default/search.aspx?SC=DEFAULT&QUERY=Authority_id_idx:$1 |
Motivation Edit
Bonjour, La bibliothèque de la Société de l'histoire du protestantisme français (SHPF) (Q3487967) a mis la semaine dernière son catalogue d'archives en ligne. Serait-il possible de créer une nouvelle page Property: pour ajouter l'identifiant sur Wikidata et donner le lien des archives dans les Notices d'autorités sur Wikipédia ? C'est ma première demande de création de propriété, désolé si j'ai mal rempli le modèle. J'ai d'abord posé la question dans le Bistro (Topic:Xq7qadp93vgl8e7d) Merci, Hypsibius (talk) 16:20, 22 September 2023 (UTC)
- Bonjour @Hypsibius:,
- Globalement cela me semble plutôt bien parti.
- Pour être "idéal", serait-il possible de fournir :
- quelques exemples en plus ? (en particulier des exemples diversifiés, pour donner un meilleur aperçu du contenu ; là on a deux organisations, est-ce que ce ne sont que des organisations ? je vois aussi que les valeurs autorisées indiquées sont "[1-9AB]{6}" mais les deux exemples ne contiennent que des chiffres, aucune lettre)
- une liste de tout les identifiants ? (cela serait surtout utile pour faire l'alignement et l'import en masse dans Wikidata si/une fois la propriété créée).
- Cdlt, VIGNERON (talk) 10:06, 23 September 2023 (UTC)
- Bonjour,
- A mon avis, il y a sutout des auteurs, qu'ils soient humains ou personnes morales.
- Effectivement, on dirait bien qu'il n'y a que des chiffres finalement - mais je ne sais pas si c'est 6 maximum.
- Je ne travaille pas pour cette bibliothèque, mais on peut tenter demander la liste des identifiant par email, oui.
- Cordialement, Hypsibius (talk) 13:25, 25 September 2023 (UTC)
Discussion Edit
Bonjour, c'est toujours une excellente nouvelle quand une nouvelle grande bibliothèque de référence s'ouvre en ligne :)
Comment détermines-tu l'identifiant ? où le trouves-tu ? --Hsarrazin (talk) 17:07, 22 September 2023 (UTC)
- @Hsarrazin: il semble qu'on puisse trouver l'identifiant dans le code source de la page. Il faut chercher « Authority_id_idx ». Pamputt (talk) 17:39, 22 September 2023 (UTC)
- merci ! et j'ai vu aussi qu'on peut le trouver en glissant le curseur sur le lien d'une autorité... seul inconvénient, ces identifiants ne donnent pas accès à un fichier d'autorité (où on pourrait trouver des informations), mais aux notices liées à cette autorité...
- ça me semble un peu juste comme intérêt pour créer un identifiant dédié... --Hsarrazin (talk) 17:52, 22 September 2023 (UTC)
Support. Maxime 19:29, 22 September 2023 (UTC)
DBIL ID Edit
Description | identifier for the Latin American Left Biographic Dictionary |
---|---|
Represents | no label (Q122826888) |
Data type | External identifier |
Domain | human (Q5) |
Example 1 | Raymundo Gleyzer (Q979254) → gleyzer-raymundo |
Example 2 | Tristán Marof (Q7844232) → navarro-ameller-gustavo-adolfo |
Example 3 | Maria Werneck de Castro (Q9028894) → werneck-maria |
Source | https://diccionario.cedinci.org |
Implied notability | Wikidata property for an identifier that suggests notability (Q62589316) |
Formatter URL | https://diccionario.cedinci.org/$1/ |
Applicable "stated in"-value | no label (Q122826888) |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivación Edit
The dictionary contains curated biographies about numerous and relevant leaders of the Latin American left and labor movement Mr. Moonlight (talk) 04:19, 26 September 2023 (UTC)
Discussion Edit
Museum of Fine Arts, Bordeaux object ID Edit
Description | identifier for an artwork on the Museum of Fine Arts, Bordeaux website |
---|---|
Represents | Musée des Beaux-Arts de Bordeaux (Q954222) |
Data type | External identifier |
Domain | work of art (Q838948) |
Allowed values | .{36} |
Example 1 | Q120488655 → 17e104d8-cd2a-45c1-93f5-6f1dec7da7e6 |
Example 2 | Q121333814 → fd705f55-f94f-4d5b-ad4d-a10c4f1d58f7 |
Example 3 | Vanitas (Q119149975) → d58ab8d8-284e-4563-97f7-84f3e414c86f |
Number of IDs in source | 8250 |
Formatter URL | https://musba-bordeaux.opacweb.fr/r/$1 .{36} |
Single-value constraint | yes |
Distinct-values constraint | yes |
Motivation Edit
Requested by Uchroniste 40.
There is already 186 artworks with collection (P195) = Musée des Beaux-Arts de Bordeaux (Q954222) (https://w.wiki/7ZUt) and 17 of them already point manually to this website (with described at URL (P973), https://qlever.cs.uni-freiburg.de/wikidata/XefzeB). There is also a lot of files on Commons (under commons:Category:Collection of the Musée des Beaux-Arts de Bordeauxthat could benefit from this property).
Cheers, VIGNERON (talk) 13:00, 26 September 2023 (UTC)
Discussion Edit
Support +
Notified participants of WikiProject France, Maxime 13:14, 26 September 2023 (UTC)
Support proposant. Uchroniste 40 (talk) 13:31, 26 September 2023 (UTC)
Support. Thierry Caro (talk) 14:16, 26 September 2023 (UTC)
Support --Pierre André Leclercq (talk) 15:04, 26 September 2023 (UTC)
Support Jean-Fred (talk) 16:07, 26 September 2023 (UTC)