Qualifiers “series ordinal (P1545), object of statement has role (P3831), affiliation (P1416), forgery after (P1778), affiliation string (P6424), URL (P2699), reason for deprecated rank (P2241), reason for preferred rank (P7452), object named as (P1932), subject has role (P2868), military or police rank (P410), author given names (P9687), author last names (P9688), different from (P1889), ORCID iD (P496), sex or gender (P21), ISNI (P213), statement supported by (P3680), applies to people (P6001)”: this property should be used only with the listed qualifiers. (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/P2093#allowed qualifiers, SPARQL

Conflicts with “instance of (P31): human (Q5), album (Q482994)”: this property must not be used with the listed properties and values. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Songs of Disappearance: Australian Bird Calls (Q110036257)
List of violations of this constraint: Database reports/Constraint violations/P2093#Conflicts with P31, search, SPARQL

Type “work (Q386724), item of collection or exhibition (Q18593264)”: item must contain property “instance of (P31)” with classes “work (Q386724), item of collection or exhibition (Q18593264)” 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/P2093#Type Q386724, Q18593264, SPARQL

Allowed entity types are Wikibase item (Q29934200), Wikibase MediaInfo (Q59712033), Wikibase lexeme (Q51885771): 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/P2093#Entity types

Scope is as qualifier (Q54828449), 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/P2093#Scope, SPARQL

Format “(?i)((?!redaktionen).)*”: 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/P2093#Format, SPARQL

This property is being used by: hy:Կաղապար:Տիեզերական գիտարշավ en:Template:Academic-written review/testcases ast:Plantía:Llibru commons:Template:Wikidata Infobox/core, commons:Template:Structured Data es:Plantilla:Wikidata Infobox id:Templat:Wikidata infobox, id:Templat:Kotak info Wikidata/inti mw:Template:Wikidata Infobox/core mr:साचा:विकिडाटा माहितीचौकट/core, mr:साचा:विकिडेटा माहितीचौकट/core ur:سانچہ:خانہ معلومات ویکی ڈیٹا/کور, ur:سانچہ:Wikidata Infobox/core q:fr:Modèle:Wikidata Infobox/core de:Vorlage:Wikidata Infobox/core gu:ઢાંચો:Wikidata Infobox/core ta:வார்ப்புரு:Wikidata Infobox/core hi:साँचा:Wikidata Infobox/core sv:Mall:Wikidata Infobox/core s:zh:Template:Wikidata Infobox/core ckb:داڕێژە:Wikidata Infobox/core pt:Predefinição:Wikidata Infobox/core jv:Cithakan:Infobox manuscript ku:Şablon:Wikidata Infobox/core mnw:ထာမ်ပလိက်:Wikidata Infobox/core s:bn:টেমপ্লেট:উইকিউপাত্ত তথ্যছক/মূল d:Template:Wikidata Infobox/core no:Mal:Wikidata Infobox/core s:ban:Mal:Infobox manuscript, s:ban:Mal:Wikidata Infobox/core ban:Mal:Wikidata Infobox/core lv:Veidne:Wikidata Infobox/core voy:shn:ထႅမ်းပလဵတ်ႉ:Wikidata Infobox s:hi:साँचा:Wikidata Infobox/core gl:Modelo:Academic-written review/uso ms:Templat:Kotak info pangkalan data biologi, ms:Templat:Kotak info pangkalan data biologi/kotak pasir ps:کينډۍ:Wikidata Infobox/core cbk-zam:Plantilla:Wikidata Infobox/core Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Duplicate between author and short author name at a given position in an authoring list
Identical P1545 for both a P50 and a P2093 statement (Help)
Violations query: select ?item ?interval where { ?item p:P2093/pq:P1545 ?interval ; p:P50/pq:P1545 ?interval . } LIMIT 1000
List of this constraint violations: Database reports/Complex constraint violations/P2093#Duplicate between author and short author name at a given position in an authoring list

Pattern ^(.*)ü(.*)$ will be automatically replaced to \1ü\2. Testing: TODO list

Pattern ^(.*)ö(.*)$ will be automatically replaced to \1ö\2. Testing: TODO list

Pattern ^(.*)ä(.*)$ will be automatically replaced to \1ä\2. Testing: TODO list

Pattern ^(.*)é(.*)$ will be automatically replaced to \1é\2. Testing: TODO list

Pattern ^(.*)á(.*)$ will be automatically replaced to \1á\2. Testing: TODO list

Pattern ^(.*)ø(.*)$ will be automatically replaced to \1ø\2. Testing: TODO list

Pattern ^(.*)ã(.*)$ will be automatically replaced to \1ã\2. Testing: TODO list

Pattern ^(.*)ó(.*)$ will be automatically replaced to \1ó\2. Testing: TODO list

Pattern ^(.*)ç(.*)$ will be automatically replaced to \1ç\2. Testing: TODO list

Pattern ^(.*)ë(.*)$ will be automatically replaced to \1ë\2. Testing: TODO list

Pattern ^(.*)è(.*)$ will be automatically replaced to \1è\2. Testing: TODO list

Pattern ^(.*)Ã¥(.*)$ will be automatically replaced to \1å\2. Testing: TODO list

Pattern ^(.*)æ(.*)$ will be automatically replaced to \1æ\2. Testing: TODO list

Pattern ^(.*)ú(.*)$ will be automatically replaced to \1ú\2. Testing: TODO list

Pattern ^(.*)ñ(.*)$ will be automatically replaced to \1ñ\2. Testing: TODO list

Pattern ^(.*)'(.*)$ will be automatically replaced to \1'\2. Testing: TODO list

Pattern ^(.*)ö(.*)$ will be automatically replaced to \1ö\2. Testing: TODO list

Pattern ^(.*)é(.*)$ will be automatically replaced to \1é\2. Testing: TODO list

Pattern ^(.*)á(.*)$ will be automatically replaced to \1á\2. Testing: TODO list

Pattern ^(.*)í(.*)$ will be automatically replaced to \1í\2. Testing: TODO list

Pattern ^(.*)’(.*)$ will be automatically replaced to \1'\2. Testing: TODO list

Pattern ^&NA;$ will be automatically replaced to somevalue. Testing: TODO list

(A) Using search

Try Special:Search/"John Doe" haswbstatement:P31=Q13442814

(B) Using search limited to string used in value

Try Special:Search/haswbstatement:"P2093=John Doe" haswbstatement:P31=Q13442814

(C) Using search limited to string used in value excluding papers that already have author (P50)=John Doe (Q302057)

Try Special:Search/haswbstatement:"P2093=John Doe" -haswbstatement:P50=Q302057

(D) Using Wikidata query server

See #Author name search query below

search by author

https://author-disambiguator.toolforge.org/

search by paper

https://author-disambiguator.toolforge.org/work_item.php?id=Q40115913

missing related authors

https://scholia.toolforge.org/author/Q66672198/missing

#Author name strings 
SELECT ?item ?itemLabel
{
  ?item wdt:P2093 "Jane Doe" .
  SERVICE wikibase:label { bd:serviceParam wikibase:language "en". }
}

Note: change the string "Jane Doe" to the name you wish to search for, retaining the quote marks. The matching must be precise, so the example above would not find values like "Jane Q. Doe" or "J Doe".

Is this property intended for only temporary use, to be replaced author (P50) as soon as someone gets around to it? If so, maybe this should be set up so that all uses are constraints violations, so that it shows up as a "thing to be done" on the reports. --Yair rand (talk) 12:12, 13 October 2015 (UTC)Reply

It's probable that we will never be able to replace all instances of author name string (P2093) with author (P50), since some citations and sources simply do not provide enough information to say for sure which Wikidata item to map an author string to. For cases where the mapping can be done, P2093 is indeed meant to be temporary. In terms of signalling constraint violations, this means that there's merit in doing it, but once there are too many unmappable cases on the list, it becomes less usable. --Daniel Mietchen (talk) 12:51, 13 October 2015 (UTC)Reply

Maybe a unique constraint? --- Jura 09:09, 14 October 2015 (UTC)Reply

Not a bad idea Jura, but I doubt it is that easy. I worked with a professor who wrote his name "S. Johansson". That is probably the most common combination of names in Sweden. I had the advantage to just go to his office and ask him if he was the author of an article, but I soon learned which subjects he wrote about. -- Innocent bystander (talk) 14:35, 26 November 2015 (UTC)Reply

Let's see what it does. If it ends up just outputting loads of "Smith J" .. we can remove it.

Q21521425 has just two Johansson ;) --- Jura 15:20, 26 November 2015 (UTC)Reply

