Property talk:P3308
Documentation
ID for “Things” (review subjects) on lib.reviews
Description | ID for 'Things' (review subjects) on lib.reviews | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Applicable "stated in" value | lib.reviews (Q27926115) | ||||||||||||
Data type | External identifier | ||||||||||||
Domain | Anything except for living people (note: this should be moved to the property statements) | ||||||||||||
Allowed values | Alphanumeric (note: this information should be moved to a property statement; use property format as a regular expression (P1793)) | ||||||||||||
Example | According to this template:
When possible, data should only be stored as statements | ||||||||||||
Source | https://lib.reviews | ||||||||||||
Formatter URL | https://lib.reviews/$1 | ||||||||||||
Formatter URN | urn:uuid:$1 — List of Uniform Resource Names (URN) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P3308#Conflicts with P31, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3308#Entity types
List of violations of this constraint: Database reports/Constraint violations/P3308#Scope, SPARQL
Change to URL structure
[edit]As of January 25, we use a new URL structure. We now only expose UUIDs through the URL if there is no human-readable label for a given review subject, and no longer use the "/thing" path for review subjects. If there is a label, we use a transformed (lower case, hyphenated, some characters excluded) version of the most recently added label as the canonical URL, e.g.:
Previous labels are preserved as redirects. We may sometimes end up removing redirects if they are unreasonable/misleading, but generally, disambiguation is done automatically by affixing numbers, e.g., -2, -3, at the point of creation.
Previous UUID-based URLs will still work. Indeed, if you look at the HTML source of the page above, you'll find the comment
<!-- permanent ID of this item: d93fc8ef-41c5-4007-a0e7-661acdbda23e -->
Both the URLs https://lib.reviews/d93fc8ef-41c5-4007-a0e7-661acdbda23e and https://lib.reviews/thing/d93fc8ef-41c5-4007-a0e7-661acdbda23e will redirect to the most recent canonical URL. Unlike the human-readable identifier, unless the item itself is removed, this ID will not change if any of the human-readable aliases need to be removed for any reason. I leave it up to the Wikidata community which identifiers should be added to the items here.--Eloquence (talk) 03:52, 11 February 2017 (UTC)
- Eloquence could you please review if this regular expression will find the id in any url pointing to the thing 🙃 --Shisma (talk) 10:26, 22 June 2021 (UTC)
- Shisma, close, but lib.reviews slugs are more tolerant than that - https://lib.reviews/section-31-abyss-(star-trek-deep-space-nine) , https://lib.reviews/hotel-tannhäuser and https://lib.reviews/if-on-a-winters-night,-four-travelers are all valid slugs. I think you'd be better off just breaking on a
?
to cut off any query string (there shouldn't be any, but still) and capturing every other character.--Eloquence (talk) 03:51, 29 June 2021 (UTC)
- Shisma, close, but lib.reviews slugs are more tolerant than that - https://lib.reviews/section-31-abyss-(star-trek-deep-space-nine) , https://lib.reviews/hotel-tannhäuser and https://lib.reviews/if-on-a-winters-night,-four-travelers are all valid slugs. I think you'd be better off just breaking on a