Property talk:P3065

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

RERO ID (legacy)
identifier in the Library network of Western Switzerland's RERO database

Associated item	Library Network of Western Switzerland (Q3456783)
Applicable "stated in" value	RERO (Q19696495)
Has quality	VIAF component (Q26921380)
Data type	External identifier
Domain	human (Q5), organization (Q43229), political entity (Q16562419), work (Q386724), geographical feature (Q618123), social movement (Q49773), family (Q8436) or character (Q95074)
Allowed values	A\d{9}
Usage notes	In VIAF, the RERO id is the $35 field of the processed RERO record. The ID for works (resources) are prepended with the 01-R prefix; creators (agents/authors) with the 02-A prefix.
Example	Voltaire (Q9068) → A000173676 Emil Bessels (Q90898) → A024181746 The Netherlands Red Cross (Q16238073) → A011487825
Source	VIAF (note: this information should be moved to a property statement; use property source website for the property (P1896))
Formatter URL	https://viaf.org/en/processed/RERO$1 https://web.archive.org/web/*/http://data.rero.ch/$1
Related to country	Switzerland (Q39) (See 80 others)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Items with deprecated claims Usage history (total) Usage history (main statement) Chart by item creation date Map of people by place values: place of birth educated at work location residence place of death place of burial January 1st dates People with date of birth on January 1 People with date of death on January 1 People with both dates on January 1 Database reports/Constraint violations/P3065 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 193,372 Main statement 193,238 >99.9% of uses Qualifier 3 <0.1% of uses Reference 131 <0.1% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Distinct values: this property likely contains a value that is different from all other items. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P3065#Unique value, SPARQL (every item), SPARQL (by value)

Single value: this property generally contains a single value. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Johns Hopkins University (Q193727)
List of violations of this constraint: Database reports/Constraint violations/P3065#Single value, SPARQL

Type “human (Q5), organization (Q43229), political entity (Q16562419), work (Q386724), geographical feature (Q618123), social movement (Q49773), family (Q8436), character (Q95074)”: item must contain property “instance of (P31)” with classes “human (Q5), organization (Q43229), political entity (Q16562419), work (Q386724), geographical feature (Q618123), social movement (Q49773), family (Q8436), character (Q95074)” or their subclasses (defined using subclass of (P279)). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P3065#Type Q5, Q43229, Q16562419, Q386724, Q618123, Q49773, Q8436, Q95074, SPARQL

Item “instance of (P31)”: Items with this property should also have “instance of (P31)”. (Help)

List of violations of this constraint: Database reports/Constraint violations/P3065#Item P31, hourly updated report, search, SPARQL

Format “A\d{9}”: value must be formatted using this pattern (PCRE syntax). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P3065#Format, SPARQL

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P3065#Entity types

Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P3065#Scope, SPARQL

This property is being used by:

• ko:틀:위키데이터 속성 추적

---

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Pattern ^02-(A\d{9})$ will be automatically replaced to \1. Testing: TODO list

Discussion

Identifier for authors

The correct identifier for authors is 02-A00999999 (per [1][2]), NOT vtls009999999 which is an identifier for VTLS (Q7907618), not Library Network of Western Switzerland (Q3456783).

The data.rero.ch website doesn't always work, sometimes you get data, sometimes you get "No record found", but the URL is correct (proof). --Thibaut120094 (talk) 16:53, 30 June 2017 (UTC)

Is it okay to delete all the vtls identifiers? --Pasleim (talk) 21:48, 19 August 2017 (UTC)

Regarding the "No record found" entries, I have asked RERO directly. The answer was that there are two fields with "035 - System Control Number (R)" in the VIAF record. Take a look at this example: It contains field 035 twice. First one ist used by VIAF for link, but the correct field to use is the second one, beginning with A: "035 ‎‡a A003320701". For the very most entities both values are the same, for some they are different like in the example. In this case, the authority record has to be checked manually for the right identifier. --Sotho Tal Ker (talk) 19:41, 14 May 2018 (UTC)

@Pasleim : VTLS identifiers must be converted to the 02-A or 01-R format. --Thibaut (talk) 14:25, 22 January 2020 (UTC)

Added organization (Q43229) to allowed types

Since there were a lot of constraint violations due to use of this property in items about organizations, I have added organization (Q43229) to the allowed types. I do not see that RERO is limited to humans only. —MisterSynergy (talk) 11:41, 13 November 2017 (UTC)

Changed property constraint regex

I did update the property constraint regex to be more "exact". There is either 01-R OR 02-A, neither 01-A or 02-R. Also there are always 9 digits, not any number between 0 and 9. The new regex takes both into account, and a few wrong values have been already found. --Sotho Tal Ker (talk) 22:01, 5 April 2020 (UTC)

Small addendum: Some values for books or magazines do violate the new regex, but they did violate the old one aswell. I think it is better to keep those violations for now as they are currently very few and sometimes identifiers for books get added to humans, instead of the correct value. --Sotho Tal Ker (talk) 23:00, 5 April 2020 (UTC)

Rero bugging on a fr.wikipedia model

Hello,