I regard this property as temporary-as-possible: When the author item has been identified we use author (P50) and then erase the associated author name string (P2093). Currently, Magnus Manske's resolver at https://tools.wmflabs.org/sourcemd/new_resolve_authors.php does not delete the associated author name string (P2093), but has previously done so. Shouldn't we ask Magnus Manske to change it back? The presence of both author name string (P2093) and author (P50) for the same author confuses both Magnus Manske's resolver as well as our Scholia when normalizing for the number of coauthors and searching for not-yet-identified author items, see, e.g., The page https://tools.wmflabs.org/scholia/author/Q21504196/missing list authors string, some which have already been identified. @Magnus Manske: What is your opinion? I am under the impression that you (and the rest of us) do not know what the consensus is? — Finn Årup Nielsen (fnielsen) (talk) 15:19, 11 January 2018 (UTC)Reply

There are previous discussion at WikiProject Source MetaData and the Magnus Manske's commit is here. Given that his resolver is already moving the information from author name string (P2093) to the qualifier object named as (P1932) I think we will loose no information by removing author name string (P2093) with we have a author (P50) match. — Finn Årup Nielsen (fnielsen) (talk) 13:18, 12 January 2018 (UTC)Reply

author name string (P2093) should not be removed unless there is a object named as (P1932) match. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:38, 12 January 2018 (UTC)Reply

