Here is the text we could read:
COMMONWEALTH OF PENNSYLVANIA
COUNTY OF ____________
ORDER DENYING PETITION FOR EMERGENCY
RELIEF IN CONNECTION WITH CLAIMS OF
SEXUAL VIOLENCE OR INTIMIDATION
ÁN LỆNH BÁC BỎ ĐƠN XIN BIỆN PHÁP CÔNG LÝ
KHẨN CẤP LIÊN QUAN ĐẾN KHIẾU NẠI VỀ BẠO
HÀNH TÌNH DỤC HOẶC HĂM DỌA
Mag. Dist. No:
Số Địa hạt Pháp lý
MDJ Name:
Tên MDJ
Address:
Địa chỉ
Telephone:
Điện thoại
_________________________
vs.
_________________________
Docket No / Số Ghi án:
Case Filed / Hồ sơ Đã nộp:
ORDER
ÁN LỆNH
DENYING PETITION FOR EMERGENCY RELIEF IN
CONNECTION WITH CLAIMS OF SEXUAL VIOLENCE OR
INTIMIDATION
BÁC BỎ ĐƠN XIN BIỆN PHÁP CÔNG LÝ KHẨN CẤP LIÊN
QUAN ĐẾN KHIẾU NẠI VỀ BẠO HÀNH TÌNH DỤC HOẶC HĂM
DỌA
At an ex parte hearing held on _______________________,
I have found that it is not necessary to issue a protective
order and the petition for emergency relief is denied.
Tại phiên điều trần một phía diễn ra vào _______________,
tôi nhận thấy rằng không cần thiết phải ban hành một lệnh
bảo vệ và đơn xin biện pháp công lý khẩn cấp bị bác bỏ.
_________________________ _____________________________________________
Date / Ngày
Magisterial District Judge / Thẩm phán Quan tòa Quận
MDJS 306E-BL (Vietnamese)
1
Date Created: December 26, 2016
Vietnamese Order Denying Petition for Emergency Relief in Connection with Claims of Sexual Violence or Intimidation 306E
This info page is part of the LIT Lab's Form Explorer project. It is not associated with the Pennsylvania state courts.
To learn more about the project, check out our about page.
Downloads: You can download both the original form (last checked 2023-03)
and the machine-processed form with normalized data fields.
About This Form:
- Sourced from www.pacourts.us (2023-03)
- Page(s): 1
- Fields(s): 7
- Average fields per page: 7
- Reading Level: Grade 5
- LIST Grouping(s):
GO-00-00-00-00.
Use our Rate My PDF tool to learn more.
Go beyond the above insights and learn more about this or any pdf form at
RateMyPDF.com, includes: counts of difficult words used,
passive voice decetion, and suggestions for how to make the form more usable.
Identified Data Fields:
We have done our best to automaticly identify and name form fields according to our naming conventions.
When possible, we've used names tied to our question library. See e.g., user1_name.
If we think we've found a match to a question in our library, it is highlighted in green. Novel names are auto generated. So, you will probably need to edit some of them if you're trying to stick to the convention.
Here are the fields we could identify.
count
was COUNTY OF (0.54 conf)found_necessary_issue
was I have found that it is not necessary to issue a protective (0.34 conf)date_ng
was Date Ngày (0.42 conf)vs
was vs (0.33 conf)undefined
was undefined (0.38 conf)fill__1
was fill_4 (0.36 conf)fill__2
was fill_7 (0.36 conf)
We've done our best to group similar variables togther to avoid overwhelming the user.
Suggested Screen 0:
Suggested Screen 1:
Suggested Screen 2:
count
found_necessary_issue
date_ng
fill__1
fill__2
Create an Interactive Version of this Form:
The Weaver creates a draft guided interview from a template form, like the one provided here. You can use the link below to open this form in the Weaver.
To learn more, read "Weaving" your form into a draft interview.
Launch Form in Weaver