commit 9411ad817dcde1d50f9ba027ec6f3dd06f51bb71 Author: 张献维 Date: Sat Dec 28 10:20:33 2024 +0800 初步校核文档记录 diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..85e7c1d --- /dev/null +++ b/.gitignore @@ -0,0 +1 @@ +/.idea/ diff --git a/Writerside/c.list b/Writerside/c.list new file mode 100644 index 0000000..c4c77a2 --- /dev/null +++ b/Writerside/c.list @@ -0,0 +1,6 @@ + + + + + \ No newline at end of file diff --git a/Writerside/cfg/buildprofiles.xml b/Writerside/cfg/buildprofiles.xml new file mode 100644 index 0000000..332e47b --- /dev/null +++ b/Writerside/cfg/buildprofiles.xml @@ -0,0 +1,13 @@ + + + + + + + + true + + + + diff --git a/Writerside/cfg/glossary.xml b/Writerside/cfg/glossary.xml new file mode 100644 index 0000000..22bec6b --- /dev/null +++ b/Writerside/cfg/glossary.xml @@ -0,0 +1,7 @@ + + + + + Description of what "foo" is. + + \ No newline at end of file diff --git a/Writerside/images/00000.png b/Writerside/images/00000.png new file mode 100644 index 0000000..1c5cc65 Binary files /dev/null and b/Writerside/images/00000.png differ diff --git a/Writerside/images/00001.png b/Writerside/images/00001.png new file mode 100644 index 0000000..4356a72 Binary files /dev/null and b/Writerside/images/00001.png differ diff --git a/Writerside/images/00002.png b/Writerside/images/00002.png new file mode 100644 index 0000000..3906b38 Binary files /dev/null and b/Writerside/images/00002.png differ diff --git a/Writerside/images/00003.png b/Writerside/images/00003.png new file mode 100644 index 0000000..22b450b Binary files /dev/null and b/Writerside/images/00003.png differ diff --git a/Writerside/images/00004.png b/Writerside/images/00004.png new file mode 100644 index 0000000..1bd6b9f Binary files /dev/null and b/Writerside/images/00004.png differ diff --git a/Writerside/images/00005.png b/Writerside/images/00005.png new file mode 100644 index 0000000..bdd4418 Binary files /dev/null and b/Writerside/images/00005.png differ diff --git a/Writerside/images/00006.png b/Writerside/images/00006.png new file mode 100644 index 0000000..6dcba19 Binary files /dev/null and b/Writerside/images/00006.png differ diff --git a/Writerside/images/00007.png b/Writerside/images/00007.png new file mode 100644 index 0000000..f409ba6 Binary files /dev/null and b/Writerside/images/00007.png differ diff --git a/Writerside/images/00008.png b/Writerside/images/00008.png new file mode 100644 index 0000000..837c7db Binary files /dev/null and b/Writerside/images/00008.png differ diff --git a/Writerside/in.tree b/Writerside/in.tree new file mode 100644 index 0000000..076894b --- /dev/null +++ b/Writerside/in.tree @@ -0,0 +1,14 @@ + + + + + + + + + + + \ No newline at end of file diff --git a/Writerside/topics/备份.md b/Writerside/topics/备份.md new file mode 100644 index 0000000..b24eda4 --- /dev/null +++ b/Writerside/topics/备份.md @@ -0,0 +1,79 @@ +# Starter + + + +## Add new topics +You can create empty topics, or choose a template for different types of content that contains some boilerplate structure to help you get started: + +![Create new topic options](new_topic_options.png){ width=290 }{border-effect=line} + +## Write content +%product% supports two types of markup: Markdown and XML. +When you create a new help article, you can choose between two topic types, but this doesn't mean you have to stick to a single format. +You can author content in Markdown and extend it with semantic attributes or inject entire XML elements. + +## Inject XML +For example, this is how you inject a procedure: + + + +

Start typing and select a procedure type from the completion suggestions:

+ completion suggestions for procedure +
+ +

Press Tab or Enter to insert the markup.

+
+
+ +## Add interactive elements + +### Tabs +To add switchable content, you can make use of tabs (inject them by starting to type `tab` on a new line): + + + + ![Alt Text](new_topic_options.png){ width=450 } + + + + ]]> + + + +### Collapsible blocks +Apart from injecting entire XML elements, you can use attributes to configure the behavior of certain elements. +For example, you can collapse a chapter that contains non-essential information: + +#### Supplementary info {collapsible="true"} +Content under a collapsible header will be collapsed by default, +but you can modify the behavior by adding the following attribute: +`default-state="expanded"` + +### Convert selection to XML +If you need to extend an element with more functions, you can convert selected content from Markdown to semantic markup. +For example, if you want to merge cells in a table, it's much easier to convert it to XML than do this in Markdown. +Position the caret anywhere in the table and press Alt+Enter: + +Convert table to XML + +## Feedback and support +Please report any issues, usability improvements, or feature requests to our +YouTrack project +(you will need to register). + +You are welcome to join our +public Slack workspace. +Before you do, please read our [Code of conduct](https://www.jetbrains.com/help/writerside/writerside-code-of-conduct.html). +We assume that you’ve read and acknowledged it before joining. + +You can also always email us at [writerside@jetbrains.com](mailto:writerside@jetbrains.com). + + + + Markup reference + Reorder topics in the TOC + Build and publish + Configure Search + + \ No newline at end of file diff --git a/Writerside/topics/开始.md b/Writerside/topics/开始.md new file mode 100644 index 0000000..4d1f5cd --- /dev/null +++ b/Writerside/topics/开始.md @@ -0,0 +1,38 @@ +# 《%mainJob%》开始 + +## 功能位置 + + + +

