text:
LEVOCHKINA v. RUSSIA About Project
CASE OF LEVOCHKINA v. RUSSIA
(Application no. 944/02)
This judgment will become final in the circumstances set out in Article 44 § 2 of the Convention. It may be subject to editorial revision.
In the case of Levochkina v. Russia,
The European Court of Human Rights (First Section), sitting as a Chamber composed of:
Mr C.L. Rozakis, President,
Mr L. Loucaides,
Mrs N. Vajić,
Mr A. Kovler,
Mr K. Hajiyev,
Mr D. Spielmann,
Mr S.E. Jebens, judges,
and Mr S. Nielsen, Section Registrar,
Having deliberated in private on 14 June 2007,
Delivers the following judgment, which was adopted on that date:
1. The case originated in an application (no. 944/02) against the Russian Federation lodged with the Court under Article 34 of the Convention for the Protection of Human Rights and Fundamental Freedoms ("the Convention") by a Russian national, Mrs Nadezhda Petrovna Levochkina ("the applicant"), on 4 July 2001.
2. The Russian Government ("the Government") were represented by Mr P. Laptev, Representative of the Russian Federation at the European Court of Human Rights.
3. The applicant alleged, in particular, that the domestic judicial authorities had reconsidered a judgment given in her favour having improperly used the procedure for reconsidering judgments on the basis of newly discovered circumstances.
4. By a decision of 17 November 2005 the Court declared the application partly admissible.
5. The Government, but not the applicant, filed further written observations (Rule 59 § 1). The Chamber having decided, after consulting the parties, that no hearing on the merits was required (Rule 59 § 3 in fine), the applicant replied in writing to the Government's observations.
I. THE CIRCUMSTANCES OF THE CASE
6. The applicant was born in 1941 and lives in Novosibirsk.
7. The applicant receives an old-age pension. The Law of 21 July 1997 on the Calculation and Upgrading of State Pensions ("the Pensions Act") introduced, from 1 February 1998 onwards, a new method for calculating pensions. The idea behind this method, based on what is known as an "individual pensioner coefficient", was to link the pension to the pensioner's previous earnings.
8. The authority in charge of the applicant's pension, the Pension Fund Agency of the Kirovskiy District of Novosibirsk ("the Agency"), fixed the applicant's coefficient at 0.525. The applicant challenged the Agency's decision in the Kirovskiy District Court of Novosibirsk. She argued that her coefficient should be 0.7.
9. On 31 August 1999 the District Court found for the applicant, considering that the Agency had misinterpreted the Pensions Act. In particular, it held as follows:
"... Article 4 [of the 1997 Pensions Act] fixes an individual pensioner coefficient at the maximum rate of 0.7. This rate is subject to changes hereafter by a federal law at the adoption of a federal law on the budget of the RF PF [Pension Fund] for a next financial year."
The District Court decided that the Agency was to recalculate the applicant's pension using a coefficient of 0.7 from 1 February 1998 "until a change in the legislation".
10. The Agency appealed against the judgment. On 7 October 1999 the Novosibirsk Regional Court upheld the judgment, which became enforceable on the same day. The judgment was never executed.
11. On 29 December 1999 the Ministry of Labour and Social Development ("the Ministry") issued an Instruction on the "Application of Limitations" established by the Pensions Act ("the Instruction"). The Instruction clarified how to apply the Pensions Act.
12. On 23 August 2000 the Agency lodged an application with the District Court for the reconsideration of the applicant's case owing to newly discovered circumstances. They asked the court to take account of the Instruction, which supported their arguments that had been rejected by the court during the initial examination of the case.
13. Some time thereafter a group of individuals challenged the Instruction before the Supreme Court of the Russian Federation. On 24 April 2000 the Supreme Court dismissed the complaint. It found that, contrary to what the complainants had suggested, the Ministry of Labour had not acted ultra vires in issuing the Instruction, and that the Ministry's interpretation of the Pensions Act had been correct. On 25 May 2000 the Cassation Division of the Supreme Court upheld this judgment on appeal.
14. On 16 January 2001 the District Court examined the Agency's request. The District Court noted that by virtue of Article 333 of the Code of Civil Procedure enforceable judgments may be reconsidered owing to newly discovered circumstances which could not have been known at the time when the judgment had been delivered. The court further noted that the Instruction had been upheld by the Supreme Court which, therefore, had found it lawful to interpret article 4 of the Pensions Act so that the rate of 0.7 should not apply to an "individual pensioner coefficient".
15. In a decision of 16 January 2001 the District Court granted the Agency's application, under Article 337 of the Code of Civil Procedure, quashed the judgment of 31 August 1999, as upheld on 7 October 1999, and ordered a fresh examination of the case. It stated that its decision was not subject to appeal.
16. As a result of the fresh examination of the case the District Court delivered a judgment of 31 January 2001 in which it rejected the applicant's claims in full. The applicant appealed. On 13 March 2001 the Novosibirsk Regional Court dismissed the applicant's appeal and upheld the judgment of 31 January 2001.
17. From 1 May 2001, following changes to the pension regulations, the applicant's pension was calculated based on a coefficient of 0.84.
II. RELEVANT DOMESTIC LAW AND PRACTICE
18. The Code of Civil Procedure of 1964 ("CCivP"), in force at the material time, provided as follows:
Article 333. Grounds for reconsideration
"[Judgments] which have come into force may be reconsidered on the basis of newly discovered circumstances. The grounds for reconsideration ... shall be as follows:
1. significant circumstances which were not and could not have been known to the party who applies for reconsideration; ...
4. cancellation of a court [judgment] or of another authority's decision which served as legal basis for the [judgment] in question."
Article 334. Lodging of application
"... [An application for reconsideration of a [judgment] owing to newly discovered circumstances] shall be lodged within three months after the discovery of the circumstances."
Article 337. Court decision on reconsideration of a case
"After examination of an application for reconsideration of a [judgment] owing to newly discovered circumstances, the court may either grant the application and quash the [judgment], or dismiss the application.
The court decision by which an application for reconsideration of a [judgment] owing to newly discovered circumstances is granted shall not be subject to appeal. ..."
19. On 2 February 1996 the Constitutional Court of the Russian Federation adopted a ruling concerning certain provisions of the Code of Criminal Procedure ("CCrP"). In that ruling the Constitutional Court decided that Article 384 of the CCrP ("Grounds for reconsideration of a [criminal] case on the basis of newly discovered circumstances", which was in many respects similar to Article 333 of the CCivP) was unconstitutional in that it limited the grounds for the reopening of a criminal case to situations of "newly discovered circumstances". In that ruling the Constitutional Court suggested that this provision of the CCrP prevented rectification of judicial errors and miscarriages of justice. In its ruling of 3 February 1998 the Constitutional Court came to the conclusion that Article 192 § 2 of the Code of Commercial Procedure was unconstitutional in so far as it had served as a basis for the dismissal of applications for reconsideration of judgments of the Presidium of the Supreme Commercial Court, where the judgment had been delivered as a result of a judicial error which had not been and could not have been established earlier.
20. The Instruction of the Ministry of Labour and Social Development of 29 December 1999 on the "Application of Limitations" established by the Pensions Act was registered by the Ministry of Justice on 31 December 1999 and became binding in February 2000, ten days after its official publication.
I. ALLEGED VIOLATION OF ARTICLE 6 § 1 AND ARTICLE 1 OF PROTOCOL No. 1
21. The applicant complained that the State had reconsidered a final judgment in her favour. The Court will examine this complaint under Article 6 § 1 of the Convention and Article 1 of Protocol No. 1.
Article 6 § 1 of the Convention, as far as relevant, reads as follows:
"In the determination of his civil rights and obligations ..., everyone is entitled to a fair ... hearing ... by [a] ... tribunal..."
Article 1 of Protocol No. 1 reads as follows:
"Every natural or legal person is entitled to the peaceful enjoyment of his possessions. No one shall be deprived of his possessions except in the public interest and subject to the conditions provided for by law and by the general principles of international law.
The preceding provisions shall not, however, in any way impair the right of a State to enforce such laws as it deems necessary to control the use of property in accordance with the general interest or to secure the payment of taxes or other contributions or penalties."
A. The parties' submissions
1. The Government
22. The Government submitted that the complaint was incompatible with the Convention ratione materiae, as it did not concern "civil rights and obligations" or "property" or, alternatively, that there had been no breach of Article 6 § 1 or Article 1 of Protocol No. 1 on account of the reconsideration of the case concerning the applicant's pension.
(a) Applicability of Article 6 § 1
23. The Government stressed that the judgment of 31 August 1999 had not determined any definite amount due to the applicant, but had rather established how the pension should be calculated. In their words, "the subject-matter of the dispute was not the applicant's claim to award her monetary sums, but the matter of lawfulness ... of application of the Instruction". According to the Government, the dispute at issue was not a civil one because "the determination of the order of calculation of pensions belongs to the realm of public law". They referred to Schouten and Meldrum v. the Netherlands (judgment of 9 December 1994, Series A no. 304, § 50), Pančenko v. Latvia, ((dec.), no. 40772/98, 28 October 1999), and Kiryanov v. Russia ((dec.), no. 42212/02, 9 December 2004).
(b) Applicability of Article 1 of Protocol No. 1
24. The Government contested that the pension awarded to the applicant by virtue of the judgment of 31 August 1999 constituted her "possession". They noted that in the case of Pravednaya v. Russia (no. 69529/01, 18 November 2004) the Court had regarded a judicial award of that type as the applicant's "possession". In that case the Court had ordered the restoration of the initial judgment in the applicant's favour and the payment of the pension in the amount established by that judgment. However, in the Government's view, such an approach created confusion. If the sum awarded by a court was a pensioner's "possession", it should not be affected by any subsequent increase in pension rates. Therefore, in Pravednaya the applicant would have had to return the money "excessively" paid to her by virtue of the later changes in the legislation on State pensions. They concluded that in order to avoid such situations the Court should not regard the pension amounts awarded by the domestic courts as the claimants' "possessions" within the meaning of Article 1 of Protocol No. 1.
(c) Merits of the complaint
25. The Government submitted that it was the Supreme Court's decision upholding the Instruction which had constituted a newly discovered circumstance and warranted the reopening of the case within the meaning of Article 333 of the CCivP. This was a major difference with the Pravednaya case (cited above). The Government explained that to consider the Supreme Court's decision as a newly discovered circumstance was in line with the position of the Constitutional Court set out in its decisions of 2 February 1996 and 3 February 1998. In another decision of 14 January 1999 the Constitutional Court had held that court judgments might be reconsidered if relevant provisions of law had been found unconstitutional.
26. The Government further submitted that the Instruction had been issued after the initial judgment had become final, so the Agency could not have relied on it in the appeal proceedings. This was another difference with the Pravednaya case, where the Instruction had been adopted while the proceedings were still pending. Therefore, the Agency's request to reopen the case had not been an "appeal in disguise" but a conscientious effort to make good a miscarriage of justice.
27. The Government observed that the reopening of the case had been lawful and complied with the procedure prescribed by law, the request having been lodged within the statutory three-month time-limit.
28. The Government concluded that the reopening of the case had not infringed the principle of legal certainty as guaranteed by Article 6 § 1 nor had it interfered with the applicant's property rights as guaranteed by Article 1 of Protocol No. 1.
2. The applicant
29. The applicant disagreed with the Government's arguments. She pointed out that there had been no lawful grounds for the quashing of the judgment of 31 August 1999, upheld on 7 October 1999. The Pensions Act underlying the judgment had not changed and the Ministry of Labour and the Supreme Court could not have substituted the law by their decisions. Furthermore, the Agency had missed the time-limit for reopening a case: it had applied to the court more than eleven months after the Instruction had been issued, instead of three months as required by the civil procedure.
B. The Court's assessment
1. Applicability of Article 6 § 1 of the Convention and Article 1 of Protocol No. 1
30. The Court notes that the dispute as to the increase of the applicant's old-age pension entitlement was one of a pecuniary nature and undeniably concerned a civil right within the meaning of Article 6 § 1 of the Convention (see Schuler-Zgraggen v. Switzerland, judgment of 24 June 1993, Series A no. 263, p. 17, § 46; Massa v. Italy, judgment of 24 August 1993, Series A no. 265-B, p. 20, § 26; Süßmann v. Germany, judgment of 16 September 1996, Reports of Judgments and Decisions 1996-IV, p. 1170, § 42; and, as a recent authority, Tričković v. Slovenia, no. 39914/98, § 40, 12 June 2001).
31. It reiterates that Article 1 of Protocol No. 1 does not guarantee, as such, the right to an old-age pension or to any social benefit in a particular amount (see, for example, Aunola v. Finland (dec.), no. 30517/96, 15 March 2001). However a "claim" – even concerning a pension – can constitute a "possession" within the meaning of Article 1 of Protocol No. 1 if it is sufficiently established to be enforceable (see Stran Greek Refineries v. Greece, judgment of 9 December 1994, Series A no. 301, § 59). T judgment of the Kirovskiy District Court of 31 August 1999, which became final after it had been upheld on appeal by the Novosibirsk Regional Court on 7 October 1999, provided the applicant with an enforceable claim to receive an increased pension based on a coefficient of 0.7.
32. The Court notes that the objections and arguments put forward by the Government were rejected in the earlier similar case of Bulgakova v. Russia (no. 69524/01, §§ 27-32, 18 January 2007) and sees no reason to reach a different conclusion in the present case.
33. Accordingly, the Court considers that in the present case the applicant's dispute concerned a civil right within the meaning of Article 6, and that the applicant had a "possession" within the meaning of Article 1 of Protocol No. 1.
2. Alleged violation of Article 6 § 1
34. The Court reiterates that the right to a fair hearing before a tribunal as guaranteed by Article 6 § 1 of the Convention must be interpreted in the light of the Preamble to the Convention, which, in its relevant part, declares the rule of law to be part of the common heritage of the Contracting States. One of the fundamental aspects of the rule of law is the principle of legal certainty, which requires, among other things, that where the courts have finally determined an issue, their ruling should not be called into question (see Brumărescu v. Romania, judgment of 28 October 1999, Reports 1999-VII, § 61). This principle underlines that no party is entitled to seek a review of a final and binding judgment merely for the purpose of obtaining a rehearing and a fresh determination of the case. Review by higher courts should not be treated as an appeal in disguise, and the mere possibility of there being two views on the subject is not a ground for re-examination. A departure from that principle is justified only when made necessary by circumstances of a substantial and compelling character (see Ryabykh v. Russia, no. 52854/99, § 52, ECHR 2003-IX).
35. The Court examined the quashing of a final judgment on the ground of newly discovered circumstances in Pravednaya (cited above), a case with a similar set of facts, where it held:
"27. The procedure for quashing of a final judgment presupposes that there is evidence not previously available through the exercise of due diligence that would lead to a different outcome of the proceedings. The person applying for rescission should show that there was no opportunity to present the item of evidence at the final hearing and that the evidence is decisive. Such a procedure is defined in Article 333 of the CCivP and is common to the legal systems of many member States.
28. This procedure does not by itself contradict the principle of legal certainty in so far as it is used to correct miscarriages of justice. ..."
36. In the case of Pravednaya the Instruction of the Ministry of Labour had been issued between the first-instance and appeal judgments. The relevant pension agency had not relied on the Instruction in the appeal proceedings but had only done so later, in their request for the judgment, then final, to be set aside owing to "newly discovered circumstances". The Court considered that the agency's request had been an "appeal in disguise" and found that by granting it the court had infringed the principle of legal certainty and the applicant's "right to a court" under Article 6 § 1 of the Convention (see Pravednaya, cited above, §§ 29-34).
37. The present case differs from Pravednaya in that the Instruction of the Ministry of Labour was issued after the first-instance judgment had been upheld on appeal. The Court's task is to determine whether, on the facts of the present case, the quashing of the judgment was exercised in a manner compatible with Article 6. To do so it will examine the reasons adduced by the Kirovskiy District Court for the quashing of the judgment (see paragraph 14 above).
38. The Kirovskiy District Court held that the interpretation of the Pensions Act by the Ministry of Labour, which had been upheld by the Supreme Court, was a "newly discovered circumstance". Therefore, the District Court decided that the Agency's request should be granted and the judgment be quashed.
39. The Court first notes that the Instruction and the Supreme Court's decision upholding it did not exist during the examination of the applicant's case. They were adopted after the judgment had been upheld on appeal. In the Court's view, the above-mentioned Instruction and decision were new legal acts and did not constitute newly discovered circumstances as considered by the District Court (see Article 333 of CCivP, paragraph 18 above).
40. Further, the judgment of 31 August 1999 was a result of the District Court's interpretation and application of the Pensions Act to the applicant's case. As it transpires from the decision of 7 February 2001, the fact that the Ministry's interpretation of that Act in an Instruction, a subordinate legal instrument, differed from the court's findings, with the effect that it would have led to a different outcome of the proceedings, was considered by the District Court a sufficient reason to quash the judgment and reconsider the case. The Court finds that this reason as such could not justify the reopening of the case after a final and binding judgment.
41. The Court notes the Government's argument that the reopening was necessary to make good a miscarriage of justice. However, other than referring to the Ministry's interpretation of the law, upheld by the Supreme Court, as a reason for the reopening, the District Court said nothing in its decision to explain why its original findings were to be considered a "miscarriage of justice" such as to justify the reopening.
42. The Court finds that by granting the Agency's request to reconsider the applicant's case and setting aside the final judgment of 31 August 1999, as upheld on 7 October 1999, the domestic authorities infringed the principle of legal certainty and the applicant's "right to a court" under Article 6 § 1 of the Convention.
43. There has accordingly been a violation of that Article.
3. Alleged violation of Article 1 of Protocol No. 1
44. The Court notes that the "possession" in this case was the applicant's claim to a pension based on a coefficient of 0.7 from 1 February 1998, in accordance with the judgment of the Kirovskiy District Court of 31 August 1999, upheld on 7 October 1999.
45. The District Court held that this method of calculation should have been maintained until a change in the legislation. Indeed, when delivering its judgment it applied the statutory pension regulations which were in force at the time. Those regulations, however, "are liable to change and a judicial decision cannot be relied on as a guarantee against such changes in the future" (see Sukhobokov v. Russia, no. 75470/01, § 26, 13 April 2006). Thus the Court observes that, as a result of such changes, the coefficient for the calculation of the applicant's pension changed to 0.84 from 1 May 2001.
46. The Court notes that the applicant's concern under Article 1 of Protocol No. 1 was the loss of her entitlement to a pension based on a coefficient of 0.7 for the period between 1 February 1998 and 1 May 2001, as opposed to the pension calculated and actually paid. However, the Court further notes that before that period ended on 1 May 2001, the Instruction had removed the ambiguity of the Pensions Act with the effect that the applicant's dispute over the coefficient had been resolved, at the level of the statutory regulations, in favour of the Agency. The Court considers that it was until the moment when the Instruction became binding in February 2000, and apparently changed the legislative framework relevant to the applicant's dispute, that the applicant's claim – and "possession" under Article 1 of Protocol No. 1 – had been secured by the judgment.
47. The effect produced by the decision of the Kirovskiy District Court of 16 January 2001, by which the application for reconsideration was granted, was that the applicant became deprived, retrospectively in respect of the above-mentioned period from February 1998 to February 2000, of the right to receive the pension in the amount initially determined by the court or, in other words, deprived of her possession within the meaning of the second sentence of the first paragraph of Article 1 of Protocol No. 1. The taking of property, in the light of this rule, can only be justified if it is shown, inter alia, to be "in the public interest" and "subject to the conditions provided for by law" (see Pravednaya, cited above, §§ 39-40).
48. While assuming that it was in the public interest to ensure a uniform application of the Pensions Act, the compliance of the reconsideration of the applicant's case with the "lawfulness" requirement is questionable (see paragraph 39 above). Even assuming that the court's interpretation of the domestic procedural law was not arbitrary (see the Government's argument concerning the Constitutional Court's decisions and the relevant domestic law in paragraphs 25 and 19 above), it still remains to be established whether the interference was proportionate to the legitimate aim pursued.
49. In this connection the Court reiterates its finding in Pravednaya that "the State's possible interest in ensuring a uniform application of the Pensions Law should not have brought about the retrospective recalculation of the judicial award already made" (Pravednaya, cited above, § 41). Having regard to the fact that the reconsideration of the case resulted in the full dismissal of the applicant's claim that had been granted in the initial judgment, the Court finds no reason to depart from that conclusion in the present case.
50. Based on the above considerations, the Court finds that by depriving the applicant of the right to benefit from the pension in the amount secured in a final judgment, the State upset the fair balance between the interests at stake.
51. There has, accordingly, been a violation of Article 1 of Protocol No. 1.
II. APPLICATION OF ARTICLE 41 OF THE CONVENTION
52. Article 41 of the Convention provides:
"If the Court finds that there has been a violation of the Convention or the Protocols thereto, and if the internal law of the High Contracting Party concerned allows only partial reparation to be made, the Court shall, if necessary, afford just satisfaction to the injured party."
A. Damage
53. In her letter of 11 January 2006, in reply to the Court's proposal to submit claims for just satisfaction, the applicant submitted that she wished "to reaffirm" her claims for just satisfaction according to Article 41 of the Convention since the violation of her rights in the court proceedings had adversely affected the state of her health and had caused her psychological suffering. In her application form the applicant claimed 21,000 roubles (RUR) in respect of pecuniary damage and RUR 30,000 in respect of non-pecuniary damage.
54. The Government asserted that it had followed from the applicant's letter of 11 January 2006 that she had failed to submit any claims in respect of pecuniary and non-pecuniary damage. The Government also submitted that no just satisfaction should be awarded to the applicant because there had been no violation of her rights under the Convention. Alternatively, the finding of a violation in itself would constitute sufficient just satisfaction.
55. The Court cannot agree with the Government that the applicant had failed to submit her claims for just satisfaction and, having regard to her submissions, will consider her claims as stated above.
1. Pecuniary damage
56. The applicant claimed RUR 21,000 in respect of pecuniary damage. This amount represented the underpayment of her pension between 1 February 1998 and 1 May 2001 and the relevant inflation-related losses. The difference in pension was based on an "individual pensioner coefficient" of 0.7 and a coefficient linked to the region of the applicant's residence.
57. The Court considers it appropriate to award the applicant, in respect of the violation of Article 1 of Protocol No. 1, the sum she would have received had the reduction of the pension as a result of the reconsideration of the case not been backdated (see, mutatis mutandis, Vasilyev v. Russia, no. 66543/01, § 47, 13 October 2005). The Court notes that the sum to be awarded by the Court should not take account of the coefficient linked to the region of the applicant's residence, as that claim was not secured by the judgment of 31 August 1999, upheld on 7 October 1999, having been rejected by the first-instance court (see the facts in the Levochkina v. Russia admissibility decision of 17 November 2005). Nor should it cover the whole period between 1 February 1998 and 1 May 2001. The period relevant to the violation of Article 1 of Protocol No. 1 is indicated in paragraph 46 above. Those adjustments being made, the Court awards the applicant 464 euros (EUR) in respect of pecuniary damage.
2. Non-pecuniary damage
58. The applicant claimed RUR 30,000 in respect of non-pecuniary damage.
59. The Court considers that the applicant has sustained non-pecuniary damage as a result of the violations found and that this cannot be made good merely by the Court's finding of a violation. It awards the applicant EUR 871 corresponding to the amount claimed.
B. Costs and expenses
60. The applicant claimed RUR 250.20 for postal expenses incurred in connection with her application to the Court. She also submitted three receipts on which the sums paid are not readable.
61. The Government agreed with the claim of RUR 250.20.
62. According to the Court's case-law, an applicant is entitled to reimbursement of his costs and expenses only in so far as it has been shown that these have been actually and necessarily incurred and were reasonable as to quantum. Having regard to the information in its possession, the Court awards the applicant EUR 7 in respect of costs and expenses.
C. Default interest
63. The Court considers it appropriate that the default interest should be based on the marginal lending rate of the European Central Bank, to which should be added three percentage points.
FOR THESE REASONS, THE COURT UNANIMOUSLY
1. Holds that there has been a violation of Article 6 § 1 of the Convention;
2. Holds that there has been a violation of Article 1 of Protocol No. 1 to the Convention;
3. Holds
(a) that the respondent State is to pay the applicant, within three months from the date on which the judgment becomes final in accordance with Article 44 § 2 of the Convention, the following amounts, to be converted into Russian roubles at the rate applicable at the date of settlement:
(i) EUR 464 (four hundred and sixty-four euros) in respect of pecuniary damage;
(ii) EUR 871 (eight hundred and seventy-one euros) in respect of non-pecuniary damage;
(iii) EUR 7 (seven euros) in respect of costs and expenses;
(iv) any tax that may be chargeable on the above amounts;
(b) that from the expiry of the above-mentioned three months until settlement simple interest shall be payable on the above amounts at a rate equal to the marginal lending rate of the European Central Bank during the default period plus three percentage points;
4. Dismisses the remainder of the applicant's claim for just satisfaction.
Done in English, and notified in writing on 5 July 2007, pursuant to Rule 77 §§ 2 and 3 of the Rules of Court.
Søren Nielsen Christos Rozakis
Registrar President
LEVOCHKINA v. RUSSIA JUDGMENT


