Property talk:P6394

Documentation

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

ELNET ID
identifier assigned by the ELNET consortium of Estonian libraries. Format: 7 digits, "x" or another digit

Associated item	ELNET Consortium(Q12361408)
Applicable "stated in"value	ERRR(Q105754767)
Has quality	VIAF component(Q26921380)
Data type	External identifier
Allowed values	[0-9]{7}[0-9x] (string starting 7 digits, then either another digit or "x")
Example	Eeva Heinaru(Q24545716)→11174882 Eve Naanuri(Q60606534)→12410998 Arne Sellin(Q60606544)→11169746
Formatter URL	https://viaf.org/processed/ERRR|$1
Related to country	Estonia(Q191)(See 33 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 Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P6394 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 14,961 Main statement 14,953 >99.9% of uses Qualifier 3 <0.1% of uses Reference 5 <0.1% of uses
Search for values

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

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

Exceptions are possible as rare values may exist.Exceptions can be specifiedusingexception to constraint(P2303).
List of violations of this constraint:Database reports/Constraint violations/P6394#Single value,SPARQL

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 specifiedusingexception to constraint(P2303).
List of violations of this constraint:Database reports/Constraint violations/P6394#Unique value,SPARQL (every item),SPARQL (by value)

Format “[0-9]{7}[0-9x]”:value must be formatted using this pattern (PCRE syntax). (Help)

List of violations of this constraint:Database reports/Constraint violations/P6394#Format,hourly updated report,SPARQL

Allowed entity types areWikibase 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 specifiedusingexception to constraint(P2303).
List of violations of this constraint:Database reports/Constraint violations/P6394#Entity types

Scope isas 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 specifiedusingexception to constraint(P2303).
List of violations of this constraint:Database reports/Constraint violations/P6394#Scope,SPARQL

Pattern^a([0-9]{7}[0-9x])$will be automatically replaced to\1. Testing:TODO list

After formatter URL edit each link using it returns 404 Document not found

@Jahl de Vautban:after your edithttps://www.wikidata.org/w/index.php?title=Property:P6394&diff=prev&oldid=2191167993each link using the formatter URL returns 404: Document not found OCLC SRW/SRU ServerFriedrich Schultz(talk)06:45, 12 October 2024 (UTC)

@Friedrich Schultz:thanks for the ping. My edit back then was to fix what you got otherwise witha11174882.However things have changed yet again and now the initialaseem to have been droped from the identifer as11174882correctly resolve. If @Epìdosis:can confirm my analysis I can launch a batch tonight to remove theaon every item. —-Jahl de Vautban(talk)08:10, 12 October 2024 (UTC)

@Jahl de Vautban:I confirm your analysis: on October 6 VIAF replaced ERRR IDs starting with "a" with IDs without "a"; I have now consequently adapted the property removing "a" from the examples and from the constraints; I have also enabled an autofix that will fix in a few days all the existing IDs (it is better to use the autofix instead of QuickStatements, because removing and readding the IDs would lose their references, which are not fundamental, but I think it would be anyway preferrable to keep them). --Epìdosis08:17, 12 October 2024 (UTC)

So:

VIAF contributor ERRR ID overview - format and value

When	formatter	example result not encoded	example result encoded
2019-01-24[1]day of property creation	https://viaf.org/processed/ERRR|$1	https://viaf.org/processed/ERRR|a11174882	https://viaf.org/processed/ERRR%7Ca11174882
2024-06-29[2]value with a	https://viaf.org/processed/ERRR$1	https://viaf.org/processed/ERRRa11174882	https://viaf.org/processed/ERRRa11174882
2024-10-12[3]value without a	https://viaf.org/processed/ERRR$1	https://viaf.org/processed/ERRR11174882	https://viaf.org/processed/ERRR11174882

@Jahl de Vautban:"re My edit back then was to fix what you got otherwise with [https://viaf.org/processed/ERRR%7Ca11174882 a11174882]" - what did you got?

@Epìdosis:1) re "I confirm your analysis" - the following text does not match - "on October 6 VIAF replaced ERRR IDs starting with" a "" - the formatter edit didn't remove "a". 2) Wherefrom did you take "October 6"?Friedrich Schultz(talk)18:21, 12 October 2024 (UTC)

October 6 comes from the history of a few VIAF clusters that I have checked randomly, e.g.https://viaf.org/viaf/12149542594800300759/:in all cases it was visible that on October 6 the ID starting with "a" was removed and the ID without "a" was added. The formatter URLs with and without | both work as of now (https://viaf.org/processed/ERRR11174882andhttps://viaf.org/processed/ERRR%7C11174882); "a" has been removed not from the formatter URL (which, I confirm, did not contain it) but from the ID themselves.Epìdosis07:56, 13 October 2024 (UTC)

@Friedrich Schultz:ah interesting, probably the|isn't understood the same way by all browsers and some aren't/weren't able to process it, resulting in an error saying that the URL contained an unauthorized character. I'm not able to reproduce the error on the computer though (it does appears from time to time on mobile), and double checking on a cluster confirm that there is indeed this|,though it doesn't appear to be mandatory for the URL to resolve; anyway, I have reverted my edits. --Jahl de Vautban(talk)18:35, 15 October 2024 (UTC)