开始操作 系统登录 :

+ completion suggestions for procedure +
+ +

点击 机构信息管理人员信息管理 进入。

+ completion suggestions for procedure +
+ +

校核功能包含 机构%mainJob%人员%mainJob%整库%mainJob%校核规则管理 等功能。

+ completion suggestions for procedure + completion suggestions for procedure + completion suggestions for procedure + completion suggestions for procedure +
+ +

数据维护包含 机构信息维护人员信息维护排序信息维护 等功能。

+ completion suggestions for procedure + completion suggestions for procedure + completion suggestions for procedure +
+
+ +## 功能说明 +%projectName%的%mainJob%,更多可以理解为数据查询,但是校核不仅仅只有查询,也包含 **校核规则定义** 和 **校核结果维护** 等。 + +## 校核的区别 {collapsible="true"} + +其实校核中的`机构%mainJob%`、`人员%mainJob%`,其实都是`整库%mainJob%`的功能`界面`,针对不同的校核功能,进行校核`条件的过滤`。 + +就是人员校核,展示人员校核条件;机构校核,只展示机构校核条件。 + +> 主要校核区别,就是定义校核规则的主校验表是否为 `B01` 表。 \ No newline at end of file diff --git a/Writerside/topics/规则分类.md b/Writerside/topics/规则分类.md new file mode 100644 index 0000000..9d44718 --- /dev/null +++ b/Writerside/topics/规则分类.md @@ -0,0 +1,63 @@ +# 《%mainJob%》分类 + +> 校核规则主要分为无前提条件校核和有前提条件校核两个部分。 + + +## 无前提条件校核 + +是指该部分校核,不存在前置条件,直接作为校核(查询)依据,该部分校核多为单条件, +或为某指标项为空(或未填写); +或为某指标项包含特殊字符串(多使用正则匹配); +或为某指标项不为6或8位数字(由于当前描述时间指标项均为字符串类型,可以填写到月,也可以精确的日,其实潜在描述不为 `时间字符串` ); +或为某指标项是否超出代码值范围等。 + + + + + a + + + a + + + a + + + a + + + + + +## 有前提条件校核 + +是指该部分校核,不存在前置条件,直接作为校核(查询)依据,该部分校核多为单条件, +或为某指标项为空(未填写); +或为某指标项(时间指标)不在某时间范围,或与校核截至时间比较; +或为某指标项是否超出代码值范围等。 + + +> 补充:其中也存在某些前提条件,主要看校核描述是否存在前提条件因子。 +> -- 机构信息集“机构类别”超出代码值范围或为根节点代码值 +> '' AND B0131 NOT IN(SELECT code_value FROM code_value WHERE code_type='ZB04' and CODE_STATUS='1' and CODE_LEAF='1')]]> +> +> 存在前提条件“属于法人单位的机构”才进行 +> (补充:WHERE 1=1 AND B01_temp.B0111 = :B0111 AND特定格式) + +## 每年变动规则 + +该部分校核规则多与指定时间有关,脚本中会写死具体条件。当汇数年度发生变化,该部分年份信息,也需要跟着修改。 + +## 总结 + +数据校核是一项解决数据质量重要手段,但是往往校核规则会被简化成俗语,有些精简的比较深的话,里面包含大量的前提条件;同时有些被简化的俗语,按照直观意思无法理解。 + +> `有些精简的比较深的话,里面包含大量的前提条件`:涉及存在前提条件,需要积累一些公务员人事的常识,或者咨询定制规则的用户。 + +> `被简化的俗语,按照直观意思无法理解`:需要咨询定制规则的用户,用户目的到底是什么。 + + +往往在完成校核条件定义的时候,开发人员常使用固定SQL语句进行实现,当然也可以通过校核方案进行配置,但是这些条件都仅仅是针对简单规则易用。 + + +### 最后结论: `咨询定制规则的用户` diff --git a/Writerside/topics/规则详解.md b/Writerside/topics/规则详解.md new file mode 100644 index 0000000..666fa0d --- /dev/null +++ b/Writerside/topics/规则详解.md @@ -0,0 +1,98 @@ +# 《%mainJob%》规则详解 + +## 每年变动规则 {collapsible="true"} + +## 无前提条件校核 {collapsible="true"} + +### 2017年1月以后的选调生,未填写考录信息 +### 2021年“考核结果”未填写 +### 填写了“学位名称”,但“学位代码”为空 +### “学位名称”、“学位代码”、“学历名称”、“学历代码”同时为空 +### 工作单位及职务中在任职务的“是否领导成员”为空 +### 家庭成员“工作单位及职务”为空或小于2个字 +### 人员排序号为空 +### 工作单位及职务中已免职务的“任职机构代码”为空 +### “职务层次(职级)”为空 +### 家庭成员出生日期为空,但未检测到“(已去世)” +### “现工作单位及职务全称”为空 +### 是“选调生”,但“进入选调生时间”为空 +### “最高学历”为空 +### “机构编码”为空 +### “出生年月”为空 +### “籍贯”为空 +### “出生地”为空 +### “职位类别”为空或职位类别超出代码值范围 +### “健康状况”为空 +### “参加工作时间”为空 +### “人员类别”为空 +### “人员管理状态”为空 +### “管理类别代码”为空 +### “任现领导职务时间(职务层次批准日期)”不为空,“现职务层次”为空 +### “身份证号”为空 +### “任现职级层次时间”(职级层次批准日期)为空 +### “现职务层次”和“现职级层次”不能同时为空 +### “是否具有两年以上基层工作经历”为空 +### 奖惩综述为空 +### “年度考核结果综述”为空 +### “政治面貌”为空 +### 人员的职务信息的排序号为空 +### “考核年度”为空 +### 家庭成员“工作单位及职务”为空 +### “性别”为空 +### 中专以上学历“学校及院系名称”未填写 +### “编制类型”为空 +### 选择了领导成员但“成员类别”为空 +### “现职级层次”不为空,但“任现职级层次时间”(职级层次批准日期)为空 +### 职务层次与职级信息集中“状态”为空 +### 机构排序号为空 +### 2023年“考核结果”未填写 +### 职务层次与职级信息集中“类别”为空 +### 是“考录”,但“录用审批(或备案 )时间”为空 +### 工作单位及职务中已免职务的“任职时间”为空 +### “现领导职务”(现职务层次)不为空,但“任现领导职务时间”(职务层次批准日期)为空 +### 工作单位及职务中已免职务的“免职时间”为空 +### “学校及院系名称”为空 +### 工作单位及职务中在任职务的“任职机构名称”为空 +### “民族”为空 +### “隶属关系”为空 +### 工作单位及职务中已免职务的“职务输出标识”为空 +### 工作单位及职务中的“是否破格提拔”为空 +### “机构类别”为空 +### 学历与学位同时为空 +### 工作单位及职务中在任职务的“职务名称”为空 +### “法人单位标识”为空 +### “是否考录”为空 +### 学历信息集“教育类别”为空 +### “考核结论”为空 +### 工作单位及职务中在任职务的“任职机构代码”为空 +### “是否选调生”为空 +### 家庭成员“姓名”为空 +### 工作单位及职务中已免职务的“任职机构名称”为空 +### 中专以上学历“学校及院系名称”和与所学专业都未填写 +### 2022年“考核结果”未填写 +### “现职级层次”不为空,但“职级起算时间”为空 +### “现领导职务”为厅局级正职时,现职级应当为空 +### 工作单位及职务中已免职务的“是否领导成员”为空 +### 14岁以上家庭成员的政治面貌为空 +### 工作单位及职务中已免职务的“主职务”为空 +### 填写了“学历名称”,但“学历代码”为空 +### 填写了“学历代码”,但“学历名称”为空 +### 工作单位及职务中的“任职状态”为空 +### 工作单位及职务中在任职务的“职务输出标识”为空 +### “称谓”为空 +### 填写了“学位代码”,但“学位名称”为空 +### 工作单位及职务中在任职务的“任职时间”为空 +### “机构级别”为空 +### 学历信息集“输出标识”为空 +### 工作单位及职务中在任职务的“主职务”为空 +### “所在政区”为空 +### “姓名”为空 +### 工作单位及职务中已免职务的“职务名称”为空 +### “现工作单位及职务简称”为空 +### 大专以上“所学专业名称”未填写 +### 专业技术信息集的“专业技术资格”名称为空 +### 奖惩信息集中“奖惩名称”为空 + + + +## 有前提条件校核 {collapsible="true"} \ No newline at end of file diff --git a/Writerside/v.list b/Writerside/v.list new file mode 100644 index 0000000..30c1ac9 --- /dev/null +++ b/Writerside/v.list @@ -0,0 +1,6 @@ + + + + + + diff --git a/Writerside/writerside.cfg b/Writerside/writerside.cfg new file mode 100644 index 0000000..98e1435 --- /dev/null +++ b/Writerside/writerside.cfg @@ -0,0 +1,11 @@ + + + + + + + + + + \ No newline at end of file