Property talk:P3029
Latest comment: 1 month ago by Jheald in topic URL format
Documentation
UK National Archives ID
identifier for a person, family or organisation, in the UK's National Archives database
identifier for a person, family or organisation, in the UK's National Archives database
[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/P3029#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). List of violations of this constraint: Database reports/Constraint violations/P3029#Single value, SPARQL
Type “human (Q5), group of humans (Q16334295), legal person (Q3778211), religious community (Q2742167)”: item must contain property “instance of (P31)” with classes “human (Q5), group of humans (Q16334295), legal person (Q3778211), religious community (Q2742167)” 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). Known exceptions: Fort George (Q1426707), Ede & Ravenscroft (Q5336719), Pipewell Abbey (Q1362788), Business Design Centre (Q7373586)List of violations of this constraint: Database reports/Constraint violations/P3029#Type Q5, Q16334295, Q3778211, Q2742167, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3029#Format, hourly updated report, SPARQL
Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)
List of violations of this constraint: Database reports/Constraint violations/P3029#Scope, hourly updated report, 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/P3029#Entity types
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Note: Not to be confused with the old-style IDs, used in en:Template:NRA, which now redirect to pages using these new IDs.
URL format
editIs there a way to link https://discovery.nationalarchives.gov.uk/details/r/D7719833 to Percy Towns Armstrong (Q63155558)? It doesn't seem to have the right URL format, i.e., /r/ instead of /c/. Ghouston (talk) 10:39, 5 April 2020 (UTC)
- @Pigsonthewing, Mr impossible: I have the same problem with http://discovery.nationalarchives.gov.uk/details/r/C1356 and Committee for Compounding with Delinquents (Q5152924). Can you help? - PKM (talk) 01:23, 23 May 2021 (UTC)
- At present, no. We could change the formatter URL from
https://discovery.nationalarchives.gov.uk/details/c/$1tohttps://discovery.nationalarchives.gov.uk/details/$1, but we would need a bot to update all the current "c" values. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:18, 23 May 2021 (UTC)- Yes, I'm afraid we use different prefixes for different kinds of database entry. /c is for a record creator (person, organisation etc.), /r for a record and /a for an archive (but we have separate archon codes for these so it's not so much of an issue). Tbh we are likely to have to rewrite all of these in the next two years because we're moving to a completely new URL schema - a much better one but it's still churn. --Mr impossible (talk) 14:39, 24 May 2021 (UTC)
- I've had the same problem with https://discovery.nationalarchives.gov.uk/details/r/C1083 for an organisation, Royal Ordnance Factory. I think we should address both the scope and url format by accepting the ID can be for anything in the archive and rewriting the entries to quote the prefix letter. @Mr impossible what is the status of the new URL schema you mentioned? Vicarage (talk) 20:59, 24 May 2024 (UTC)
- Yes, I'm afraid we use different prefixes for different kinds of database entry. /c is for a record creator (person, organisation etc.), /r for a record and /a for an archive (but we have separate archon codes for these so it's not so much of an issue). Tbh we are likely to have to rewrite all of these in the next two years because we're moving to a completely new URL schema - a much better one but it's still churn. --Mr impossible (talk) 14:39, 24 May 2021 (UTC)
- @Ghouston, Pigsonthewing, Vicarage: I hit this as well with Carlisle Citadel Station Committee (Q130265838) -> https://discovery.nationalarchives.gov.uk/details/r/C12286
- I've forced the link on the item to work by stating the ID as
../r/C12286, and I've adjusted the format constraint (I hope correctly) to allow this, a workaround that we've occasionally used elsewhere. Not especially pretty, but should function. Jheald (talk) 11:31, 9 September 2024 (UTC)
Scope constraint too limited
editThe ship Batavia (Q30603082) has a valid National Archives page, but is flagged because 'Batavia currently isn't: human, group of humans, legal person. This is too restrictive given the National Archives cover a very wide of subjects. Vicarage (talk) 09:16, 12 September 2022 (UTC)