Here is the text we could read:
ORDER DENYING PETITION FOR EMERGENCY
RELIEF IN CONNECTION WITH CLAIMS OF
SEXUAL VIOLENCE OR INTIMIDATION
ÒDONANS POU REFIZE PETISYON POU
PWOTEKSYON IJAN KI ASOSYE AK VYÒL AK
ENTIMIDASYON
_________________________
_________________________
vs.
Docket No / No. Dosye:
Case Filed / Dat Depoze:
COMMONWEALTH OF PENNSYLVANIA
COUNTY OF ____________
Mag. Dist. No:
No Dist. Maj
DJ Name:
Non Jij la
ddress:
Adrès
elephone:
Telefòn
N
DENYING PETITION FOR EMERGENCY RELIEF IN
CONNECTION WITH CLAIMS OF SEXUAL VIOLENCE OR
INTIMIDATION
ORDER
ÒDONANS
REFIZE PETISYON POU PWOTEKSYON IJAN KI ASOSYE AK
VYÒL AK ENTIMIDASYON
t 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.
an yon odyans ki te fèt ________________ san defandè a,
mwen jije li pa nesesè pou bay yon òdonans konsèvatwa epi
mwen rejte petisyon pou pwoteksyon ijan an.
_________________________ __________________________________________
Date / Dat
Magisterial District Judge / Jij Distri Majisteral
M
A
T
A
1
Date Created: December 26, 2016
DJS 306E-BL (Haitian Creole)
M
Haitian Creole Order Denying Petition for Emergency Relief in Connection with Claims of SV-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 8
- 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_dat
was Date Dat (0.33 conf)vs
was vs (0.33 conf)undefined
was undefined (0.38 conf)li_pa_pou_bay_yon_epi
was mwen jije li pa nesesè pou bay yon òdonans konsèvatwa epi (0.41 conf)magisterial_district_judge_jij_distri_majisteral
was Magisterial District Judge Jij Distri Majisteral (0.42 conf)
We've done our best to group similar variables togther to avoid overwhelming the user.
Suggested Screen 0:
Suggested Screen 1:
count
found_necessary_issue
date_dat
undefined
li_pa_pou_bay_yon_epi
magisterial_district_judge_jij_distri_majisteral
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