If an item has both

• a author name string (P2093) statement and
• a author (P50) statement

for the same series ordinal (P1545) and

the author (P50) statement also has

• a object named as (P1932) statement and
• a reference,

then I think the author name string (P2093) statement should be removed. --Daniel Mietchen (talk) 00:19, 10 February 2018 (UTC)Reply

Is this just intended for publications? On items about authors it could also be useful to be able to indicate the common short name(s) of that author. Say, on Larissa Bravina (Q24522527), to indicate that "L. Bravina" is a short name. Could we use the same property, or should we create a new one for that use case? Danmichaelo (talk) 22:02, 10 June 2016 (UTC)Reply

Not sure. Have you looked at the difference in usage of official name (P1448) and nickname (P1449)? Would the latter suit your needs? --Daniel Mietchen (talk) 19:36, 15 June 2016 (UTC)Reply

Having thought about this a bit more, I like the idea of broadening the scope of the property to be applicable on items about people as well. The usage on items about papers is almost reciprocal to that on items about people — when we change a author name string (P2093) statement to a author (P50) statement on a paper item, we should perhaps check whether the short author name from that P2093 statement is already listed as P2093 statement on the item about the author, and add it if not (this way, we could keep track of all people who have authored stuff and have been referred to as, say, "J Smith"). The item about that particular paper could also serve as a reference for the P2093 statement on the item about the author. --Daniel Mietchen (talk) 23:49, 30 June 2016 (UTC)Reply

Just broadened the scope to include people as well as publications. Feel free to help updating descriptions in more languages, I could only update a few. Danmichaelo (talk) 20:45, 18 November 2017 (UTC)Reply

Couldn't we just use short name (P1813) on items for people?
--- Jura 20:48, 18 November 2017 (UTC)Reply

I added a constraint that reflects how it was meant to be used. What do you think?
--- Jura 18:39, 19 November 2017 (UTC)Reply

Wouldn't we need the same for, e.g., editors?

To my understanding, this may also be useful when an author changed name. author (P50) would yield the current name of the author, and author name string (P2093) could then be used to indicate the name as it appears on the paper? Or should that rather be done with a qualifier on the author (P50) (which?) --Chire (talk) 08:08, 11 October 2017 (UTC)Reply

You have object named as (P1932) for that purpose, yes. P2093 is the lazy version of P50. When you do not know anything about "A Smith" use P2093 instead of P50 with a specific item. Normally editors are easier to identify since they are fewer than the authors are. -- Innocent bystander (talk) 14:45, 11 October 2017 (UTC)Reply

Using a mix of editor (P98) for a Wikidata-known editor and this (P2093) for Wikidata-unknown editors on Global Warming of 1.5°C: IPCC Special Report on impacts of global warming of 1.5°C above pre-industrial levels in context of strengthening response to climate change, sustainable development, and efforts to eradicate poverty (Q123675901) gave the unknown editors as authors and the known editor as an editor with w:cite Q in w:Special Report on Global Warming of 1.5 °C. So it seems to me that a separate property for strings for Wikidata-unknown editors is also needed: I don't see how w:cite Q can decide that "author or editor strings" should be editors without that. (Of course, the alternative would be to create Wikidata items for all the Wikidata-unknown editors ...) Boud (talk) 04:27, 5 December 2023 (UTC)Reply