Growing up, Peter was the kid who liked to take things apart – and put things back together. His love of troubleshooting – and problem-solving – led him to start his career as an operating engineer at the original World Trade Center. When working nights lost its appeal, he made a career change to become a design engineer.
Employee number five at WB, Peter is known for finding solutions for really complex problems. For example, following Superstorm Sandy, he designed a diving bell solution to protect Verizon's critical equipment at their downtown NYC communications hub. Although it is a centuries old concept, this was the first time it was applied in a Manhattan building.
Our engineers regard Peter as their go-to resource if they need to understand how something works (and they are guaranteed a thorough answer!).


text:
The Gaffers View
Managing an amateur football team in Scotland
The Winter Brakes
Sportsguard Insurance
The Worst Man For The Job
The Bastard Committee
The Teams That Train Together, Prosper Together?
When Will It Stop
A Negative Influence
#PassItOn
Starting The Process
An Open Letter To The SAFA
A Balancing Act
The View So Far
The Silly Season
The Player of the Year…
Winter Football – The Problems
The Amateur Class System
The Perfect Substitute
The Title Race
"We have all got work in the morning"
"He's the best player in amateur football"
Dealing with a clique
The weekend referee
"I'm not going to beat about the bush mate"
Rossvale AFC – In Focus
Oban Saints AFC – In Focus
Weirs Recreation AFC – In Focus
A Referees View
A Coaches View
Another Gaffers View
Amateur Football Links
Scottish Amateur FA Website
Scottish Amateur Football Forum
Pie and Bovril Website
Scottish Amateur Football League
Aberdeenshire AFA
Ayrshire AFA
Caledonian League
Fife AFA
Glasgow & District AFL
Greater Glasgow AFL
Lothian & Edinburgh AFL
Paisley & District AFL
March 31, 2016 ~ thegaffersview
Whether we like it or not, as players, coaches, managers and clubs we all fall into place in the class system that has developed over a number of years in amateur football. It shapes the way we talk about each other and it shapes our opinions even if we do our best not to let it.
In my opinion we have four clear class groups.
Sunday football is widely regarded as the poor cousin of amateur football in Scotland. This is probably due to the fact that a lot of players will be out drinking on a Saturday night, and the unpredictability of their sobriety for a match the following day. Sunday leagues also get a lot of stick for being on a par with pub leagues with inferior players who aren't good enough to play for a Saturday team. Historically Sunday football has been known for this but in recent times the trend is being bucked. There are thousands of quality players all over the country who play at a very good level of amateur football on a Saturday who also play for a team on the Sunday. The standard of Sunday football and the leagues in which teams participate in has certainly changed my view on it but perhaps you need to have watched games or been involved in them to appreciate who good some of these teams really are. There are players and managers who would never dream of being involved with a Sunday team because they would risk harming their reputation in the Saturday setups.
Does a day of the week really matter when you play football?
Saturday Morning Teams
One rung up on the ladder of class is the Saturday morning leagues of which there are a few. These teams struggle to attract the top players due to the class system and a bit of snobbery from players who consider themselves too good to "drop down" to Saturday morning teams. People don't realise that writing these teams off actually gives them added motivation to prove people wrong. How many times have you seen on twitter a morning team knocking one of the afternoon teams out of a national competition and then using words to the effect of "we are just a diddy Saturday morning team." This kind of proves my point that these teams accept their place in the class system albeit they might not agree with it. Acknowledging the fact that there is a clear divide would appear to me to be some form of acceptance.
It suits a lot of players' lifestyle to play football in the morning and get your game played giving you the rest of the day to spend with your family, going to watch your team or down the pub. Waiting around all day to kick off at two isn't feasible for some guys hence why the morning game suits them best? Does that make them poor players? Of course it doesn't. These leagues may not be as strong as the afternoon ones but that is because people write them off without giving them a chance and refuse to play in them.
It goes without saying that the top teams in amateur football all play in the afternoon. That is proved by the national competitions of which no Saturday morning team that I am aware of has ever won one. Teams in these leagues will try to attract players from the morning leagues by telling players that they don't want to be wasting their time playing morning football when they can come and play in a more attractive league with a higher standard. Does that say more about the standard of player in the morning league though or does it say more about the club trying to attract them? Afternoon players tend to be the worst when it comes to football snobbery. Many a time I have heard guys say they would be embarrassed to play on a Sunday or on a Saturday morning as they see it as dropping down a level. If you have never played at that "level" then how would you know? Continuing on from national cups from the morning section, the afternoon teams take a defeat to a morning team a lot harder than they would a fellow afternoon team because they think they should have enough in their kick off time locker to beat them before the game has even started.
Does the time of the day really matter when you play football?
The top of the tree of amateur football and the best league in the country, or is it?
It can't be argued that some of the best amateur players play in this league and historically their teams do well in the East, West and Scottish Cup but does that make it the top league in the country? I think the people in power in the league would say yes and probably the majority of the people involved would say that it is. Let me be clear this is in no way a bashing of the Central league, far from it actually, but I do believe that the league as a whole see themselves as a class apart from the rest of amateur football and in turn the rest of amateur football believe the hype. A fear factor has been created around the Central teams and people look to avoid drawing one of the teams in the cups. It's a fear factor without substance though because this is amateur football and any team can be beaten on any given day as we have seen so many times before.
We really need to drop the snobbery from some of our attitudes with regards to where we play our football. Sunday teams are littered with players who have won the Saturday Scottish Cup, Saturday morning teams are full of players who have played at a very good level of junior or professional football and afternoon leagues are have players who have played junior and won the Scottish Cup but would never play any other form of amateur.
We need to get over it.
Posted in Football
< Previous The Perfect Substitute
Next > Winter Football – The Problems
View TheGaffers View's profile on Facebook
View @thegaffersview's profile on Twitter
The Five Subs Rule
Beat The Stigma
A Safe Pair Of Hands
SAFA Website
Amateur Football Forum