By working with several GLAM employees today, I found out that the Authority model on fr.wikipedia has been giving error messages for the past two years or so when a rero number is added.

Here is an example, with a Swiss historian, Q59533639. When the following rero number : A003773184 (found on this VIAF page) is added on the correct entry of Modèle:Autorité, a message signalling that the number is incorrect appears.

Is there an issue going on with the Wikidata property?

Thanks for your support!--Flor WMCH (talk) 12:55, 4 October 2021 (UTC)

@Flor WMCH: The correct value is preceded by "02-", as stated in Property:P3065#P1793. Values of RERO and other VIAF members can be easily extracted from VIAF clusters through User:Bargioni/moreIdentifiers. --Epìdosis 14:58, 4 October 2021 (UTC)

New RERO+ identifiers

There has been some discussion at en:Template_talk:Authority_control#Does_RERO_need_an_update? about how this ID is not valid anymore and is being replaced with a new ID — Martin (MSGJ · talk) 08:42, 12 November 2022 (UTC)

@MSGJ: I think the answer from RERO reported in the en.wikipedia discussion implies we shouldn't do anything as of now:

• "The "old" RERO authority file with identifiers in the form of "02-A000173676" is not maintained and not publicly accessible any more." = this RERO ID (legacy) (P3065) is obsolete
• "Ideally, we should in the long term replace all RERO ID by IdRef ID: in our data as well as in Wikidata. The alignments are not finished yet, so a lot of our bibliographic data (in https://bib.rero.ch/ and in https://swisscovery.slsp.ch/) still has RERO IDs as references." = RERO will user IdRef ID (P269) and convert old IDs to IDREF/SUDOC IDs both in their database and in Wikidata
• "The identifier you proposed to put instead (https://bib.rero.ch/global/persons/2433193) is not persistent. We don't recommend to use it in Wikidata." = The IDs currently visible are not persistent, so we cannot create a new property for them

--Epìdosis 17:24, 12 November 2022 (UTC)

I agree with your analysis. I have also added (obsolete) to the label of this property — Martin (MSGJ · talk) 13:21, 2 March 2023 (UTC)

There is a proposal to create replacement property, please see Wikidata:Property proposal/RERO+ ID — Martin (MSGJ · talk) 10:04, 11 March 2024 (UTC)

Better understable instructions needed

Please coders add a better 'How to'-instruction that should pop up when someone edits the rero id into a biography. It's basically easy: user has to add '02-' to the value found in the VIAF database for any persons. But up to now the script only nags afterwards that the entry without 02- is wrong. --Just N. (talk) 19:15, 15 November 2022 (UTC)

legacy instead of obsolete

The info that goes with these ids is valid, so "obsolete" isn't that great a description. How about "legacy"? e 14:30, 11 January 2025 (UTC)

Problem with the statement: "RERO ID (legacy)"

If I start the parameter with "02-" as required, the program can't find the page when I click on the link:

Example: Albert Einstein, RERO ID (legacy) = 02-A003212458. When I click on it, it says: Page or resource not found! However, I don't get a formatting error in Wikidata.

If I omit the "02-" beforehand, I get a formatting error in Wikidata, but the link works:

Example: Klaus Peter Jantke, RERO ID (legacy) = A003420368. When I click on it, I get the correct VIAF page. Allexkoch (talk) 12:20, 13 March 2025 (UTC)

See above #New RERO+ identifiers. bdijkstra (overleg) 20:37, 28 March 2025 (UTC)

URL-Formatter does not work

In Michael Pohl (Q19796954) there is a RERO 02-A008932076 the URL-Formatter creates https://viaf.org/en/processed/RERO02-A008932076 but this does not work, it should create https://viaf.org/en/processed/RERO%7CA008932076 omitting the prefix "02-" --Wurgl (talk) 07:59, 1 August 2025 (UTC)

Indeed, the "02-" is superfluous when linking to VIAF. The only way to fix it without changing all identifiers is by using Q108047563. @ArthurPSmith: Could you kindly create an entry for this property in your tool? --Sotho Tal Ker (talk) 21:15, 1 August 2025 (UTC)

Reversing the {{Autofix}} will be sufficient to remove systematically "02-". --Epìdosis 22:19, 1 August 2025 (UTC)

Sure, though the "02-" was part of the original identifier, even if VIAF does not store it. If we really want to change the stored format, all the tools that add this property need to be updated aswell. Sotho Tal Ker (talk) 22:51, 1 August 2025 (UTC)

Someone changed the formatter, before it created a link to the web-archive, but this worked very seldom. --Wurgl (talk) 06:31, 2 August 2025 (UTC)

Changing systematically all the tools which add the ID will be very easy; I think in a few days everything will work fine. Epìdosis 07:01, 2 August 2025 (UTC)

The URLs do not seem to be working, I think the pipe | needs to be replaced by %7C. Kusma (talk) 11:14, 8 August 2025 (UTC)

| or %7C seems to depend on the Browser. Firefox may need %7C Chrome is happy with | --Wurgl (talk) 11:21, 8 August 2025 (UTC)

Safari does not work with |. Kusma (talk) 13:28, 8 August 2025 (UTC)