| Literature DB >> 36124249 |
Hongjing Cui1, Huican Zhang2, Deng Pan3, Bing Zhao4,5.
Abstract
This study aims to make public sports health emergency corpus as a way to deal with public health emergency such as COVID-19, reducing the losses affected by an illness or health condition that has occurred frequently in recent years. On this basis, this paper analyzes the research status of emergency language services at home and abroad, discusses the significance and principles of Multimodal Aligned Corpus Public Health Emergency (shorted for MACPHE) construction, and develops technical processing paths and building procedures for MACPHE. Finally, it was emphasized that the construction of MACPHE and emergency language resources are important parts of the national language service capacity. Furthermore, on the basis of big data, a modal architecture of MACPHE was given and analyzed in the field of public health service.Entities:
Mesh:
Year: 2022 PMID: 36124249 PMCID: PMC9482519 DOI: 10.1155/2022/8717072
Source DB: PubMed Journal: J Environ Public Health ISSN: 1687-9805
Figure 1Architecture and classification of emergency corpus for public health emergency.
Major channels to obtain public health emergencies from media.
| Public health emergency | TikTok | News site | Newspapers and magazines | TV broadcast | |||
|---|---|---|---|---|---|---|---|
| SARS | 0% | 0% | 14.3% | 0% | 9.63% | 14.75% | 61.32% |
| H1N1 | 0.63% | 1.48% | 23.65 | 0% | 11.58% | 52.14% | 0% |
| COVID-19 | 43.67 | 23.16% | 4.15% | 35.68% | 2.37% | 1.03% | 4.69% |
Figure 2Flowchart of multimodal corpus construction.
Figure 3Classification of multimodal corpus.
Figure 4Official download website of ELAN.
Definition and raw data processing of XML schema.
| Code NO. | Description of the date processing |
|---|---|
| 001 | <?xml version=“1.0” encoding=“UTF-8”?> |
| 002 | <xs:schemaxmlns:xs=“http:// |
| 003 | targetNamespace = “ |
| 004 | xmlns=“ |
| 005 | <xs:element name=“articleInfo” |
| 006 | <xs:complexType> |
| 007 | <xs:sequence> |
| 008 | <xs:element name=“title” type=“xs:string”/> |
| 009 | <xs:element name=“time” type=“xs:string”/> |
| 010 | <xs:element name=“source” type=“xs:string”/> |
| 011 | <xs:element name=“author” type=“xs:string”/> |
| 012 | <xs:element name=“classify” type=“xs:string”/> |
| 013 | <xs:element name=“theme” type=“xs:string”/> |
| 014 | </xs:sequence> |
| 015 | </xs:complexType> |
| 016 | </xs:element> |
| 017 | <xs:element name=“text”> |
| 018 | <xs:complexType> |
| 019 | <xs:sequence> |
| 020 | <xs:element name=“sectID” type=“xs:string”/> |
| 021 | <xs:element name=“sentenceID” type=“xs:string”/> |
| 022 | <xs:element name=“sentence” type=“xs:string”/> |
| 023 | <xs:element name=“sentenceCut” type=“xs:string”/> |
| 024 | <xs:element name=“sentenceDependency” type=“xs:string”/> |
| 025 | <xs:element name=“sentenceSemantic” type=“xs:string”/> |
| 026 | </xs:sequence> |
| 027 | </xs:complexType> |
| 028 | </xs:element> |
| 029 | </xs:schema> |