redpajama_set_name: RedPajamaCommonCrawl


text:
Compare Our Best Mobile Phone Deals
Is the Google Pixel 7 worth buying in 2023?
Tuesday, September 27 2022
Joe Minihane
It's part of Google's 2022 Pixel range and built to showcase the very best of its Android operating system. So, is it worth buying? Read our full Google Pixel 7 review now to find out.
Our Google Pixel 7 review in summary
About the Google Pixel 7
Operating system and performance
Google Pixel 7's deals and incentives
Google Pixel 7 pricing
Pros and cons of choosing Google Pixel 7 in 2023
How does Google Pixel 7 compare against other Google phones?
Google Pixel 7 review: Verdict
Compare Google Pixel 7 deals
The Google Pixel 7 refines the Google Pixel 6 and comes with a new design that features a mental band across the back of the device.
Under the hood is Google's brand new Tensor 2 chipset, backed up by Android 13, the very latest smartphone operating system from the Big G.
Storage options are limited to 128GB and 256GB, smaller than many flagship phones, such as the iPhone 14 and Samsung's Galaxy S22, but that's fine unless you're big into gaming and downloading video.
The camera is what really makes the Pixel 7 stand out, with a seriously impressive night mode.
The Google Pixel 7 is built with Android lovers in mind. It shows off Google's mobile OS in its purest form and comes with the very best Google features and no annoying bloatware apps that often get in the way on third party Android devices.
The camera is what makes the Google Pixel 7 special. Google has opted for a main 50MP lens and a 12MP ultra wide sensor. The latter doesn't come with the same autofocus smarts found on the more expensive Pixel 7 Pro's ultrawide camera. However, the Pixel 7 is much more affordable, meaning this feature isn't something you'll miss if staying on budget is top priority.
Thanks to a series of tweaks to the camera software and the Tensor 2 chipset, the camera is a cut above older Pixel models. The Photo Unblur feature allows you edit blurry images and make them clear and crisp. Night Sight, a feature that gave the Pixel 6 an edge, has seen a number of technical enhancements, so that shots taken in the darkest conditions appear with greater clarity.
There are new and impressive creative features such as Action Pan and Long Exposure. Throw those in and Google continues to be top of the tree when it comes to smartphone imaging.
The front facing camera comes in at 10.8MP and can shoot 4K video, making it more than good enough for video calls and social media.
Google has made a few noticeable tweaks to the Pixel 7, while maintaining the broader design of the Pixel 6. It has dropped the two tone colour finish which caused uproar among mobile fanatics, instead opting for a neat metal band across the back of the device, where the main camera is housed.
The all screen finish is slick and in keeping with previous Pixel phones. And while swankier devices such as the Apple iPhone 14 Pro look better, the Pixel 7's lower price tag makes this easier to bear. Throw in water and dust proof ratings that will help stop any nasty breakages and you've got a rock solid modern smartphone.
The Pixel 7's screen looks virtually identical to that of the Pixel 6. It comes in at 6.3 inches, with a Full HD+ resolution and a 20:9 aspect ratio, with brightness topping out at 1,400 nits.
The 90Hz refresh rate puts it a little below rival devices such as Samsung's Galaxy S22 Ultra, which has a slicker 120Hz rating, making it marginally better for gaming and streaming video. Only hardcore users will discern the difference, though.
Always On display smarts for checking key details without unlocking the phone and an in screen fingerprint scanner mean the display here is a cut above similarly priced handsets.
This is an area where the Pixel 7 really stands out. It packs Google's new Tensor 23 chipset for snappy performance, and runs the very latest version of Android.
Android 13 is Google's best OS yet, with updated apps and a far slicker overall experience. Pixel devices have long been the best way to experience Android as Google intends, and with the latest updates hitting these handsets before any others, the Pixel 7 is the way to go if you value the newest software.
The Pixel 7 can last around a single day on one charge when streaming video, checking social media and taking calls. That puts it in line with most handsets at the same price point. For those who can't get to power easily, an Extreme Battery Saver mode promises 72 hours between charges, letting you 'white list' apps you want to use while denying access to those you don't.
There's support for 21W fast charging, but as with most phones these days there's no charger in the box.
There are loads of great Pixel 7 deals and incentives here at MoneySuperMarket. iD Mobile offers money off with a dedicated discount code and offers three months of free Apple TV+ and Apple Music when you take out a deal.
Prices are competitive too, with a number of networks vying for your business. Take a look at our price comparison tool and you'll see deals from as low as £29 per month (at the time of writing).
SIM free pricing for the Pixel 7 is competitive. At launch, a 128GB model costs £599, rising to £699 for 256GB. That compares very well against more expensive phones from Samsung and Apple.
Tensor 2 chipset ensures great performance
Android 13 means very latest software out of the box
Great camera
Only a minor update compared with Pixel 6
The Pixel 7 is part of Google's 2022 range. As the name suggests, the Pixel 7 Pro offers a better camera and sleeker screen, but costs more.
The older Pixel 6 has many of the same features, while the Pixel 6a serves up the best of Google at a lower price.
The Google Pixel 7 is a great phone at a really good price. With the best of Google's new chipset tech, the latest Android software and an excellent camera, it marks an affordable alternative to the iPhone 14 and Samsung Galaxy S22, with features that match each of those phones.
Compare great mobile phone or SIM deals
Pay monthly Handsets only Best SIM only deals No upfront cost handsets


