Property talk:P236

From Wikidata
Jump to navigation Jump to search


International Standard Serial Number (print or electronic)
DescriptionInternational Standard Serial Number, under the responsibility of ISO subcommittee ISO/TC 46/SC 9 (Q7669804)
RepresentsInternational Standard Serial Number (Q131276)
Data typeExternal identifier
Template parameter"ISSN" in en:template:infobox journal (Template:Infobox journal (Q13256340))
According to this template: periodicals: periodical literature (Q1002697)
According to statements in the property:
serial (Q2217301)
When possible, data should only be stored as statements
Allowed values\d{4}\-\d{3}(\d|X)
ExampleThe Guardian (Q11148)0261-3077 (RDF)
Nature (Q180445)0028-0836 (RDF) and 1476-4687 (RDF)
Format and edit filter validationAbuse filter #84
Formatter URL$1$1$1$1
Tracking: usageCategory:Pages using Wikidata property P236 (Q35048516)
See alsoCPPAP ID (P5968)
Proposal discussionProposal discussion
Current uses66,706
Search for values
[create] Create a translatable help page (preferably in English) for this property to be included here
Format “[0-9]{4}\-[0-9]{3}[0-9X]|: value must be formatted using this pattern (PCRE syntax). (Help)
List of this constraint violations: Database reports/Constraint violations/P236#Format, hourly updated report, SPARQL, SPARQL (new)
Distinct values: this property likely contains a value that is different from all other items. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P236#Unique value, SPARQL (every item), SPARQL (by value), SPARQL (new)
Type “serial (Q2217301): element must contain property “instance of (P31)” with classes “serial (Q2217301)” or their subclasses (defined using subclass of (P279)). (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P236#type Q2217301, SPARQL, SPARQL (new)
Qualifiers “applies to part (P518), start time (P580), end time (P582), language of work or name (P407), official name (P1448), distribution format (P437), named as (P1810): this property should be used only with the listed qualifiers. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P236#Allowed qualifiers, SPARQL, SPARQL (new)
Item “language of work or name (P407): Items with this property should also have “language of work or name (P407)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P236#Item P407, search, SPARQL, SPARQL (new)
Item “title (P1476): Items with this property should also have “title (P1476)”. (Help)
Exceptions are possible as rare values may exist.
List of this constraint violations: Database reports/Constraint violations/P236#Item P1476, SPARQL, SPARQL (new)
Pictogram voting comment.svg Invalid ISSN
ISSN that have wrong checksum (Help)
Violations query: SELECT ?item { { ?item wdt:P236 ?value } UNION { ?statement pq:P236 ?value . ?item ?p ?statement . ?prop wikibase:claim ?p } UNION { ?ref pr:P236 ?value . ?statement prov:wasDerivedFrom ?ref . ?item ?p ?statement . ?prop wikibase:claim ?p } . BIND(REPLACE(STR(?value), "-", "") AS ?nohyphen) . FILTER(STRLEN(?nohyphen) = 8) . BIND(xsd:integer(REPLACE(SUBSTR(?nohyphen, 8, 1), "X", "10")) AS ?last) . BIND(xsd:integer(SUBSTR(?nohyphen, 1, 1)) * 8 + xsd:integer(SUBSTR(?nohyphen, 2, 1)) * 7 + xsd:integer(SUBSTR(?nohyphen, 3, 1)) * 6 + xsd:integer(SUBSTR(?nohyphen, 4, 1)) * 5 + xsd:integer(SUBSTR(?nohyphen, 5, 1)) * 4 + xsd:integer(SUBSTR(?nohyphen, 6, 1)) * 3 + xsd:integer(SUBSTR(?nohyphen, 7, 1)) * 2 AS ?checksum) . BIND(?checksum - FLOOR(?checksum / 11) * 11 AS ?remainder) . FILTER(?remainder + ?last != 11) . FILTER(?remainder + ?last != 0) }
List of this constraint violations: Database reports/Complex constraint violations/P236#Invalid ISSN

Unique constraint[edit]

The unique constraint seems to be inappropriate here. It is unlikely that we will (typically) have distinct items for print vs online versions of a periodical, as the majority of the facts about both editions is the same - the main difference is that articles have two issued dates: first online and then in print. That difference is an attribute of the article, rather than of the periodical. John Vandenberg (talk) 00:27, 25 February 2014 (UTC)

11000 "single value" violations out of 28000 periodicals - all having two IDs: electronic + paper IDs. We need to suppress that constraint for now. Could be reinstated if there eventually exist a "one or two" constraint... LaddΩ chat ;) 23:26, 15 March 2014 (UTC)
{{Constraint:Single value}}

E-ISSN (electronic ISSN)[edit]

Looks like we need divide this property to two properties: electronic ISSN and paper ISSN. — Ivan A. Krestinin (talk) 08:09, 16 March 2014 (UTC)
I think the next step is to add a property for 'ISSN-L', which is constrained per the new (2007) ISO standard as having a single value for each journal. It will be very rare that we have two items with the same ISSN-L - so rare that the constraint exceptions list is sufficient to deal with them.
I have been thinking that perhaps the ISSNs should have a qualifier, instead of multiple properties, as it allows more flexibility.
I personally dont see the benefit in having distinct properties for electronic ISSN vs paper ISSN. Most of the time when people look up an ISSN, they dont care whether it is the ISSN or eISSN. The electronic version of the article (eISSN) and the digitised print version of the article (ISSN) are usually almost identical. However if someone puts together a well designed solution using multiple propertyies, I will support and help implement it.
Two issues to consider:
  1. Periodicals can also have CDROM ISSNs, which should probably be recorded on the main item for the journal. These are mostly given to conferences rather than journals, but Physical Review Letters (Q2018386) does have a CDROM ISSN.
  2. Periodicals can also have additional ISSNs (paper & electronic) for special editions, supplement, etc. These vary so much it is hard to say whether a rule can be written to say whether the special edition should a separate item or be part of the main item for the journal. Some supplements are very distinct works; others are only published once in place of a normal issue by the same team and most readers consider it to have been an odder-then-usual issue but not a separate work. However if they are a separate item, how do we link it to the main item, and should the special issue item have an ISSN-L property?
John Vandenberg (talk) 00:33, 18 March 2014 (UTC)

I think we should divide to ISSN, eISSN, and ISSN-L. Many bibliographic systems have that distinction, eg PubMed XML has:

  • Journal/ISSN with attribute @IssnType (Electronic | Print)
  • MedlineJournalInfo/ISSNLinking

--Vladimir Alexiev (talk) 11:50, 20 February 2019 (UTC)

too many resolvers[edit]

This prop has 4 formatter URL and 7 third-party formatter URL. I understand these different databases include different journal lists, but I need some guidance on "which is better" (what is their respective coverage).

@John Vandenberg, Ivan A. Krestinin: maybe you can help? Also asked at --Vladimir Alexiev (talk) 11:56, 20 February 2019 (UTC)