How can I search items with this property for a specific name? DGtal (talk) 11:43, 26 November 2017 (UTC)Reply

See Wikidata:Contact the development team#Articles not searchable.
--- Jura 12:18, 26 November 2017 (UTC)Reply

Yes; using SPARQL. See the query I just added, near the top of this page. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:51, 26 November 2017 (UTC)Reply

• In the meantime, this possible using Special:Search. No complex syntax required. --- Jura 09:46, 4 December 2018 (UTC)Reply

For scientific literature but many other types of works too, authors write contributions under some affiliation. As such, I would welcome affiliation (P1416) as allowed qualifier (one or more) on author name string. Has this been discussed in the past? Do people foresee significant issues with this? --Egon Willighagen (talk) 12:58, 5 February 2018 (UTC)Reply

 Support affiliation is an immutable property of an author a document, at a time its bibliographic record is deposited, as a result it makes a ton of sense to allow its use as a qualifier in a bibliographic record. Of course, the author item itself (if it exists) can represent affiliations with additional temporal qualifiers.--DarTar (talk) 17:58, 5 February 2018 (UTC)Reply

 Support, on the understanding it gets transferred to the item about the author, if one is created. The only potential issue, at that point, is confusion or duplication with P1416 and properties like employer (P108), sponsor (P859), etc. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:34, 5 February 2018 (UTC)Reply

It's good you bring up that last point, which is one of the reasons why I am interested in it. It's fairly common to publish a paper under a past (or even future) affiliation, while not formally being employed by that affiliation anymore (or yet). Particullarly, many post-docs are well-known with this phenomenon, finishing up papers from previous one/two-year positions. --Egon Willighagen (talk) 05:49, 6 February 2018 (UTC)Reply

This may be a good idea. I do not see any problems with it, except that we should ask Magnus to copy the qualifier to P50 for his resolver, so that any work on this is not in vain. — Finn Årup Nielsen (fnielsen) (talk) 16:56, 9 February 2018 (UTC)Reply

@Magnus Manske:, where should I file a feature request to copy affiliation information when your tools convert a 'author name string' to 'author'? --Egon Willighagen (talk) 11:07, 13 February 2018 (UTC)Reply

OK, thanks everyone. I have added the qualifier, following what author (P50) already had. --Egon Willighagen (talk) 11:07, 13 February 2018 (UTC)Reply

I updated the allowed qualifier. All current uses of subject has role (P2868) should be using object of statement has role (P3831) instead. Sample values: editor (Q1607826), translator (Q333634), contributor (Q20204892). See Wikidata:Project_chat#Author_Qualifiers for discussion. --- Jura 17:44, 13 October 2018 (UTC)Reply

Hi!

Is this property supposed to be used only for academic articles and related topics? It seems like a good fit for paintings (and other artworks), where we know the creator's name (or some string) but don't have a better match. At the same time, the expected property for those is creator (P170) not author (P50), so maybe a parallel "creator name string" property would be a better fit. --Reosarevok (talk) 12:17, 17 January 2019 (UTC)Reply

@Reosarevok : Good question! I have recently started using it to indicate songwriter credits as they appear on labels, as they sometimes differ from what's official/correct and also to record misspellings.@Jc86035 : Moebeus (talk) 17:41, 17 January 2019 (UTC)Reply