text:
ABO: Interactive Journal for Women in the Arts, 1640-1830
About This IR
Scholar Commons > Open Access Journals > ABO > Vol. 7 (2017) > Iss. 1
Arabella's Valentines and Literary Connections [dot] com: Playing with Eighteenth-Century Gender Online
Melanie D. Holm, Indiana University of PennsylvaniaFollow
Melanie Holm is an Assistant Professor at Indiana University of Pennsylvania. She is currently at work on a book tentatively titled "The Skeptical Imagination: Gender, Genre, and Sociability in Literature of the Eighteenth Century" that explores the role of skepticism in experiments with gender and genre that seek out new possibilities of social engagement for eighteenth-century readers.
This article describes two digital assignments that ask students to imaginatively embody characters from eighteenth-century texts written by women in order to cultivate a greater awareness of the critical role of gender and gender critique in these works. The first of these assignments, "Arabella's Valentines," asks students to translate dialogue from Charlotte Lennox's The Female Quixote as humorous Internet memes. The second assignment, "Literary Connections [dot] com," asks students to imagine how characters from the course archive might represent themselves on an internet dating site. Through creative role-play facilitated by these digital genres, students engage with the texts in stimulating and playful ways that extends their consideration of writers' works beyond the page. In the article I explain how these activities were deployed using PowerPoint and Tumblr, and for the second assignment, Google Forms, with step-by-step instructions for replicating the technological aspects of the assignments, and add reflections on the outcome of these assignments for student learning.
digital, tumblr, pedagogy, lennox, quixotism, quixote, gender, women's writing, online assignments, social media
Holm, Melanie D. (2017) "Arabella's Valentines and Literary Connections [dot] com: Playing with Eighteenth-Century Gender Online," ABO: Interactive Journal for Women in the Arts, 1640-1830: Vol.7: Iss.1, Article 5.
http://doi.org/10.5038/2157-7129.7.1.1138
Available at: https://digitalcommons.usf.edu/abo/vol7/iss1/5
Dramatic Literature, Criticism and Theory Commons, Educational Methods Commons, Literature in English, British Isles Commons, Women's Studies Commons
ABO home
About ABO
ABOPublic
All Issues Vol. 11, Iss. 2 Vol. 11, Iss. 1 Vol. 10, Iss. 2 Vol. 10, Iss. 1 Vol. 9, Iss. 2 Vol. 9, Iss. 1 Vol. 8, Iss. 2 Vol. 8, Iss. 1 Vol. 7, Iss. 2 Vol. 7, Iss. 1 Vol. 6, Iss. 2 Vol. 6, Iss. 1 Vol. 5, Iss. 2 Vol. 5, Iss. 1 Vol. 4, Iss. 2 Vol. 4, Iss. 1 Vol. 3, Iss. 2 Vol. 3, Iss. 1 Vol. 2, Iss. 2 Vol. 2, Iss. 1 Vol. 1, Iss. 1
Tweets by @ABOwomeninarts
USF Scholar Commons
ABO's entry in DOAJ
Scholar Commons | About This IR | FAQ | My Account | Accessibility Statement


text:
/*
 * DO NOT EDIT THIS FILE!
 *
 * Automatically generated by SCons
 */

#ifndef __DEBUG_IPI_HH__
#define __DEBUG_IPI_HH__

namespace Debug {
class SimpleFlag;
extern SimpleFlag IPI;
}

#endif // __DEBUG_IPI_HH__

redpajama_set_name: RedPajamaGithub


A Montreal to New York City train was traveling near Albany, New York at about 7:20 p.m. on Wednesday when two cars separated from the engine, Amtrak spokesman Jason Abrams said in a statement. Of the 287 passengers and crew, he said, no one was injured. The passengers were transferred to a new train, Abrams said.
NEW YORK — Hundreds of passengers on an Amtrak train that became disconnected will have quite a story to tell around the Thanksgiving table.
The Montreal to New York City train was traveling near Albany, New York at about 7:20 p.m. on Wednesday when two cars separated from the engine, Amtrak spokesman Jason Abrams said in a statement. Of the 287 passengers and crew, he said, no one was injured. The passengers were transferred to a new train, Abrams said.
CNN has reached out to Amtrak for further details but has not heard back.
He heard a noise and turned around to see cars behind him rip apart from the train, he said. That's when one passenger pulled the emergency brake to stop the train and others — upon smelling smoke — grabbed the fire extinguisher.
Helen Mary Crane was with her son on the way to spend the holiday with her daughter. Crane said two cars were added to the train when she boarded in Rensselaer, New York and that she and her son were told to sit in the first of the additions.
Crane's car was one of the two to break off.
CNN has reached out to the National Transportation Safety Board, but has not heard back.
The New York State Police is investigating the incident.


