Property talk:P3218

From Wikidata
Jump to navigation Jump to search

Documentation

Auñamendi ID
identifier of an item in Auñamendi Encyclopaedia
Descriptionidentifier of an item in Auñamendi Encyclopaedia
RepresentsBasque surname (Q3342913)
Associated itemAuñamendi Eusko Entziklopedia (Q2873219)
Data typeExternal identifier
Domainitems... things... stuff... (note: this should be moved to the property statements)
Allowed values(|ee)[1-9]\d*(|/[1-9]\d*)
[1-9]\d*
ExampleEstanislao de Urquijo y Landaluce (Q8843105)135044
Elías Salaverria (Q8775239)120266
Toribio Altzaga (Q11952194)9338
Marijane Minaberri (Q12263083)79184
Formatter URLhttp://aunamendi.eusko-ikaskuntza.eus/artikuluak/artikulua.php?id=en&ar=$1
http://aunamendi.eusko-ikaskuntza.eus/artikuluak/artikulua.php?id=eu&ar=$1
http://aunamendi.eusko-ikaskuntza.eus/artikuluak/artikulua.php?id=fr&ar=$1
http://aunamendi.eusko-ikaskuntza.eus/artikuluak/artikulua.php?id=es&ar=$1
http://www.euskomedia.org/aunamendi/$1
Robot and gadget jobsthere are several values harvestable with harvesttemplates tool to start with something
Related to countryFlag of Spain.svg Spain (Q29) (See 64 others)
Lists
Proposal discussionProperty proposal/Auñamendi ID
Current uses4,814
Search for values
[create] Create 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.
List of this constraint violations: Database reports/Constraint violations/P3218#Single value, SPARQL, SPARQL (new)
Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P3218#Unique value, SPARQL (every item), SPARQL (by value), SPARQL (new)
Format “[1-9]\d*”: value must be formatted using this pattern (PCRE syntax). (Help)
List of this constraint violations: Database reports/Constraint violations/P3218#Format, hourly updated report, SPARQL, SPARQL (new)
Scope is: the property must be used by specified way only (Help)
List of this constraint violations: Database reports/Constraint violations/P3218#scope, hourly updated report, SPARQL (new)
This property is being used by:

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


Language selection[edit]

Some articles in Auñamendi are both in basque language and spanish language, some are only in spanish (numbers) and some only in basque (ee+numbers). When we use this property for authority control in basque Wikipedia we can put an ee before the numbers, but this will only work with articles that are both in basque language and in spanish language. If the articles is only in basque, we will find a link like eeee+number and if the articles is only in spanish language we will find a link like ee+number that simply isn't working. Could we imagine a solution for this? -Theklan (talk) 18:11, 24 January 2017 (UTC)

I have made a change Basque Wikipedia so in Authority Control template will appear both basque language and spanish language article links (it takes the number for spanish article, and puts an ee before the number for completing the basque article link. It works fine for those items that have the property data in format number, but doesn't work well for those that already have the data with the ee before the number. Is a way to automatically delete the ee before the number in those items that already have it? Lainobeltz (talk) 10:57, 25 January 2017 (UTC)
Can you then add one of the Basque examples to the examples of this property? ChristianKl (talk) 11:42, 25 January 2017 (UTC)
If the "ee" is deleted in those items, the formatter url http://www.euskomedia.org/aunamendi/$1won't be valid with those only-in-basque-items (now: 13 out of ~1008?). Well, they'll work fine in eu.wikipedia but not in es.wikipedia nor wikidata. I ask myself if it would not be possible writing a template or module such as "when the identifier starts with ee -> do this", "if not -> do that". Any way, there would still be a broken link to the basque version of the article in eu.wikipedia with the items available in Spanish but not in Basque, whether this "ee-issue" is resolved or not.
Other options are
1) using, somehow, a qualifier (applies to part (P518)? language of work or name (P407)? ...?) storing the languages an article is available in (then the identifier should be stored always without the prefix "ee"):
"language of work or name (P407) -> Spanish" or "language of work or name (P407) -> basque". If no qualifier at all... it could be supposed it's a "bilingual" entry.
2) Or... splitting P3218 in two properties (Auñamendi in Spanish (this one minus the 13 ee-items) and Auñamendi in Basque), with most of their identifiers overlapping, though. Pretty extreme solution. Strakhov (talk) 13:48, 25 January 2017 (UTC)
Now the authority control is using two boxes, one with http://www.euskomedia.org/aunamendi/ee$1 formater for basque article and other with http://www.euskomedia.org/aunamendi/$1 formater for spanish article. Here some examples: Jose Migel Barandiaran, that has both basque and spanish article in Auñamendi, Jesus Gaztañaga, that has no article in basque, and Maialen Lujanbio, that has article in both spanish and basque, but formater doesn't work because the "ee" is already in the data. They are many articles in Auñamendi that have spanish article but not basque; I don't now any example that has basque article but not spanish. I think the better solution is to delete the "ee" in the data that has it, and do the work in basque wikipedia to workaround the basque/spanish issue. By now the template presents both links wether basque article exists or not, untill we find a way to detect if the basque article exists Lainobeltz (talk) 07:51, 26 January 2017 (UTC)

Formatter url removed[edit]

I've removed the formatter url, since they have changed the url. They still use the same numerical identifier, but have introduced a creepy alphabetic part in between. The ID's are still useful as authority control though, so they shouldn't be removed. Strakhov (talk) 23:47, 2 July 2017 (UTC)

@Strakhov: In fact, it's useless, as it does not allow to search anything in their fancy website. I mean, by no means the id is useful anymore. Although it's kept in the URL, the alphabetic part in-between is mandatory and the knowledge of what we call an ID is not needed or useful. --Discasto (talk) 10:01, 3 July 2017 (UTC)
@Discasto: Yes, it's useful as an "unique" identifier. In the same way Bien de Interés Cultural (BIC) code (P808) it's useful to us (no searches, no urls, no nothing with it in www.mecd.gob.es, just... a identifier in a database). It has lost most of its value, though. Strakhov (talk) 23:28, 5 July 2017 (UTC)
And... with the old formatter url and the identifier ...a bot operator may try to recover some old-version-links in Wayback Machine (Q648266) and copying them to described at URL (P973). Anyway, I've made a backup of the id's. Strakhov (talk) 23:46, 5 July 2017 (UTC)
Hi, I can't see the last point you mention. Goint to the Wayback Machine would recover the known (now useless) URL, not the current one. As far as I can see, there's no way to get new URL's in an automated way. Am I missing anything? --Discasto (talk) 08:05, 6 July 2017 (UTC)
I meant (precisely) getting the old one (not useless, if it were useless Wayback Machine wouldn't exist..). It's still a url with an encyclopaedic entry... describing the item. And we can store it (using described at URL (P973)). Anyway, it seems old formatter url works fine now, as a redirect. They fixed their mess. :) Strakhov (talk) 09:21, 6 July 2017 (UTC)