Property talk:P2704
Documentation
identifier for a film or television work, edit or manifestation, in the Entertainment Identifier Registry
List of violations of this constraint: Database reports/Constraint violations/P2704#Single value, SPARQL
10\.5240/([0-9A-Z]{4}-){5}[0-9A-Z]|
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P2704#Conflicts with P31, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P2704#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.) |
|
Discussion
editFormatter URL
editSuggested reference URL for the formatter URL: http://eidr.org/about-us/, this cannot be added without login, also see Property talk:P356#EIDR. It's not a general DOI resolver. –2.247.247.18 04:17, 18 September 2017 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Actually http://eidr.org/about-us/#how isn't good enough as reference URL, forget it. (same user:) 2.247.247.233 19:36, 8 October 2017 (UTC) |
Wrong format ?
editWhen trying to determine the value of URN formatter (P7470) for this property, I noticed that the part "10.5240/" isn't included. It seems this property should have been defined differently. --- Jura 19:03, 30 October 2019 (UTC)
@Kam Solusar: what do you think? --- Jura 12:48, 1 November 2019 (UTC)
- I'm not quite familiar with the topic of URNs, so I'm not sure I can really give a qualified opinion on it. Reading RFC 7972, it seems the namespace ID is "eidr", so the URNs consist of the part "urn:eidr:", the EIDR prefix "10.5240" and the EIDR-suffix (the rest of the ID). And because it's a special character, the slash needs to be replaced by a colon. Which I guess means we can't simply use the IDs we currently sstore to create proper URNs via URN formatter (P7470), because of the slash after "10.5240", which would need to be replaced by a colon to make it work. I'm not sure if we have a way to do regex operations in such cases. So the way to fix that would probably be to not store the "10.5240/" part and make if part of the formatter URL (P1630) and URN formatter (P7470). But that seems a bit problematic since the property already exists in its current form for over 4 years now.
- Additionally while the 10.5240 prefix is currently the standard, the document also notes "The only value of EIDR-PREFIX currently in use is "10.5240". Additional prefix values conforming to the EIDR-PREFIX syntax might be introduced by EIDR Association in the future.". Which again means that excluding the "10.5240" part from the IDs and only adding them in the formatter URL could potentially backfire if they ever add a new prefix. --Kam Solusar (talk) 15:46, 1 November 2019 (UTC)
- @Kam Solusar: Looks like I mixed this up with another identifier. Sorry about that. As 10.5240 is actually mentioned even for urn, I think we should keep it. That some conversion is needed ("/" to ":") shouldn't be much of an issue. --- Jura 17:10, 1 November 2019 (UTC)
Mix'n'match
editNot sure where to post this, but thanks to whoever tweaked and improved this mix'n'match catalog I originally added. :) Trivialist (talk) 01:10, 8 November 2020 (UTC)
Finding podcasts
editEIDRs are under-used for podcasts, this a list of things to search for to find them