Coding rules - Revision history

Nils Duepont: /* Technical variable names */

2025-05-12T09:06:49Z

‎Technical variable names

2024-09-12T19:15:19Z

‎Technical rules

2024-08-19T11:54:21Z

‎Technical variable names

2024-06-05T19:32:47Z

‎Citation

2024-05-31T20:07:30Z

‎Conceptual agreements

2024-05-31T19:54:12Z

‎Conceptual agreements

2024-05-31T19:53:21Z

2024-05-31T19:51:03Z

‎Citation

2024-05-31T19:49:51Z

‎Citation

2024-05-31T19:48:05Z

‎Regional fragmentation

@@ Line 57: / Line 57: @@
 |Immigrant social rights
 |isr_
 |}

@@ Line 20: / Line 20: @@
 ==== Country codes ====
 WeSIS makes use of the entity codes defined by the [http://www.correlatesofwar.org/ Corrrelates of War] project (COW). See the entire list and additional notes on the [[Country_codes|country codes]] page.
 ==== Technical variable names ====

@@ Line 79: / Line 79: @@
 |Geography
 |geo_
 |}

@@ Line 144: / Line 144: @@
 Indicator names (and hence page titles) shall ''not'' be capitalized. For general guidelines please refer to Wikipedia's [https://en.wikipedia.org/wiki/Wikipedia:Simplified_Manual_of_Style Manual of Style] as well.
-== Citation ==
+== Citations ==
 WeSISpedia applies the citation style of the ''American Political Science Review'' in line with the American Political Science Association's [https://connect.apsanet.org/stylemanual/ official style guide]. The style uses the author-date system for in-text citations. It is used in the following format: (Author Year, Pages). There is no comma between the author and the year whereas mass citations are separated with a semicolon.

@@ Line 104: / Line 104: @@
 == Conceptual agreements ==
 ==== Regional fragmentation ====
@@ Line 111: / Line 120: @@
 * consistency, e.g., in case there are breaks due to changes in statehood like colonies becoming independent states or regime break down;
 * resources, e.g., the decision how many subnational entities need to be coded to (better) grasp the regional variation.
 ''For WeSIS it was agreed that''
 # the ''default'' is to collect data for the ''most populous entity today''.
-# projects may deviate from this rule for reasons grounded in the specificity of the focal policy or scheme. If they do so, they are obliged to justify and document their decision.
+# Projects may deviate from this rule for reasons grounded in the specificity of the focal policy or scheme. If they do so, they are obliged to justify and document their decision.
 # If they deviate from the default, projects are still encouraged to invest resources and collect data for the most populous entity today which already gives first hints about the actual variation.
 Any deviation from the default has to be documented in WeSISpedia as follows:

@@ Line 120: / Line 120: @@
 Any deviation from the default has to be documented in WeSISpedia as follows:
-# The indicator description shall include a note that regional fragmentation is present.
+* The indicator description shall include a note that regional fragmentation is present.
-# The section on "Coding rules" shall state which subnational entity is used to "represent" the focal country in the indicator's time-series.
+* The section on "Coding rules" shall state which subnational entity is used to "represent" the focal country in the indicator's time-series.
-# When preparing the data for upload to WeSIS, the [[Optional_column_names|optional column]] "comment" shall be used to state the presence of regional fragmentation, e.g., "There is regional fragmentation. Data refers to entity XYZ".
+* When preparing the data for upload to WeSIS, the [[Optional_column_names|optional column]] "comment" shall be used to state the presence of regional fragmentation, e.g., "There is regional fragmentation. Data refers to entity XYZ".
 If the projects invest the resources to also code additional entities (e.g. the most popoulos entity today), they have to decide which data is used to “represent” the focal country in the main indicator’s time-series. They can then upload further indicators containing only the data for the additional entities and document and name them accordingly. For example,

← Older revision		Revision as of 19:53, 31 May 2024
Line 1:		Line 1:
−	In order to ensure consistency for the data in WeSIS and in the documentation in WeSISpedia, several coding rules ~~and~~ documentation standards have been established.	+	In order to ensure consistency for the data in WeSIS and in the documentation in WeSISpedia, several coding rules, documentation standards and conceptual agreements have been established.

	__TOC__		__TOC__

@@ Line 142: / Line 142: @@
 The citation style is readily available as a template in Citavi and RefWorks and can be downloaded for [https://www.zotero.org/styles/american-political-science-association Zotero], [https://endnote.com/downloads/style/american-political-science-review EndNote] or [https://csl.mendeley.com/styleInfo/?styleId=http%3A%2F%2Fwww.zotero.org%2Fstyles%2Famerican-political-science-review Mendeley].
-Below you will find some examples for referencing common types of publication. Please refer to the [http://www.apsanet.org/Portals/54/APSA%20Files/publications/APSAStyleManual2006.pdf APSA Style Guide] for further information:
+Below you will find some examples for referencing common types of publication. Please refer to the [https://connect.apsanet.org/stylemanual/ APSA Style Guide] for further information:
 <ul>
 <li>'''Edited Volumes''': Castles, Francis G., Stephan Leibfried, Jane Lewis, Herbert Obinger, and Christopher Pierson, eds. 2010. ''The Oxford Handbook of the Welfare State''. Oxford: Oxford University Press.</li>