Here is the text we could read:
COMMONWEALTH OF PENNSYLVANIA
COUNTY OF ____________
ORDER DENYING EMERGENCY
RELIEF FROM ABUSE
ПРИКАЗ ОБ ОТКАЗЕ В ПРЕДОСТАВЛЕНИИ
СРОЧНОЙ СУДЕБНОЙ ЗАЩИТЫ ОТ ЖЕСТОКОГО
ОБРАЩЕНИЯ
Mag. Dist. No:
Суд. округ №
MDJ Name:
Ф. И. О. окр. судьи
Address:
Адрес
Telephone:
Телефон
_______________________
vs.
_________________________
Docket No / Дело №:
Case Filed / Дата открытия дела:
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 / Дата
Magisterial District Judge / Окружной судья
MDJS 307E-BL (Russian)
1
Date Created: December 26, 2016
Russian 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): 8
- Average fields per page: 8
- 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)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)fill__1
was fill_5 (0.36 conf)fill__2
was fill_9 (0.36 conf)fill__3
was fill_6 (0.36 conf)fill__4
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_order
fill__1
fill__2
fill__3
fill__4
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