Here is the text we could read:
ORDER DENYING EMERGENCY
RELIEF FROM ABUSE
ORDONNANCE REFUSANT UN
REDRESSEMENT EN URGENCE
POUR UN ACTE CONSTITUANT
UNE MALTRAITANCE
_______________________
vs.
_________________________
Docket No / Dossier n° :
Case Filed / Plainte déposée le :
COMMONWEALTH OF PENNSYLVANIA
COUNTY OF ____________
DJ Name:
Nom du juge du dist. jud
Mag. Dist. No:
N° de dist. jud
ddress:
Adresse
elephone:
Téléphone
M
A
T
ORDONNANCE
REFUSANT UN REDRESSEMENT EN URGENCE
CONTRE UN ACTE CONSTITUANT UNE MALTRAITANCE
le
Lors d'une audience unilatérale qui s'est
____________________,
j'ai conclu qu'il n'était pas
nécessaire de rendre une ordonnance de protection. La
requête pour un
redressement en urgence est par
conséquent refusée.
tenue
ORDER
DENYING EMERGENCY PROTECTION FROM ABUSE
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.
_____________________________________ ___________________________________________
Date / Date
Magisterial District Judge / Juge du district judiciaire
_
1
Date Created: December 26, 2016
DJS 307E-BL (French)
M
French Order Denying Emergency Relief From Abuse-307E
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 9
- 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)vs
was vs (0.33 conf)undefined
was undefined (0.38 conf)found_necessary_order
was have found that it is not necessary to issue a protective order (0.37 conf)de_rendre_une_la
was nécessaire de rendre une ordonnance de protection La (0.48 conf)date
was Date Date (0.42 conf)magisterial_district_judge_juge_du_judiciaire
was Magisterial District Judge Juge du district judiciaire (0.49 conf)
We've done our best to group similar variables togther to avoid overwhelming the user.
Suggested Screen 0:
count
vs
undefined
found_necessary_order
date
Suggested Screen 1:
de_rendre_une_la
magisterial_district_judge_juge_du_judiciaire
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