text:
FITZPATRICK, AMY L thru FITZPATRICK, ANDREW
FITZPATRICK, AMY L. married JOE ROGERS on 16 August 2003 using a marriage license issued in Vigo County, Indiana, United States of America. 53,934,301
Check the source file (free) and then check Archives for AMY L. FITZPATRICK.
FITZPATRICK, AMY L. was born 18 October 1966, received Social Security number 362-82-0659 (indicating Michigan) and, Death Master File says, died 01 December 2006 53,934,302
Check the source file (free) and then check Archives for AMY L FITZPATRICK.
FITZPATRICK, AMY M. (bride), who was 19 years old, White, with no previous marriage, and WILLIAM C. JOHNSON, who was 22 years old, White, status 1 (Never married) had a wedding ceremony 17 July 1993 on a license issued in Lawrence County, Kentucky, United States of America (Certificate number 23422) with the intention of residing in McCreary County, Kentucky. 53,934,303
Check the source file (free) and then check Archives for AMY M FITZPATRICK.
FITZPATRICK, AMY M. was born 22 February 1910, received Social Security number 318-10-4120 (indicating Illinois) and, Death Master File says, died 12 January 1989 53,934,304
FITZPATRICK, A. N. (mother) , and M. Fitzpatrick, had a baby boy, Dan V. FITZPATRICK born 23 Nov 1889 in Raleigh Co. County, West Virginia, U.S.A.. 53,934,305
Check the source file (free) and then check Archives for A. N. FITZPATRICK.
FITZPATRICK, An was born ABT 1832 in Co Down, and she was in the 1901 census for Islandmagee, Clonduff, County Down, Ireland 53,934,306
Check the source file (free) and then check Archives for An FITZPATRICK.
FITZPATRICK, ANA E. married a groom named ISRAEL PEREZ in the year 1977 on license number 2896 issued in Manhattan, New York City, New York, U.S.A. 53,934,307
Check the source file (free) and then check Archives for ANA E. FITZPATRICK.
FITZPATRICK, ANA I. was born 29 July 1904, received Social Security number 582-66-9101 (indicating Puerto Rico) and, Death Master File says, died 15 May 1996 53,934,308
Check the source file (free) and then check Archives for ANA I FITZPATRICK.
FITZPATRICK, ANASTASIA was born 14 December 1903, received Social Security number 015-07-7683 (indicating Massachusetts) and, Death Master File says, died 15 March 1994 53,934,309
Check the source file (free) and then check Archives for ANASTASIA FITZPATRICK.
FITZPATRICK, ANASTASIA was born 22 July 1897, received Social Security number 129-05-4437 (indicating New York) and, Death Master File says, died January 1981 53,934,310
FITZPATRICK, ANASTASIA died 19 March 1994 at age 90, and was buried in Yard 5D Range 54 Section - Lot 3A Grave 2A of Saint Patrick Cemetery in Lowell, Massachusetts, U.S.A. 53,934,311
FITZPATRICK, Anastasia was born ABT 1831 in Co Kilkenny, was in the 1901 census for Johnstown, Johnstown, County Kilkenny, Ireland 53,934,312
FITZPATRICK, Anastasia was born ABT 1838 in Co Kilkenny and she was in the 1911 census for Mill Street, Callan Urban, County Kilkenny, Ireland 53,934,313
FITZPATRICK, Anastasia was born ABT 1854 in Co Wexford, she married William Fitzpatrick ABT 1883, and she was in the 1911 census for Horetown, Killinick, County Wexford, Ireland 53,934,314
FITZPATRICK, Anastasia was born ABT 1862 in Co Kilkenny, she married Daniel Fitzpatrick ABT 1891, and she was in the 1911 census for Archerstown, Aghmacart, Queen's County (now known as County Laois), Ireland 53,934,315
FITZPATRICK, Anastasia was born ABT 1871 in Co Kilkenny, (daughter of William Gannon) was in the 1901 census for Rathbane, Galmoy, County Kilkenny, Ireland 53,934,316
FITZPATRICK, Anastasia was born ABT 1873 in Co Wicklow, she married Michael Fitzpatrick ABT 1895, and she was in the 1911 census for Blackditches, Upper, Togher, County Wicklow, Ireland 53,934,317
FITZPATRICK, Anastasia was born ABT 1875 in City of Dublin, was in the 1911 census for Francis St., Wood Quay, County Dublin, Ireland 53,934,318
FITZPATRICK, Anastasia was born ABT 1875 in Co Cork, (daughter of Jeremiah Fitzpatrick) was in the 1901 census for Derrishal, Ballyhoolahan, County Cork, Ireland 53,934,319
FITZPATRICK, Anastasia was born ABT 1881 in Queens Co, (daughter of Catherine Fitzpatrick) was in the 1911 census for Moat, Dysartgallen, Queen's County (now known as County Laois), Ireland 53,934,320
FITZPATRICK, Anastasia was born ABT 1884 in Kings County, (daughter of Patrick Fitzpatrick) was in the 1901 census for Ballyduff, Gorteen, King's County (now known as County Offaly), Ireland 53,934,321
FITZPATRICK, Anastasia was born ABT 1905 in Queen's Co, (daughter of Daniel Fitzpatrick) was in the 1911 census for Archerstown, Aghmacart, Queen's County (now known as County Laois), Ireland 53,934,322
Fitzpatrick, Anastasia died in 1893 according to a Massachusetts vital record for Lowell, Volume 437, Page 260. 53,934,323
Fitzpatrick, Anastasia died in 1894 according to a Massachusetts vital record for Stoughton, Volume 446, Page 537. 53,934,324
Fitzpatrick, Anastasia was born in 1886 according to a Massachusetts vital record for Boston, Volume 369, Page 97. 53,934,325
Fitzpatrick, Anastasia (alias Schofield) died in 1869 according to a Massachusetts vital record for Boston, Volume 222, Page 100. 53,934,326
Check the source file (free) and then check Archives for Anastasia (alias Schofield) Fitzpatrick.
FITZPATRICK, ANASTASIA M. was born 21 March 1902, received Social Security number 385-24-4425 (indicating Michigan) and, Death Master File says, died September 1993 53,934,327
Check the source file (free) and then check Archives for ANASTASIA M FITZPATRICK.
FITZPATRICK, ANASTASIA T. was born 06 September 1906, received Social Security number 180-18-5349 (indicating Pennsylvania) and, Death Master File says, died 06 December 1990 53,934,328
Check the source file (free) and then check Archives for ANASTASIA T FITZPATRICK.
FITZPATRICK, Anastatia was born ABT 1836 in Co Kilkenny and she was in the 1901 census for Mill Street, Callan Urban, County Kilkenny, Ireland 53,934,329
Check the source file (free) and then check Archives for Anastatia FITZPATRICK.
FITZPATRICK, Anastatia was born ABT 1867 in Co Kilkenny, she married Michael Fitzpatrick ABT 1889, and she was in the 1911 census for Rathbane, Galmoy, County Kilkenny, Ireland 53,934,330
FITZPATRICK, Anastatia was born ABT 1877 in Co Kilkenny, she married Edward Fitzpatrick ABT 1905, and she was in the 1911 census for Knockmoylan, Kilkeasy, County Kilkenny, Ireland 53,934,331
FITZPATRICK, Anastatia was born ABT 1886 in Co Kilkenny, (daughter of Laurence Fitzpatrick) was in the 1901 census for Castlewarren, Tiscoffin, County Kilkenny, Ireland 53,934,332
FITZPATRICK, Anastatia was born ABT 1886 in Kings Co, (daughter of Patrick Fitzpatrick) was in the 1911 census for Ballyduff, Gorteen, King's County (now known as County Offaly), Ireland 53,934,333
FITZPATRICK, Anastatia was born ABT 1891 in Co Kilkenny, (daughter of Michael Fitzpatrick) was in the 1901 census for Ballintee, Dunnamaggan, County Kilkenny, Ireland 53,934,334
FITZPATRICK, Anastatia was born ABT 1894 in Co Kilkenny, (daughter of Michael Fitzpatrick) was in the 1911 census for Ballintee, Dinnamaggan, County Kilkenny, Ireland 53,934,335
FITZPATRICK, Anastatia was born ABT 1895 in Co Dublin, (daughter of John Fitzpatrick) was in the 1901 census for Victoria Buildings, Blackrock, County Dublin, Ireland 53,934,336
FITZPATRICK, Anastatia was born ABT 1899 in Co Kilkenny, (daughter of Margaret Fitzpatrick) was in the 1901 census for Ennisnag, Ennisnag, County Kilkenny, Ireland 53,934,337
FITZPATRICK, Anastatia was born ABT 1901 in Co Kilkenny, (daughter of Michael Fitzpatrick) was in the 1911 census for Fountain Street, Waterford No. 5 Urban, County Waterford, Ireland 53,934,338
FITZPATRICK, Anastatin was born ABT 1889 in Wexford, was in the 1911 census for South Main Street, part of, Wexford No. 2 Urban, County Wexford, Ireland 53,934,339
Check the source file (free) and then check Archives for Anastatin FITZPATRICK.
FITZPATRICK, Anastia was born ABT 1882 in Queens Co, (daughter of Kathrin Fitzpatrick) was in the 1911 census for Stucker Hill, Abbeyleix, Queen's County (now known as County Laois), Ireland 53,934,340
Check the source file (free) and then check Archives for Anastia FITZPATRICK.
FITZPATRICK, Anastia was born ABT 1892 in Co Dublin, (daughter of Mary Ellen Fitzpatrick) was in the 1901 census for Skirteen, Monasterevan, County Kildare, Ireland 53,934,341
FITZPATRICK, ANDERSON was born 10 July 1891, received Social Security number 252-52-9424 (indicating Georgia) and, Death Master File says, died March 1980 53,934,342
Check the source file (free) and then check Archives for ANDERSON FITZPATRICK.
FITZPATRICK, ANDREA married a groom named RICHARD SUTCAMP in the year 1972 on license number 25270 issued in Manhattan, New York City, New York, U.S.A. 53,934,343
Check the source file (free) and then check Archives for ANDREA FITZPATRICK.
FITZPATRICK, ANDREA married HENRY SMITTY on 8 June 1996 using a marriage license issued in Marion County, Indiana, United States of America. 53,934,344
FITZPATRICK, ANDREA married JOHN ARNOLD GROSLINGER 30 October 2004 in Kinnelon Boro, Morris County, New Jersey, United States of America. Special thanks to Reclaim The Records. Please consider donating to them. 53,934,345
FITZPATRICK, ANDREA C. married a groom named PATRICK J. KELLY in the year 1986 on license number 26145 issued in Manhattan, New York City, New York, U.S.A. 53,934,346
Check the source file (free) and then check Archives for ANDREA C. FITZPATRICK.
FITZPATRICK, ANDREA H. was born 12 July 1968, received Social Security number 433-61-8141 (indicating Louisiana) and, Death Master File says, died 12 June 2013 53,934,347
Check the source file (free) and then check Archives for ANDREA H FITZPATRICK.
FITZPATRICK, ANDREA L. married HENRY M. SMITH JR on 8 June 1996 using a marriage license issued in Marion County, Indiana, United States of America. 53,934,348
Check the source file (free) and then check Archives for ANDREA L. FITZPATRICK.
FITZPATRICK, ANDREA LYNN married WILLIAM PATRICK REYNOLDS 18 September 2004 in Wyckoff Township, Bergen County, New Jersey, United States of America. Special thanks to Reclaim The Records. Please consider donating to them. 53,934,349
Check the source file (free) and then check Archives for ANDREA LYNN FITZPATRICK.
FITZPATRICK, ANDREA M who was 21 (born ABT 1978) married 20 NOV 1999 in MC LENNAN COUNTY, TEXAS, U.S.A. a groom named JUSTIN W PRAESEL who was 22 (born ABT 1977). 53,934,350
Check the source file (free) and then check Archives for ANDREA M FITZPATRICK.
FITZPATRICK, ANDREW JR, born ABT 1952, and his bride MARY L, born ABT 1947, married 9 OCT 1984, and they had no children under 18 when they got divorced in HARRIS COUNTY, TEXAS, U.S.A. on 25 JUN 1987. 53,934,351
Check the source file (free) and then check Archives for ANDREW JR FITZPATRICK.
FITZPATRICK, ANDREW married a bride named MARY KIGGINS in the year 1952 on license number 7255 issued in Bronx, New York City, New York, U.S.A. 53,934,352
Check the source file (free) and then check Archives for ANDREW FITZPATRICK.
FITZPATRICK, ANDREW married a bride named MARY THERIAULT in the year 1956 on license number 8310 issued in Queens, New York City, New York, U.S.A. 53,934,353
FITZPATRICK, ANDREW married a bride named MARY WHEELER in the year 1963 on license number 5608 issued in Manhattan, New York City, New York, U.S.A. 53,934,354
FITZPATRICK, ANDREW married a bride named PHILOMENA HUGHES in the year 1957 on license number 7087 issued in Manhattan, New York City, New York, U.S.A. 53,934,355
FITZPATRICK, ANDREW was born 08 August 1912, received Social Security number 430-18-8979 (indicating Arkansas) and, Death Master File says, died November 1976 53,934,356
FITZPATRICK, ANDREW was born 09 August 1917, received Social Security number 346-12-2575 (indicating Illinois) and, Death Master File says, died 29 October 1992 53,934,357
FITZPATRICK, ANDREW was born 10 November 1928, received Social Security number 074-22-8023 (indicating New York) and, Death Master File says, died 26 August 1988 53,934,358
FITZPATRICK, ANDREW was born 10 September 1873, received Social Security number 293-34-6679 (indicating Ohio) and, Death Master File says, died September 1975 53,934,359
FITZPATRICK, ANDREW was born 13 July 1915, received Social Security number 090-07-7318 (indicating New York) and, Death Master File says, died July 1987 53,934,360
FITZPATRICK, ANDREW was born 14 June 1904, received Social Security number 166-26-5197 (indicating Pennsylvania) and, Death Master File says, died June 1980 53,934,361
FITZPATRICK, ANDREW was born 15 November 1900, received Social Security number 164-09-2263 (indicating Pennsylvania) and, Death Master File says, died August 1983 53,934,362
FITZPATRICK, ANDREW was born 17 August 1888, received Social Security number 356-30-0376 (indicating Illinois) and, Death Master File says, died November 1972 53,934,363
FITZPATRICK, ANDREW was born 17 February 1900, received Social Security number 116-12-0924 (indicating New York) and, Death Master File says, died January 1973 53,934,364
FITZPATRICK, ANDREW was born 17 September 1924, received Social Security number 465-20-0287 (indicating Texas) and, Death Master File says, died March 1984 53,934,365
FITZPATRICK, ANDREW was born 21 September 1964, received Social Security number 086-50-4577 (indicating New York) and, Death Master File says, died 03 April 1995 53,934,366
FITZPATRICK, ANDREW was born 25 November 1909, received Social Security number 234-16-2214 (indicating West Virginia) and, Death Master File says, died August 1980 53,934,367
FITZPATRICK, ANDREW was born 27 March 1894, received Social Security number 215-05-3533 (indicating Maryland) and, Death Master File says, died August 1974 53,934,368
FITZPATRICK, ANDREW was born 30 May 1930, received Social Security number 058-22-2859 (indicating New York) and, Death Master File says, died June 1977 53,934,369
FITZPATRICK, ANDREW was born 31 January 1911, received Social Security number 214-01-1693 (indicating Maryland) and, Death Master File says, died June 1974 53,934,370
FITZPATRICK, ANDREW married RACHAEL PRINCIPE on 23 June 2018 using a marriage license issued in Starke County, Indiana, United States of America. 53,934,371
FITZPATRICK, Andrew was born ABT 1832 in Ohio; was in the 1850 census in Vinton County, Ohio. 53,934,372
Check the source file (free) and then check Archives for Andrew * FITZPATRICK.
FITZPATRICK, Andrew married 26 Jun 1906 in Chester, Hancock, West Virginia, U.S.A. a bride named Margaret Hanley. 53,934,373
FITZPATRICK, Andrew (father) , and Mary [no surname shown], had a baby, Thomas FITZPATRICK born 17 Apr 1846 in Brant, Ontario, Canada. 53,934,374
FITZPATRICK, Andrew was born ABT 1832 in Co Carlow and he was in the 1911 census for Craan, St. Mary's, County Wexford, Ireland 53,934,375
FITZPATRICK, Andrew was born ABT 1832 in Co Fermanagh and he was in the 1901 census for Drumbroughas West, Derrylea, County Fermanagh, Ireland 53,934,376
FITZPATRICK, Andrew was born ABT 1834 in Co Carlow and he was in the 1901 census for Deerpark Old, Cranemore, County Carlow, Ireland 53,934,377
FITZPATRICK, Andrew was born ABT 1835 in Co Wexford and he was in the 1901 census for Handkerchief Alley, Merchants Quay, County Dublin, Ireland 53,934,378
FITZPATRICK, Andrew was born ABT 1836 in Carlow and he was in the 1911 census for Deerpark Old, Cranemore, County Carlow, Ireland 53,934,379
FITZPATRICK, Andrew was born ABT 1836 in Co Cavan, was in the 1901 census for Kilnagarbet, Laragh North, County Cavan, Ireland 53,934,380
FITZPATRICK, Andrew was born ABT 1838 in Co Carlow and he was in the 1911 census for Temple Road, Rathmines & Rathgar East, County Dublin, Ireland 53,934,381
FITZPATRICK, Andrew was born ABT 1840 in Co Carlow and he was in the 1901 census for Rochestown Demesne, Ballybrack, County Dublin, Ireland 53,934,382
FITZPATRICK, Andrew was born ABT 1840 in Queen's Co and he was in the 1911 census for Killinure, Lacka, Queen's County (now known as County Laois), Ireland 53,934,383
FITZPATRICK, Andrew was born ABT 1843 in Co Down and he was in the 1911 census for Rathmullan Lower, Tyrella, County Down, Ireland 53,934,384
FITZPATRICK, Andrew was born ABT 1843 in County Dublin and he was in the 1911 census for Newtown, Swords West, County Dublin, Ireland 53,934,385
FITZPATRICK, Andrew was born ABT 1846 in Co Dublin and he was in the 1901 census for Newtown, Swords, County Dublin, Ireland 53,934,387
FITZPATRICK, Andrew was born ABT 1852 in Co Clare, was in the 1911 census for Fermoyle West, Gleninagh, County Clare, Ireland 53,934,388
FITZPATRICK, Andrew was born ABT 1854 in Co Dublin and he was in the 1911 census for Tolka Cottages, Drumcondra, County Dublin, Ireland 53,934,389
FITZPATRICK, Andrew was born ABT 1859 in Co Dublin and he was in the 1911 census for Wyestown, Garristown, County Dublin, Ireland 53,934,390
FITZPATRICK, Andrew was born ABT 1861 in City Dublin and he was in the 1901 census for Emerald Terrace, Merchants Quay, County Dublin, Ireland 53,934,391
FITZPATRICK, Andrew was born ABT 1861 in Clare, (son of James Fitzpatrick) was in the 1901 census for Fermoyle West, Gleninagh, County Clare, Ireland 53,934,392
FITZPATRICK, Andrew was born ABT 1861 in Dublin City and he was in the 1911 census for Tipper Road, Naas Urban, County Kildare, Ireland 53,934,394
FITZPATRICK, Andrew was born ABT 1865 in County Down, was in the 1901 census for Blackwatertown, Charlemont, County Armagh, Ireland 53,934,395
FITZPATRICK, Andrew was born ABT 1870 in Dublin City, (son of Catherine Fitzpatrick) was in the 1911 census for Chaworth Terrace, Usher's Quay, County Dublin, Ireland 53,934,396
FITZPATRICK, Andrew was born ABT 1871 in City of Dublin, (son of Catherine Fitzpatrick) was in the 1901 census for Garden Lane, Wood Quay, County Dublin, Ireland 53,934,397
FITZPATRICK, Andrew was born ABT 1872 in Co Wexford and he was in the 1901 census for Knockingin, Balbriggan Rural, County Dublin, Ireland 53,934,398
FITZPATRICK, Andrew was born ABT 1873 in Co Cavan and he was in the 1901 census for Seaforde Street, Pottinger, County Down, Ireland 53,934,399
FITZPATRICK, Andrew was born ABT 1873 in Co Wexford and he was in the 1911 census for Knocknagin, Balbriggan Rural, County Dublin, Ireland 53,934,400


