Property talk:P1670

From Wikidata
Jump to navigation Jump to search

Documentation

Canadiana Authorities ID (former scheme)
obsolete identifier for authority control per the Library and Archives Canada. Format: 4 digits + 1 letter + 4 digits + optional F
DescriptionCanadiana Authorities control Number per the Library and Archives Canada
Applicable "stated in" valueLibrary and Archives Canada (Q913250)
Data typeExternal identifier
DomainNames, Titles (note: this should be moved to the property statements)
Allowed values\d{4}[A-Z]\d{4}F?
ExampleElizabeth M. Boyer (Q5362452)0101B0989
Piers Anthony (Q559409)0073L0378
Northwest Territories Department of Environment and Natural Resources (Q109289376)1016K8029
1016K8029F
Format and edit filter validationThe string seems to consists of four numerical digits, a letter and another four numerical digits. Some records have -E or -F endings to indicate English or French equivalents. These endings should be removed (link will take you to a combined record page).
Sourcehttp://www.collectionscanada.gc.ca/canadiana-authorities/index/
Formatter URLhttps://collectionscanada.gc.ca/canadiana-authorities/index/view?index_name=cdnAutNbr&search_text=$1&page=1&cdnAutNbr=$1
Tracking: usageCategory:Pages using Wikidata property P1670 (Q61034953)
Related to country Canada (Q16) (See 160 others)
See alsoCanadiana Name Authority ID (P8179)
Lists
Proposal discussionProposal discussion
Current uses
Total6,596
Main statement6,54799.3% of uses
Qualifier4<0.1% of uses
Reference450.7% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
Format “\d{4}[A-Z]\d{4}F?: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P1670#Format, hourly updated report, SPARQL
Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410), Wikimedia category (Q4167836): this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1670#Conflicts with P31, hourly updated report, SPARQL
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: Dictionary of Canadian Biography (Q838302), Northwest Territories Department of Environment and Natural Resources (Q109289376)
List of violations of this constraint: Database reports/Constraint violations/P1670#Single value, SPARQL
Distinct values: this property likely contains a value that is different from all other items. (Help)
List of violations of this constraint: Database reports/Constraint violations/P1670#Unique value, hourly updated report, SPARQL (every item), SPARQL (by value)
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/P1670#Item P31, hourly updated report, search, SPARQL
Qualifiers “subject named as (P1810), alternative name (P4970), reason for deprecated rank (P2241), reason for preferred rank (P7452): 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/P1670#allowed qualifiers, 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/P1670#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/P1670#Scope, SPARQL
Item “Canadiana Name Authority ID (P8179): Items with this property should also have “Canadiana Name Authority ID (P8179)”. (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/P1670#Item P8179, search, SPARQL

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


E/F postfix[edit]

Hello, as I understand 'E' or 'F' postfix mean language, English or French. ID without this postfix points to the same record. I have planes to remove this postfix from all items. Is there some opposition? — Ivan A. Krestinin (talk) 18:22, 8 March 2015 (UTC)[reply]

✓ DoneIvan A. Krestinin (talk) 19:57, 9 March 2015 (UTC)[reply]
If this was removed back in 2015, why is [EF] still part of the constraint? I'm trying to add 0017B9238‏ for Edward Kruk, and I get an error. Also, the link it generates isn't correct, with or without an E at the end. Nick Number (talk) 15:36, 13 February 2019 (UTC)[reply]

Allowed values[edit]

According to http://www.bac-lac.gc.ca/eng/services/canadiana/canadiana-authorities/Pages/canadiana-authorities.aspx#authorities there's an optional hyphen around the central [A-Z], so shouldn't the allowed values read as \d\d\d\d[A-Z,\-A-Z\-]\d\d\d\d instead? LeadSongDog (talk) 15:30, 4 October 2016 (UTC)[reply]

No. Otherwise this would complicate matching identifiers for distinct value constraints or finding existing items with a given value.
--- Jura 07:13, 5 October 2016 (UTC)[reply]

It can finish by a character[edit]

Hello, somme reference finish by a character. Ex : 1001C8015e 1001C8015e. Please, update the model. Thanks, --Bergil (talk) 08:31, 6 February 2018 (UTC)[reply]

Records that don't exist without 'E' or 'F' appended[edit]

There are instances where dropping the closing 'E' or 'F' (English/French) indicator does not seem to work. Please see:

and

How should these record(s) be recorded? Thank you-- TimK MSI (talk) 10:38, 30 October 2018 (UTC)[reply]

Important change[edit]

Notice on the website

"Library and Archives Canada (LAC) will no longer be updating the Canadiana Name Authorities Search; however, the site will continue to be searchable until March 2019. LAC stopped creating new authorities in AMICUS in September 2018 and will resume creating new authorities in OCLC’s integrated library management system, WorldShare Management Services (WMS), in late fall or early winter. English-language authority records will be created in the Name Authority Cooperative Program (NACO) file, and French-language authorities will be created in a separate file."

And more details FAQ :

"While many organizations around the world maintain French-language authority files, there is currently no international shared French-language authority program comparable to what is available in English through NACO. For this reason, LAC has now begun to maintain its separate French-language name authority file using the WMS Canadiana Name Authorities in French functionality. LAC’s French-language authority data will continue to be freely accessible at www.viaf.org."

--BeatrixBelibaste (talk) 18:23, 6 January 2019 (UTC)[reply]

That means, NONE LAC-ID is useful at this time, and nobody knows, if or when this will change and the system can be accessed again. Eisbaer44 (talk) 07:12, 28 August 2019 (UTC)[reply]

LAC Authority Reorganization[edit]

Vladimir Alexiev Jonathan Groß Andy Mabbett Jneubert Sic19 Wikidelo ArthurPSmith PKM Ettorerizza Fuzheado Daniel Mietchen Iwan.Aucamp Epìdosis Sotho Tal Ker Bargioni Carlobia Pablo Busatto Matlin Msuicat Uomovariabile Silva Selva 1-Byte Alessandra.Moi CamelCaseNick Songceci moz AhavaCohen Kolja21 RShigapov Jason.nlw MasterRus21thCentury Newt713 Pierre Tribhou Powerek38 Ahatd JordanTimothyJames Silviafanti Back ache AfricanLibrarian M.roszkowski Rhagfyr 沈澄心 MrBenjo S.v.Mering

Notified participants of WikiProject Authority control I want to second the above observation, and add something:

I've contacted Diane Beattie for possible clarifications:

  • Are all former LAC records in VIAF now available under code CAOONL?
  • How can the former Canadiana codes (eg 0101B0989) be migrated to the new coding (eg ncf10149073)? I guess an option is described at http://www.bac-lac.gc.ca/fra/services/catalogue-collectif-national/Pages/foire-questions-contrat-oclc.aspx "LAC will also keep French authority records in files that will be freely available to interested libraries and organizations on an FTP server. To obtain these files, contact LAC by writing to bac.servicesauxlibraries-libraryservices.lac AT canada.ca"
  • Is there a LAC authority search, or a site that displays short biographical info about each person?

--Vladimir Alexiev (talk) 09:17, 2 December 2019 (UTC)[reply]

As far as I can tell Canadiana Authorities have not been abandoned. What has changed is LAC has moved to a new online public access catalog (Q1982918); from AMICUS to Aurora (and Voilà for NUC; both are based on OCLC WorldShare Management Services): see A new library management system to share Canada’s published documentary heritage.

I have not been able to find an interface/search method similar to the old abandoned interface Canadiana Authorities anywhere including Aurora (where I would expect such).

The MARC records still use the same 016 - National Bibliographic Agency Control Number (R) field values as they always have (you can see in the 909 field this is the "LAC" identifier) but they do have new 001 - Control Number (NR) that is identified as "CAOONL". I expect this is just because the records are now maintained in a foreign database and the records are now mixed in with others (notice all the Canadiana Authorities CAOONL record numbers are prefixed with "ncf"; I bet their are other "CAOONL" records that are not).

OCLC WorldShare Record Manager help pages now mention Canadiana Authorities (with a recent "Last updated" date of 2019-09-26).

As such, I do not think there is anything wrong with our records in general. We do however, probably want to find a better way to link them to some sort of linked open data (Q18692990) interface. I hope LAC and OCLC can help provide this via their WMS-based Aurora OPAC or similar.

Uzume (talk) 20:05, 3 January 2020 (UTC)[reply]