@Reosarevok, Moebeus: I think it would be appropriate to propose a new property, although alternatively this property could be redefined to "creator name string" and the labels and descriptions reset (after a discussion at the project chat – I don't think it would be appropriate to do it without wider consensus). Jc86035 (talk) 17:49, 17 January 2019 (UTC)Reply

For the record: Wikidata:Property proposal/creator name string was not successful/withdrawn because object named as (P1932) can be used. --Marsupium (talk) 09:52, 1 April 2019 (UTC)Reply

How do we deal with different writing systems? I mean, qualifier P:P2440 could be fine, but please notice for example that the transliteration of 杜若わか would be Kakitsubata Waka instead of Waka Kakitsubata (Japanese naming order is reversed) so it doesn't seem to fit very well. Any ideas?--Sakretsu (talk) 11:35, 9 May 2019 (UTC)Reply

• Please create an item for the author and replace P2093 with author (P50). --- Jura 12:02, 9 May 2019 (UTC)Reply

See Wikidata:Request a query/Archive/2019/08#Authors most cited with no entry in Wikidata --- Jura 15:59, 20 August 2019 (UTC)Reply

The QLever alternative works well for this query: Query Karl Oblique (talk) 13:21, 25 January 2024 (UTC)Reply

I would propose wider use. I dont think so, there is a reason to limit this just for publications. We have images and we need a property author without the need of creating their item (which is even not possible). So should we propose for graphic works new property? That does not make sense if there is already one. Juandev (talk) 15:50, 5 September 2019 (UTC)Reply

I want to import some data from sites, some of these sites have some identifiers for authors, but maybe not enough to disambiguate the author. Currently though the only options for author identifiers is all or nothing, either you have the author, or you just put the string. I would like a third option, I want to be able to add the metadata to the author name string as qualifiers.

So for example, we have: Why modern open source projects fail (Q83809965)author name string (P2093)Marco Tulio Valente. Currently there is no item for Marco Tulio Valente that I can find, and sometimes even if you can find it, there is ambiguity. So now I just add the string and that is that.

However, I do also know a couple of other things about Marco Tulio Valente:

• Marco Tulio ValenteDBLP author ID (P2456)o/MarcoTuliodeOliveiraValente
• Marco Tulio ValenteORCID iD (P496)0000-0002-8180-7548

If I could add these as qualifiers to Why modern open source projects fail (Q83809965)author name string (P2093)Marco Tulio Valente then it would be pretty handy if someone later on makes an item for Marco Tulio Valente.

My proposal is to change this property to allow this use case and more specifically to allow qualifiers on this property that are instance of (P31)Wikidata property for authority control for people (Q19595382). Iwan.Aucamp (talk) 10:04, 20 May 2020 (UTC)Reply

The Source MetaData WikiProject does not exist. Please correct the name.

Notified participants of WikiProject Authority control

WikiProject Wikidata for research has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.

• Why not create items? --- Jura 10:07, 20 May 2020 (UTC)Reply
  • @Jura1: For this case I actually don't want to spend the time to create the items by hand, and I don't have some way to automate it, but adding a qualifier is not that much effort and would help future work significantly. I also think this would constitute a semantically correct use of qualifier. Iwan.Aucamp (talk) 10:17, 20 May 2020 (UTC)Reply
•  Comment I see now ORCID iD (P496) is allowed as qualifier. But this is still needed for cases where ORCID iD (P496) is NOT known (or does not exists) but other identifiers is known, as is the case for Why modern open source projects fail (Q83809965)author name string (P2093)Jailton Coelho, for which I know is Jailton CoelhoDBLP author ID (P2456)https://dblp.org/pid/166/1612 and Jailton CoelhoSemantic Scholar author ID (P4012)37127134. Either way that ORCiD is already allowed seems to suggest the general idea is okay. Iwan.Aucamp (talk) 10:17, 20 May 2020 (UTC)Reply
  • Seems to have been added by error. I don't see any discussion about it. Accordingly I removed it. --- Jura 10:31, 20 May 2020 (UTC)Reply
• In general, we don't want people to dump data into Wikidata without taking time to properly format it. --- Jura 10:28, 20 May 2020 (UTC)Reply
  • So if we had to define a general approach then, would it be:
    • If you have no author identifiers: don't create author items, just add string.
    • If you have author identifiers:
      • If an item with those identifiers exists: add data to it.
      • If an item with those identifiers does not exists: create new item and add identifiers there.

Won't this result in excessive amount of duplicate items? I guess maybe it is okay. Iwan.Aucamp (talk) 12:05, 20 May 2020 (UTC)Reply

Why would it create duplicates? --- Jura 08:48, 21 May 2020 (UTC)Reply

It seems that author data from Bulletin of the Seismological Society of America (Q15716527) is downloaded with ONLY the first author with their first initials. I don't fully understand this SourceMD tool, but it's not pulling all the authors' names. I tried to update this and I'm getting "As an anti-abuse measure..." saying we're throttling your editing.

1. Can I get the brakes removed?
2. Why is this data downloaded incorrectly?

Oh! This post was throttled for this same reason!! Thanks. Trilotat (talk) 03:15, 4 September 2020 (UTC)Reply

A name may have a dash. I got for format warning at Disentangling neocortical alpha/beta and hippocampal theta/gamma oscillations in human episodic memory formation (Q108016977), so we should remove that constraint. — Finn Årup Nielsen (fnielsen) (talk) 16:14, 9 August 2021 (UTC)Reply

@Fnielsen:author name string (P2093) can be Latin script (Q8229), Chinese (Q7850), kana (Q187659), Korean (Q9176), Arabic (Q13955) and so on. The format as a regular expression (P1793) is not suitable this Property. Please remove it.--Nostalgiacn (talk) 16:41, 9 August 2021 (UTC)Reply

I'm thinking it would be useful to be able to add contact info for authors of items (probably theses and dissertations mainly, maybe for authors who only wrote a single article) to allow people to contact the author where there is an "author name string" in an item, but no associated "author" item. It seems to me like the simplest way would be to make email address (P968) an allowed qualifier in the author name string. Thanks to Infopetal for the suggestion on the Slack Wikidata channel, and thank you for thoughts and discussion. Emwille (talk) 14:10, 11 May 2022 (UTC)Reply

Following this request for comments, the French label now includes the male and the female form. PAC2 (talk) 06:13, 18 June 2022 (UTC)Reply

Who is notable enough to have an article with a DOI but is only list as text not as a property?

∑ 100 items.

Back ache (talk) 13:57, 31 January 2024 (UTC)Reply

This property strikes me as a rather bab idea… it’s now used >130 million times, while author (P50) is at only 30 million. The purpose seems to be to allow mass imports by bots of data without the hassle of investing the effort to make the data actually useful within the working paradigm of WD. I, too, have gigabytes of files scraped from the web. Can I get a property blob of text to add items for each line? Karl Oblique (talk) 17:08, 23 February 2024 (UTC)Reply

I think it is very useful for references, to name a journalist or book author who might not be otherwise notable. But for scientific papers I agree it's preferable to have items for the authors as most people would consider researchers notable, this will greatly improve the linking of the data too. Infrastruktur (talk) 18:22, 23 February 2024 (UTC)Reply

This can be used specifically for historical authors that cannot be otherwise identified (e.g. because of their use of pseudonym) and therefore lack their own Wikidata entry but can still be assigned an assumed sex or gender based on their known name or pseudonym. ISGV (talk) 12:39, 15 March 2024 (UTC)Reply

Think of an old building with a long history and many authors of different centuries. There is one bunch of authors for a 2010s rebuild (here's the reference), another for the original construction in 1905 (here's another reference) - surely these should be kept separate and properly attributed to their times... - ? Retired electrician (talk) 09:41, 20 August 2024 (UTC)Reply

1. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T000395
2. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0900007
3. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T002994
4. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T005241
5. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1802727
6. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T006322
7. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1900985
8. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1400059
9. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T010469
10. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0400197
11. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T2254027
12. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T2216770
13. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1803851
14. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T014884
15. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T015773
16. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1201251
17. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1603504
18. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0802175
19. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1601956
20. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T019332
21. ↑ ^{21.0 21.1} https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T2071543
22. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.2001470
23. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0700804
24. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1200190
25. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T021220
26. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T021653
27. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T023075
28. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T023846
29. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0600169
30. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0700094
31. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0800454
32. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0600175
33. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.2001547
34. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T028396
35. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T029134
36. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T029151
37. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0800503
38. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T030680
39. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0800531
40. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T031794
41. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.2001821
42. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1602270
43. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0700111
44. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1700353
45. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T036993
46. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T037306
47. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.2000465
48. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0900356
49. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0400512
50. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T039345
51. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1800606
52. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1400913
53. ↑ ^{53.0 53.1} https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T039703
54. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T2089269
55. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T041434
56. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T042950
57. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T046377
58. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0100479
59. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1802383
60. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1200506
61. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1501244
62. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1302009
63. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0300289
64. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0600381
65. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0100581
66. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1602448
67. ↑ ^{67.0 67.1} https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T059273
68. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.2062626
69. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1701363
70. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T2073281
71. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T063991
72. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0700618
73. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0100730
74. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1800941
75. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1002271
76. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1601325
77. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T069909
78. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1900174
79. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1900915
80. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1401163
81. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0801839
82. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T075559
83. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0801335
84. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.2001679
85. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1500609
86. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0401086
87. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0200287
88. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T080537
89. ↑ ^{89.0 89.1} https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1602796
90. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1803010
91. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T085216
92. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T086176
93. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.2001874
94. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1601673
95. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0401011
96. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0700559
97. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.1302524
98. ↑ https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/ANB/9780198606697.ARTICLE.0700334
99. ↑ ^{99.0 99.1} https://api.crossref.org/v1/works/http://dx.doi.org/10.1093/GAO/9781884446054.ARTICLE.T092601