text:
Magnatone Introduces Varsity Reverb Amplifier
Category: Guitar News
Magnatone has announced its new Varsity Reverb amplifier. From the company:
The Varsity is quickly becoming a favorite amplifier for gigging guitarists (ask Jeff Beck). Now there's an even more versatile option: the Varsity Reverb. Same specs and great tone. As with all Magnatone amps, the Varsity Reverb is made with all American parts and true point-to-point wiring.
"The Varsity was designed to deliver that classic, all-American tone in studio with rich harmonics, amazing headroom with touch-sensitivity to die for," said Magnatone Founder and President Ted Kornblum. "The new Varsity Reverb provides more range and options, and has the muscle to accompany artists on-stage."
The Varsity Reverb is a push-pull 15-watt amplifier powered by two EL84 power tubes and has traditional Magnatone vintage brown and gold cosmetics.
This popular tube amplifier is bright and lively, full of color and harmonics. The dual 12AX7s in the preamp provide a classic American tone. Combined with tube-driven full length Accutronics spring reverb, the Varsity Reverb delivers a sound much bigger than the power rating. The new Varsity Reverb is also foot-switch compatible, so you can control the negative feedback feature by pedal as well as on/off reverb.
"We are excited to see artists using our amps in live performances, including David Crosby who is using the new Varsity Reverb on tour this May in support of his new album, Lighthouse," said Kornblum.
The Varsity Reverb, part of Magnatone's Traditional Collection, was previewed at the 2017 Winter NAMM Show in January and is now available from retailers worldwide.
To learn more about the Varsity Reverb and Magnatone's full range of professional amplifiers, featuring Magnatone's true pitch shifting vibrato available in mono or stereo, magnatoneusa.com[1].
^ magnatoneusa.com (magnatoneusa.com)
Read more from our friends at Guitar World
Featured in Guitars
Damjan Pejcinoski - All of Me
Damjan Pejcinoski born in 1984, is a Macedonian guitarist who lives in Ohrid, Macedonia. Pejcinoski started playing guitar at the age of six, but his real interest in guitar started when he was 14. He attended school in Ohrid, where he developed his musical skills playing rock music influenced by Deep Purple, AC/DC, Whitesnake, Steve Vai, Joe Satriani, Frank Gambale, Greg Howe and many more. He honed his talents the old fashioned way, gigging in night clubs in Macedonia.


text:
RankPro: 287 U-Multirank: 826/1269 Webometrics: 1677/1865 ShanghaiRanking - Mathematics: 401-500 ShanghaiRanking - Clinical Medicine: 201-300 U.S. News Rankings: 1216/1250 URAP Ranking: 1377/2500 QS Rankings: 301-350 SCImago: 693 SJR Rank - Match: RS 1/55 World 2007 UI GreenMetric Ranking: 320/619
Former rectors
Quality assurance and improvement
Why study at the University of Kragujevac?
Higher education system in Serbia
Study programmes in Serbian
Study programmes in foreign languages
Verification of the documents
Centres of Excellence of the University of Kragujevac
Center for Scientific Research of Serbian Academy of Sciences and Arts and the University of Kragujevac
Research Units at the faculties
Department for International Cooperation
International Projects Office
Center for Career Development and Student Counselling
Mobility programmes
International Strategy and Action Plan
Mobility Strategy and Action Plan
Center SANU publications
Journals - publications of the faculties
University gallery
Faculty of Agronomy
Faculty of Mechanical and Civil Engineering
Faculty of Education in Jagodina
Faculty of Education in Užice
Faculty of Philology and Arts
Faculty of Hotel Management and Tourism
Institute for Information Technologies
Student organizations and associations
Students' events
University IT Centre - UNIC
Centers – International projects results
Knowledge Transfer Center
Collaborative Training Centre
Creativity Centre
Business Support Office
International projects partner institutions
Center for Scientific Research founded by the Serbian Academy of Science and Arts and the University of Kragujevac was established on the 21st of May 1991 with the aim to encourage and develop scientific, educational and cultural activities of the wide area gravitating towards the University.
The first director of the Centre was Dragoslav Srejovic (1931-1996), an archaeologist born in Kragujevac, who held the post since the establishment of the Centre, until his death in 1996. He was succeeded by Academician Nikola Tasic, archaeologist, Vice-President of SASA, who performed his duty of the Centre director until 2010. Academician Ivan Gutman, a chemist and a professor emeritus of the University of Kragujevac, was appointed as director of the Centre, in 2011, and in October 2018, Milos Duran, PhD, correspondent member of SASA, was appointed as administrator of the Centre, for 4 years term.
In 2011, Serbian Academy of Sciences and Arts and the University of Kragujevac adopted new acts of the Center: Agreement on regulation of mutual relations and the Rules of Procedure and the organizational structure of the Centre was chaged to ensure its efficient operation.
Center for Scientific Research does not have legal personality, it has the status of an organizational unit of the University. Basic activities of the Center are realized through the work on the research projects (especially research in the sciences that are not being studied at the University of Kragujevac, as well as multidisciplinary research), organization of scientific meetings, discussions, lectures, exhibitions and other scientific and cultural events. Particularly important part of the Centre is publishing activity. Center publishes scientific and professional monographs, proceedings, and other types of publications that are important for the development of science, culture and the arts.
Milos Djuran, corresponding member of SASA
Full professor of the Faculty of Sciences in Kragujevac
E-mail: djuran@kg.ac.rs
Lela Vujosevic, professor of sociology
E-mail: lela.vujosevic@kg.ac.rs
Address: Jovana Cvijica b.b., 34000 Kragujevac, Serbia
Phone: +381 (0)34 370-270
Fax: +381 (0)34 370-168
LIFE IN KRAGUJEVAC
About Kragujevac
Manifestations in Kragujevac
Exchange and visiting staff
Incoming researches
Institutional logistic support
Buddy Network
E+ Alumni
Key academic dates
How to reach Kragujevac
Registration upon arrival
Support to students with disability
Currency and exchange offices
Cost of living and shopping
Important and useful numbers
Communication and internet


text:
<?php
namespace frontend\modules\hosxpwarning\controllers;

use yii\web\Controller;
use yii\db\Query;
use Yii;
use yii\data\ArrayDataProvider;

//AccessControl
use mdm\admin\components\AccessControl;
use yii\filters\VerbFilter;

class HosxpwarningController extends Controller {
    public function behaviors(){
        return [
            'access' => [
                'class' => AccessControl::className(),
                'allowActions' => ['index']
            ],

            'verbs' => [
                'class' => VerbFilter::className(),
                'actions' => [
                    'logout' => ['post'],
                ],
            ],
        ];
    }

