Property talk:P3430

From Wikidata
Jump to navigation Jump to search

Documentation

SNAC ARK ID
identifier for items in the Social Networks and Archival Context system
Associated itemSNAC (Q29861311)
Applicable "stated in" valueSNAC (Q29861311)
Data typeExternal identifier
Domain
According to this template: people, archives, libraries
According to statements in the property:
human (Q5), organization (Q43229) or vehicle (Q42889)
When possible, data should only be stored as statements
Allowed values\d*[A-Za-z][0-9A-Za-z]*
Usage notesNOT to be used for generic social networks (Twitter, Facebook, LinkedIn, etc)
ExampleEzra Pound (Q163366)w6650f4k
Conrad Aiken (Q380645)w62w357r
Sourcehttps://snaccooperative.org/
Formatter URLhttps://snaccooperative.org/ark:/99166/$1
Tracking: usageCategory:Pages with SNAC-ID identifiers (Q37412611)
Lists
Proposal discussionProposal discussion
Current uses
Total253,838
Main statement143,77656.6% of uses
Qualifier3<0.1% of uses
Reference110,05943.4% of uses
Search for values
[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/P3430#Unique value, SPARQL (every item), SPARQL (by value)
Format “\d*[A-Za-z][0-9A-Za-z]*: value must be formatted using this pattern (PCRE syntax). (Help)
List of violations of this constraint: Database reports/Constraint violations/P3430#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/P3430#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/P3430#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.)

Formatter URL & ID type[edit]

Moved here from my talk page - Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:54, 11 October 2017 (UTC)[reply]

I fixed the SNAC ID formatter URL to be "http://snaccooperative.org/view/$1" as the old one was not working. I was just talking to the National Archives SNAC liaison Dina Herbert and she said that should be the stable URL now. Thanks! -- Fuzheado (talk) 16:47, 11 October 2017 (UTC)[reply]

@Fuzheado: Please can you check that? The few I tested, including examples on the property page (after purging), don't seem to work. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:52, 11 October 2017 (UTC)[reply]
@Pigsonthewing: - Yikes we have a problem! Seems that SNAC now has a formal "SNAC ID" which is an all-numerical ID. The older string we were using is a permalink identifier, but not a proper SNAC ID. See this entry for an example [1] - We are storing "w6c53p0c" but the actual SNAC ID from them is 7750326. We probably need to do a massive bot sweep to convert them. -- Fuzheado (talk) 17:12, 11 October 2017 (UTC)[reply]
@Fuzheado: - The arks are still generated and considered to be the preferred link into snac. That formatter URL is "http://snaccooperative.org/ark:/99166/$1". The SNAC ID (the all-numeric ID in SNAC) is an internal identifier, which we may want to rename because of the confusion it has caused. -- Robbie Hott
@Deternitydx: - Thanks for the explanation. The revert to the ark: URL is justified. For now. But I'm still rather concerned – it seems like the simpler URL and the official-sounding "SNAC ID" is what is being put forth to the public as the user-friendly identifier. Is there a more complete explanation for when "permalink" should be used or when "SNAC ID" should be used?
The reason I'm concerned is that from the gallery shown on the front of http://snaccooperative.org/, if you click on an entry, you get sent to URL http://snaccooperative.org/view/24021813, and not http://n2t.net/ark:/99166/w60329t3. This would seem to indicate that the simpler URL is more highly visible. I'd like to find out more background before we make a decision either way, on whether to re-title our property P3430 SNAC ARK ID (P3430) to SNAC permalink or, in fact, convert IDs of the form w60329t3 to someething like 24021813 en masse, for about 148,000 entries. The latter is not hard, but it is a big change. Thanks. -- Fuzheado (talk) 20:33, 11 October 2017 (UTC)[reply]
@Fuzheado: - Thanks. Currently, we are unfortunately using two different URLs for the same content, but SNAC's governance wants to keep the additional perceived permanence provided by using Arks and the n2t Ark resolver. For now, we've simplified the nomenclature ("SNAC Ark ID" in Wikidata and "Ark ID" in our site), changes that should be reflected on snaccooperative.org in the next day or two. -- Robbie Hott
@Deternitydx, Pigsonthewing: - Thanks, this sounds like a reasonable direction. However, perhaps you can help with this - can we come up with a more specific "format as regular expression" for these Ark IDs? Right now it's a very generic [a-z0-9]+ but it seems like if we could provide a more rigid match, then our constraint reporting could warn folks if they inputted the wrong type of ID. Reason I ask is that right now I see it was not just me who made the error of using the all numerical "SNAC ID" from your site. I see a number of other instances of this error. Is that Ark identifier always 8 characters, and do they always start with "w6"? This way, we could have a more precise regexp like "^w6([a-z0-9]){6}" or the like, which would warn folks early if they're inputting something that doesn't conform. Thanks. -- Fuzheado (talk) 02:57, 12 October 2017 (UTC)[reply]
@Fuzheado: - Right now, our Arks all start with "w6" but I am unsure if they will continue to do so. That identifier is generated from the California Digital Library's EZID service. I can tell you that the 3.7M we have and the next 400k we assign will have that prefix, but after that we are switching to a different method for minting the Ark values which could produce different results. One safe regex would be to enforce at least one alpha character so that the all-numeric IDs will throw an error.
@Deternitydx, Pigsonthewing: Done. I've changed the property constraint: format constraint to reflect this. [2] -- Fuzheado (talk) 00:59, 24 October 2017 (UTC)[reply]

SNAC ID vs. SNAC Ark ID[edit]

The identifier we are currently using (SNAC Ark ID) is a subfield/subidentifier of an Archival Resource Key (Q2860403) (so this situation is similar to how digital object identifier (Q25670) is a part of Handle System (Q3126718)). It would be nice to be able to switch to "SNAC ID" but I am sure that would require a significant (and likely robotic) change. 50.53.21.2 23:36, 25 August 2019 (UTC)[reply]