Property talk:P236
Latest comment: 6 months ago by Tacsipacsi in topic Resolver problem ?
Documentation
ISSN
International Standard Serial Number (print or electronic)
International Standard Serial Number (print or electronic)
[create Create a translatable help page (preferably in English) for this property to be included here]
List of violations of this constraint: Database reports/Constraint violations/P236#Format, hourly updated report, SPARQL
Type “serial (Q2217301), reference work (Q13136)”: item must contain property “instance of (P31)” with classes “serial (Q2217301), reference work (Q13136)” or their subclasses (defined using subclass of (P279)). (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/P236#Type Q2217301, Q13136, SPARQL
Qualifiers “applies to part (P518), start time (P580), end time (P582), language of work or name (P407), official name (P1448), distribution format (P437), subject named as (P1810), reason for deprecated rank (P2241), reason for preferred rank (P7452), publisher (P123), editor-in-chief (P5769), place of publication (P291), latest start date (P8555), earliest date (P1319), earliest end date (P8554), latest date (P1326), authority (P797), last update (P5017), series ordinal (P1545), alternative name (P4970)”: 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/P236#allowed qualifiers, SPARQL
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. Exceptions can be specified using exception to constraint (P2303). List of violations of this constraint: Database reports/Constraint violations/P236#Item P407, search, SPARQL
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/P236#Item P1476, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P236#Item P1476, SPARQL
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/P236#Item P31, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P236#Item P31, search, 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). List of violations of this constraint: Database reports/Constraint violations/P236#Single value, SPARQL
Item “country of origin (P495)”: Items with this property should also have “country of origin (P495)”. (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/P236#Item P495, search, SPARQL
Allowed entity types are Wikibase item (Q29934200), Wikibase MediaInfo (Q59712033): 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/P236#Entity types
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/P236#Unique value, SPARQL (every item), SPARQL (by value)
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/P236#Scope, SPARQL
Conflicts with “ISNI (P213)”: this property must not be used with the listed properties and values. (Help)
List of violations of this constraint: Database reports/Constraint violations/P236#Conflicts with P213, hourly updated report, search, SPARQL
Invalid ISSN
ISSN that have wrong checksum (Help)
Violations query:
List of this constraint violations: Database reports/Complex constraint violations/P236#Invalid ISSN
ISSN that have wrong checksum (Help)
Violations query:
SELECT ?item ?value #?checksum ?last ?remainder WHERE { { ?st ps:P236 ?value . } UNION { ?st pq:P236 ?value . } UNION { _:b1 pr:P236 ?value . ?st prov:wasDerivedFrom _:b1 . } 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 ) ?item ?p ?st . }List of this constraint violations: Database reports/Complex constraint violations/P236#Invalid ISSN
|
Pattern ^(fk\d{5})$ will be automatically replaced to https://digi.kansalliskirjasto.fi/sanomalehti/titles/\1/data and moved to described at URL (P973) property. Testing: TODO list |
|
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
| ||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
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)
- You can see how it is done in Acta Arithmetica. The restriction says it has to be a unique value except if there is one of the following qualificators: applies to part (P518), start time (P580), end time (P582), language of work or name (P407), distribution format (P437) or publisher (P123). For printed and online versions, you can use distribution format (P437) with printed matter (Q1261026) and online publication (Q1714118). Paucabot (talk) 10:21, 17 October 2020 (UTC)
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:
- 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.
- 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
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 https://en.wikipedia.org/wiki/Wikipedia_talk:WikiProject_Academic_Journals#ISSN_Resolvers --Vladimir Alexiev (talk) 11:56, 20 February 2019 (UTC)
The "official one" is https://issn.org/resource/ISSN/$1, the official documentation for URL/URI can be found at http://www.issn.org/understanding-the-issn/assignment-rules/issn-linked-data-application-profile/ (to be added as a reference for this resolver, but I can't do it - can someone do ?)
http://www.issn.cc seems to be dead.
Online ISSN and Print ISSN edit
The most popular choice to distinguish between online and print ISSN is to use
- distribution format (P437)printed matter (Q1261026) for print
- distribution format (P437)online publication (Q1714118) for online
as qualifiers:
select ?format ?formatLabel (count(?i) as ?count) (sample(?i) as ?sample) {
?i p:P236 [pq:P437 ?format].
SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}
group by ?format ?formatLabel
order by desc(?count)
Serials without ISSNs edit
Is there a way to denote a work that does not have an ISSN? For example the British journal The Electrical Engineer (Q105221968) appears not to have one (the unrelated but roughly contemporaneous New York The Electrical Engineer does). I set it to "no value" - is that right? Should there be a reference or "as of" qualifier? Inductiveload (talk) 14:06, 3 February 2021 (UTC)
Resolver problem ? edit
There seems to be a problem with resolving the URL. Is it only for me ? For example Problemy Polityki Społecznej. Studia i Dyskusje (Q96728398). Rendered correctly in page source but opens the Wikidata Main Page instead. Kpjas (talk) 07:41, 16 October 2023 (UTC)
- @Kpjas: It works for me. Did you try it in safe mode? If it’s broken without safe mode but works in safe mode, then the breakage is likely caused by a gadget or user script you enabled. —Tacsipacsi (talk) 08:47, 17 October 2023 (UTC)