    public function actionIndex() {
        $date_start = "2015-10-01";
        $sql_chart1 = "SELECT COUNT(DISTINCT hn) AS cc_hn FROM vn_stat WHERE vstdate  BETWEEN '$date_start' AND DATE(NOW())AND (pdx='' OR pdx IS NULL)";
        $sql_chart2 = "SELECT COUNT(DISTINCT hn) AS cc_hn FROM an_stat  WHERE  dchdate BETWEEN '$date_start' AND DATE(NOW())AND (pdx='' OR pdx IS NULL)";
        $sql_chart3 = "SELECT COUNT(DISTINCT hn) AS cc_hn FROM patient WHERE  patient.hn  IN (SELECT hn FROM vn_stat WHERE vstdate  BETWEEN '$date_start' AND DATE(NOW())) AND (patient.type_area='' OR patient.type_area<>'4' OR patient.type_area IS NULL)";
        $sql_chart4 = "SELECT COUNT(DISTINCT p.hn) AS cc_hn
        FROM er_nursing_detail en
        INNER JOIN ovst o ON o.vn=en.vn
        INNER JOIN ovst_seq os ON os.vn=en.vn
        INNER JOIN er_regist e ON e.vn=o.vn
        INNER JOIN er_pt_type erpt ON erpt.er_pt_type=e.er_pt_type AND erpt.accident_code='Y'
        INNER JOIN patient p ON p.hn=o.hn
        INNER JOIN pq_screen  pq ON pq.vn=en.vn
        INNER JOIN opduser ou ON ou.loginname=pq.staff
        WHERE e.vstdate BETWEEN '$date_start' AND DATE(NOW())
        AND (en.accident_place_type_id='' OR en.accident_place_type_id IS NULL
        or en.visit_type='' OR en.visit_type IS NULL
        or en.accident_alcohol_type_id='' OR en.accident_alcohol_type_id IS NULL
        or en.accident_drug_type_id='' OR en.accident_drug_type_id IS NULL
        or en.accident_airway_type_id='' OR en.accident_airway_type_id IS NULL
        or en.accident_bleed_type_id='' OR en.accident_bleed_type_id IS NULL
        or en.accident_splint_type_id='' OR en.accident_splint_type_id IS NULL
        or en.accident_fluid_type_id='' OR en.accident_fluid_type_id IS NULL
        or en.er_emergency_type='' OR en.er_emergency_type IS NULL )
        ORDER BY e.enter_er_time";
        $sql_chart5 = "SELECT COUNT(DISTINCT o.hn) AS cc_hn FROM ovstdiag o WHERE  o.vstdate  BETWEEN '$date_start' AND DATE(NOW())
                       AND (o.diagtype='' OR o.diagtype IS NULL OR o.diagtype NOT IN('1','2','3','4','5','6','7'))";
        $sql_chart6 = "SELECT COUNT(DISTINCT person_id)AS cc_pid FROM person WHERE house_regist_type_id IN ('1','3')
                       AND nationality<>'99' AND death='N'";
        $sql_chart7 = "SELECT  COUNT(DISTINCT person_id)AS cc_pid FROM person WHERE house_regist_type_id IN ('1','3') AND person_discharge_id<>'9'AND death='N'";
        $sql_chart8 = "SELECT COUNT(DISTINCT person_id) AS cc_pid FROM person WHERE village_id='1' AND house_regist_type_id IN ('1','3')";
        $sql_chart9 = "SELECT COUNT(house_id) AS cc_house FROM house WHERE (location_area_id IS NULL  OR location_area_id= ''
                       OR house_type_id IS NULL OR house_type_id= '' OR house_subtype_id  IS NULL OR house_subtype_id ='')";
        $sql_chart10 = "SELECT COUNT(DISTINCT person_id)AS cc_pid FROM person WHERE (house_regist_type_id='' OR house_regist_type_id IS NULL)";
        $sql_chart11 = "SELECT COUNT(DISTINCT xr.hn) AS cc_hn
                        FROM xray_head  xr
                        left outer join patient p on p.hn=xr.hn
                        WHERE xr.hn not in (SELECT hn FROM xrayxn WHERE regdate BETWEEN '$date_start' AND DATE(NOW()))
                        and  xr.order_date BETWEEN '$date_start' AND DATE(NOW()) and (xr.pt_xn='' OR xr.pt_xn is null )";
        $sql_chart12 = "select count(DISTINCT an) as an_cc from ipt where (dchdate=' ' or dchdate is null)";

        $chart1 = Yii::$app->db2->createCommand($sql_chart1)->queryAll();
        $chart2 = Yii::$app->db2->createCommand($sql_chart2)->queryAll();
        $chart3 = Yii::$app->db2->createCommand($sql_chart3)->queryAll();
        $chart4 = Yii::$app->db2->createCommand($sql_chart4)->queryAll();
        $chart5 = Yii::$app->db2->createCommand($sql_chart5)->queryAll();
        $chart6 = Yii::$app->db2->createCommand($sql_chart6)->queryAll();
        $chart7 = Yii::$app->db2->createCommand($sql_chart7)->queryAll();
        $chart8 = Yii::$app->db2->createCommand($sql_chart8)->queryAll();
        $chart9 = Yii::$app->db2->createCommand($sql_chart9)->queryAll();
        $chart10 = Yii::$app->db2->createCommand($sql_chart10)->queryAll();
        $chart11 = Yii::$app->db2->createCommand($sql_chart11)->queryAll();
        $chart12 = Yii::$app->db2->createCommand($sql_chart12)->queryAll();

        return $this->render('index', [
            'date_start' => $date_start,
            'chart1' => $chart1,
            'chart2' => $chart2,
            'chart3' => $chart3,
            'chart4' => $chart4,
            'chart5' => $chart5,
            'chart6' => $chart6,
            'chart7' => $chart7,
            'chart8' => $chart8,
            'chart9' => $chart9,
            'chart10' => $chart10,
            'chart11' => $chart11,
            'chart12' => $chart12]);
    }
    public function actionDetail1() {
        $date_start = "2015-10-01";
        $sql_detail1 = "SELECT v.hn,CONCAT(p.pname,p.fname,p.lname) AS full_name,o.vstdate,o.vsttime,o.cc,v.pdx
                        FROM vn_stat v
                        LEFT OUTER JOIN opdscreen o ON o.vn=v.vn
                        LEFT OUTER JOIN patient p ON p.hn=v.hn
                        WHERE v.vstdate  BETWEEN '$date_start' AND DATE(NOW())AND (v.pdx='' OR v.pdx IS NULL)
                        GROUP BY v.hn
                        ORDER BY v.vstdate ASC";
        $data1 = Yii::$app->db2->createCommand($sql_detail1)->queryAll();

        $dataProvider = new ArrayDataProvider([
            'allModels'=>$data1,
        ]);

        return $this->render('detail1', ['dataProvider' => $dataProvider]);
    }

    public function actionDetail2() {
        $date_start = "2015-10-01";
        $sql_detail2 = "SELECT a.hn,CONCAT(p.pname,p.fname,p.lname) AS full_name,a.an,a.regdate,w.name AS ward_name,a.pdx
                        FROM an_stat a
                        LEFT OUTER JOIN patient p ON p.hn=a.hn
                        LEFT OUTER JOIN ward w ON w.ward=a.ward
                        WHERE  a.dchdate BETWEEN '$date_start' AND DATE(NOW())AND (a.pdx='' OR a.pdx IS NULL)
                        GROUP BY a.an
                        ORDER BY a.regdate";
        $data2 = Yii::$app->db2->createCommand($sql_detail2)->queryAll();

        $dataProvider = new ArrayDataProvider([
            'allModels'=>$data2,
        ]);

        return $this->render('detail2', ['dataProvider' => $dataProvider]);
    }
    public function actionDetail3() {
        $date_start = "2015-10-01";
        $sql_detail3 = "SELECT p.hn,p.cid,CONCAT(p.pname,p.fname,' ',p.lname) AS full_name,p.informaddr,p.type_area,p.last_update
                        FROM patient p
                        WHERE  p.hn  IN (SELECT hn FROM vn_stat
                        WHERE vstdate  BETWEEN '$date_start' AND DATE(NOW()))
                        AND (p.type_area='' OR p.type_area<>'4' OR p.type_area IS NULL)";
        $data3 = Yii::$app->db2->createCommand($sql_detail3)->queryAll();

        $dataProvider = new ArrayDataProvider([
            'allModels'=>$data3,
        ]);

        return $this->render('detail3', ['dataProvider' => $dataProvider]);
    }
    public function actionDetail4() {
        $date_start = "2015-10-01";
        $sql_detail4 = "SELECT p.hn,CONCAT(p.pname,p.fname,' ',p.lname) AS full_name,e.vstdate,
        en.visit_type,en.accident_alcohol_type_id,en.accident_drug_type_id,en.er_emergency_type,
        en.accident_airway_type_id,en.accident_bleed_type_id,en.accident_splint_type_id,en.accident_fluid_type_id
        FROM er_nursing_detail en
        INNER JOIN ovst o ON o.vn=en.vn
        INNER JOIN ovst_seq os ON os.vn=en.vn
        INNER JOIN er_regist e ON e.vn=o.vn
        INNER JOIN er_pt_type erpt ON erpt.er_pt_type=e.er_pt_type AND erpt.accident_code='Y'
        INNER JOIN patient p ON p.hn=o.hn
        INNER JOIN pq_screen  pq ON pq.vn=en.vn
        INNER JOIN opduser ou ON ou.loginname=pq.staff
        WHERE e.vstdate BETWEEN '$date_start' AND DATE(NOW())
        AND (en.accident_place_type_id='' OR en.accident_place_type_id IS NULL
        OR en.visit_type='' OR en.visit_type IS NULL
        OR en.accident_alcohol_type_id='' OR en.accident_alcohol_type_id IS NULL
        OR en.accident_drug_type_id='' OR en.accident_drug_type_id IS NULL
        OR en.accident_airway_type_id='' OR en.accident_airway_type_id IS NULL
        OR en.accident_bleed_type_id='' OR en.accident_bleed_type_id IS NULL
        OR en.accident_splint_type_id='' OR en.accident_splint_type_id IS NULL
        OR en.accident_fluid_type_id='' OR en.accident_fluid_type_id IS NULL
        OR en.er_emergency_type='' OR en.er_emergency_type IS NULL )
        ORDER BY e.enter_er_time";
        $data4 = Yii::$app->db2->createCommand($sql_detail4)->queryAll();

        $dataProvider = new ArrayDataProvider([
            'allModels'=>$data4,
        ]);

        return $this->render('detail4', ['dataProvider' => $dataProvider]);
    }
    public function actionDetail5() {
        $date_start = "2015-10-01";
        $sql_detail5 = "SELECT p.hn,p.cid,CONCAT(p.pname,p.fname,' ',p.lname) AS full_name,o.vstdate,o.icd10,o.diagtype,d.name AS doctor_name
        FROM ovstdiag o
        INNER JOIN patient p ON p.hn=o.hn
        LEFT OUTER JOIN doctor d ON d.code=o.doctor
        WHERE  o.vstdate  BETWEEN '$date_start' AND DATE(NOW())
        AND (o.diagtype='' OR o.diagtype IS NULL OR o.diagtype NOT IN('1','2','3','4','5','6','7'))";
        $data5 = Yii::$app->db2->createCommand($sql_detail5)->queryAll();

        $dataProvider = new ArrayDataProvider([
            'allModels'=>$data5,
        ]);

        return $this->render('detail5', ['dataProvider' => $dataProvider]);
    }
    public function actionDetail6() {
        $sql_detail6 = "SELECT p.person_id,p.cid,CONCAT(p.pname,p.fname,p.lname) AS full_name,p.age_y,p.nationality,p.house_regist_type_id,v.village_name,p.last_update
        FROM person p
        LEFT OUTER JOIN village v ON v.village_id=p.village_id
        WHERE p.house_regist_type_id IN ('1','3')
        AND p.nationality<>'99' AND p.death='N'";
        $data6 = Yii::$app->db2->createCommand($sql_detail6)->queryAll();

        $dataProvider = new ArrayDataProvider([
            'allModels'=>$data6,
        ]);

        return $this->render('detail6', ['dataProvider' => $dataProvider]);
    }
    public function actionDetail7() {
        $sql_detail7 = "SELECT p.person_id,p.cid,CONCAT(p.pname,p.fname,p.lname) AS full_name,p.age_y,v.village_name,
        p.house_regist_type_id,CONCAT(d.person_discharge_id,' : ',d.person_discharge_name)AS discharge,p.last_update
        FROM person p
        LEFT OUTER JOIN village v ON v.village_id=p.village_id
        LEFT OUTER JOIN person_discharge d ON d.person_discharge_id=p.person_discharge_id
        WHERE p.house_regist_type_id IN ('1','3') AND p.person_discharge_id<>'9'AND p.death='N'";
        $data7 = Yii::$app->db2->createCommand($sql_detail7)->queryAll();

        $dataProvider = new ArrayDataProvider([
            'allModels'=>$data7,
        ]);

        return $this->render('detail7', ['dataProvider' => $dataProvider]);
    }
    public function actionDetail8() {
        $sql_detail8 = "SELECT p.person_id,p.cid,CONCAT(p.pname,p.fname,p.lname) AS full_name,p.age_y,v.village_name,
        p.house_regist_type_id,CONCAT(d.person_discharge_id,' : ',d.person_discharge_name)AS discharge,p.last_update
        FROM person p
        LEFT OUTER JOIN village v ON v.village_id=p.village_id
        LEFT OUTER JOIN person_discharge d ON d.person_discharge_id=p.person_discharge_id
        WHERE p.village_id='1' AND p.house_regist_type_id IN ('1','3')";
        $data8 = Yii::$app->db2->createCommand($sql_detail8)->queryAll();

        $dataProvider = new ArrayDataProvider([
            'allModels'=>$data8,
        ]);

        return $this->render('detail8', ['dataProvider' => $dataProvider]);
    }
    public function actionDetail9() {
        $sql_detail9 = "SELECT h.house_id,v.village_name,h.address,h.location_area_id,CONCAT(t.house_type_id,' : ',t.house_type_name) AS house_type,CONCAT(s.house_subtype_id,' : ',s.house_subtype_name) AS house_subtype,h.last_update
        FROM house h
        LEFT OUTER JOIN village v ON v.village_id=h.village_id
        LEFT OUTER JOIN house_type t ON t.house_type_id=h.house_type_id
        LEFT OUTER JOIN house_subtype s ON s.house_subtype_id=h.house_subtype_id
        WHERE (h.location_area_id IS NULL  OR h.location_area_id= ''
        OR h.house_type_id IS NULL OR h.house_type_id= '' OR h.house_subtype_id  IS NULL OR h.house_subtype_id ='')";
        $data9 = Yii::$app->db2->createCommand($sql_detail9)->queryAll();

        $dataProvider = new ArrayDataProvider([
            'allModels'=>$data9,
        ]);

        return $this->render('detail9', ['dataProvider' => $dataProvider]);
    }
    public function actionDetail10() {
        $sql_detail10 = "SELECT p.person_id,p.cid,CONCAT(p.pname,p.fname,p.lname) AS full_name,p.age_y,v.village_name,
        p.house_regist_type_id,CONCAT(d.person_discharge_id,' : ',d.person_discharge_name)AS discharge,p.last_update
        FROM person p
        LEFT OUTER JOIN village v ON v.village_id=p.village_id
        LEFT OUTER JOIN person_discharge d ON d.person_discharge_id=p.person_discharge_id
        WHERE (p.house_regist_type_id='' OR p.house_regist_type_id IS NULL)";
        $data10 = Yii::$app->db2->createCommand($sql_detail10)->queryAll();

        $dataProvider = new ArrayDataProvider([
            'allModels'=>$data10,
        ]);

        return $this->render('detail10', ['dataProvider' => $dataProvider]);
    }
        public function actionDetail11() {
        $date_start = "2015-10-01";
        $sql_detail11 = "SELECT xr.pt_xn,xr.hn,p.cid,CONCAT(p.pname,p.fname,p.lname) AS full_name   ,xr.order_date_time,xr.department,xr.xray_list ,xr.confirm_all
        FROM xray_head  xr
        left outer join patient p on p.hn=xr.hn
        WHERE xr.hn not in (SELECT hn FROM xrayxn WHERE regdate BETWEEN '$date_start' AND DATE(NOW()) )
        and  xr.order_date BETWEEN '$date_start' AND DATE(NOW())
        and (xr.pt_xn='' OR xr.pt_xn is null )
        group by   xr.hn
        order by xr.order_date DESC";
        $data11 = Yii::$app->db2->createCommand($sql_detail11)->queryAll();

        $dataProvider = new ArrayDataProvider([
            'allModels'=>$data11,
        ]);

        return $this->render('detail11', ['dataProvider' => $dataProvider]);
    }
        public function actionDetail12() {

        $sql_detail12 = "select i.hn,p.cid,concat(p.pname,p.fname,' ',p.lname) as full_name,i.an,concat(i.regdate,' ',i.regtime) regdatetime,if(i.dchtype='0','ยังไม่จำหน่าย','ไม่ทราบ') as dchtype
        from ipt  i
        left outer join patient p on p.hn=i.hn
        where (i.dchdate=' ' or i.dchdate is null) ";
        $data12 = Yii::$app->db2->createCommand($sql_detail12)->queryAll();

        $dataProvider = new ArrayDataProvider([
            'allModels'=>$data12,
        ]);

        return $this->render('detail12', ['dataProvider' => $dataProvider]);
    }
}


We are always looking for talented individuals to join our team. Check back often to see our current career opportunities.
Opening Spring 2019, we will be serving coastal cuisine inspired by our local surroundings and global adventures. Our open kitchen features an EarthStone wood and gas fire oven along with seasonal menus that will showcase the best of our regional bounty.Located on the water in Victoria International Marina, with stunning views of the waterfront from our dining room, bar, and café.Featuring a team of dedicated and talented industry veterans, we hope to elevate Victoria's dining scene.
Elegant yet approachable, our vision is inspired by the place we choose to call home, Victoria. Globally Inspired, locally sourced. Our All-day café will be open from early till late everyday and feature coffee, pastries and savoury food. A special highlight is the hot food items baked fresh to order from our forno oven.Our Full-Service Restaurant serving lunch and dinner will feature Pizza, Pasta, Raw Bar, Salads, Grains, Vegetables, Meat, Fish and Desserts.
Our culinary team is striving to create the best restaurant in Victoria and we are seeking experienced applicants and young cooks looking to start their culinary careers. Please apply with a resume and cover letter in response to this ad. Compensation will be competitive and commensurate with experience. $16 to $19 hourly plus tips. Thanks for your interest.
Only applicants selected for interviews will be contacted at this time.
Opening Spring 2019, we will be serving coastal cuisine inspired by our local surroundings and global adventures. Our open kitchen features an EarthStone wood and gas fire oven along with seasonal menus that will showcase the best of our regional bounty. Located on the water in Victoria International Marina, with stunning views of the waterfront from our dining room, bar, patio and café. Featuring a team of dedicated and talented industry veterans, we hope to elevate Victoria's dining scene.
Elegant yet approachable, our vision is inspired by the place we choose to call home, Victoria. Globally Inspired, locally sourced. Our All-day café will be open from early till late everyday and feature coffee, pastries and savoury food. A special highlight is the hot food items baked fresh to order from our forno oven. Full Service Restaurant serving lunch and dinner will feature Pizza, Pasta, Raw Bar, Salads, Grains, Vegetables, Meat, Fish and Desserts.
Our culinary team is striving to create the best restaurant in Victoria and we are seeking experienced applicants and young cooks looking to start their culinary careers. Please apply with a resume and cover letter in response to this ad. Compensation will be competitive and commensurate with experience. $15 to $22 hourly plus tips. Thanks for your interest.
Boom + Batten, Victoria's newest restaurant located at the Victoria International Marina, opening April 2019 is now actively searching for a Bar Manager to take our new restaurant to the top of Canada's restaurant scene.
Your passion for exceptional service, innovative cocktails, beer and wine will lead our team to the execution of superior experiences for all guests. Your daily efforts must reflect the vision of our company. You will continuously train, develop and lead an incredible bar team who will be motivated by your inspirational leadership and who understand the crucial role they all play in the overall success of the business.
-Supervision of all bar service staff in accordance with operating policies during their shift.
-Responsible for ensuring that proper liquor service and presentation are being met by all bar staff.
-Working closely with the service manager and wine director to ensure proper ordering, storage and inventory of wine program.
-Assisting guests and service staff with wine and beverage pairings.
-Organizing, building and maintaining a professional work environment.
-Overseeing all initial and ongoing training of the bartenders.
-Inventory and cost control management with Optimum Control.
-Overseeing the proper execution of the entire beverage program.
-Excellent interpersonal, verbal and written communication skills.
-Must possess good attitude, attention to detail, and ability to work under pressure.
-Passion for cocktails, beer and wine.
-Strong background in hospitality with previous Bar Management experience.
-Must have proper skills with Microsoft Office; Word, Excel, PowerPoint.
-Excellent knowledge of wine and wine service.
-Working knowledge of food preparation methods and culinary terminology.
-Experience with budgeting and cost controls.
-Preferred Squirrel POS, OpenTable and Optimum Control experience.
-Schedule may fluctuate based on requirements.
Rates + bonuses will be negotiated based on the successful applicants qualifications and experiences.
Boom + Batten, Victoria's newest restaurant located at the Victoria International Marina, opening in April 2019 is now actively searching for a Service Manager / Assistant Service Manager to take our new restaurant to the top of Canada's restaurant scene.
Your passion for exceptional service and wine will lead our team to the execution of superior experiences for all guests. Your daily efforts must reflect the vision of our company. You will continuously train, develop and lead an incredible team who will be motivated by your inspirational leadership and who understand the crucial role they all play in the overall success of the business.
-Driving product and service culture, continually checking with guests and service staff.
-Supervision of all front of house service staff in accordance with operating policies during their shift.
-Responsible for ensuring that proper food handling and presentation are being met by all staff.
-Organizing and conducting pre-shift meetings and communicating pertinent information to all staff.
-Handling guest concerns and complaints in a prompt and professional manner.
-Working closely with the bar manager to ensure proper ordering, storage and inventory of wine program.
-Responsible for scheduling front of house staff in 7shifts on a weekly basis.
-Recruiting and overseeing all training of front of house partners.
-Sommelier certification preferred, or previous similar Sommelier experience.
Salary + bonuses will be negotiated based on the successful applicants qualifications and experiences.


text:
CNBC Investigation: Inside the world of a private jet company
4:00 PM ET Wed, 9 Jan 2019
Behind its elite image, a CNBC investigation found that JetSmarter has left behind a trail of broken promises and outraged customers who call the company a fraud, as well as falling short on its promises to investors. JetSmarter denies the allegations and says it's more positive about the health of the business than ever. And despite the company saying it has the most rigorous safety standards in private aviation, members told us about security concerns on JetSmarter flights. Our story debuts on Thursday, Jan. 10 on CNBC.


Double T applique Red and black metallic ribbon French barrette clip style Made in U.S.A.
Double T patch on top of wide red ribbon French barrette style clip Made in U.S.A.
Double T on red stripe Some stretch for one size fits most Made in U.S.A. Width measures approximately 2.5"
Double T on team colored plaid Some stretch for one size fits most Made in U.S.A. Width measures approximately 2.5"
Double T patch on top of red polka dot ribbon French barrette style cip Made in U.S.A.
Double T patch on top of wide silver sequin ribbon Frech barrette style clip Made in U.S.A.
Look great the next game day with this fun red and black lip colors!
Pack includes 4 Double Ts Easy to apply Waterproof once applied Perfect to wear for the games!


Welcome to the 2017 Colorado Summit VBC Open Gym Registration!
Please join us for our Open Gym. The purpose of the Open Gym is to give athletes, in a relaxed setting, the opportunity to meet and work with our coaching staff on a variety of skills (passing, setting, hitting, etc.). In addition, the parents will have a chance to meet the Club's leadership to discuss our philosophy and to answer any questions related to the upcoming 2018 Season. It is best to arrive approximately 15 minutes prior to the session to assure that your athlete is checked-in prior to the start of the season.