Alarming signs in discussions about the financing of higher education

No ratings yet. Log in to rate.
European Union More data is needed on students and financing.

BRUSSELS - The financing of higher education has become an increasingly important discussion topic in European policy-making processes. This subject has been addressed in several reports and will set the agenda of major events in the upcoming months. However, the European Students’ Union (ESU) has growing concerns about the frame of those discussions.

Meetings of the Bologna Follow-up Group, Directors General of the European Commission, Council of the European Union and the funding forum of the European University Association, are on among the European events that address the funding of higher education institutions. In addition, following ESU’s project called Financing the Students’ Future (FinSt) the European Commission also released the report “Do changes in cost-sharing have an impact on the behaviour of students and higher education institutions?”.

Financing was for a long time considered to be the ‘third rail’ of policy-making in higher education in Europe. It is clear that this trend has now been broken. To put it mildly, we are concerned about some of the ways this issue is being addressed.” says Elisabeth Gehrke, ESU’s chairperson.

Insufficient data used in conclusions

The report from the European Commission attempted to analysed the impact of tuition fees on students. Although ESU recognises the need for more peer-learning and data collection on the financing of higher education, it is deeply concerned with the European Commission’s interpretation of the study. This understanding was noted in related press releases and presented to member states of the European Union and the Bologna Process.

Similar to the authors of the report, ESU considers the data made available in the report to be insufficient insufficient to draw such drastic conclusions as were put forward. The same issue was addressed in ESU’s FinSt project as well as in several of the Bologna implementation reports. Lacking data is for instance evidenced in the report addressing only enrollment numbers as there is no data about the students’ study progression and even less in case of vulnerable groups, that are not defined. Data about vulnerable groups is either not made available by countries or not collected at all. This is an issue that ESU has voiced several time in the past.

Tuition fees or cost-sharing

Moreover, the term "cost sharing" avoids the proper wording of "tuition fees" because “cost sharing” is a broader term referring to the combination of public and private funding. However, the only factor analysed in the report is tuition fees. The claim is that tuition fees have neither negative effects on students in general, nor students from disadvantaged groups as long as student aid in the form of grants or loans is provided. While ESU supports the report in its call for better data about the social status and composition of the student population, it finds the report to be inconclusive and the conclusions of the European Commission misleading.

We would like to encourage the European Commissioner designate Mr. Tibor Navracsics to reconsider this approach to ‘cost-sharing’ and call on the member states to deliver more and better data regarding access and completion of higher education,” says Elisabeth Gehrke, ESU chairperson. She continues, “We are concerned with the ways in which these issues are being framed and the skewed conclusions that are being put forward. We also want to express our dismay that tuition fees are being discussed in certain forums where the student and stakeholder voice is being shut out. This is not responsible policy-making and breeds distrust in a time in Europe where that is the last thing we need.”

-- END ---

For more information, please contact:

Elisabeth Gehrke, ESU Chairperson: +32/479.591.499 // or Robert Hlynur Baldursson, ESU Communications Manager: +32/473.669.894 //

The European Students’ Union, headquartered in Brussels, is the umbrella organisation of 47 national unions of students from 39 European countries. ESU represents and promotes the educational, social, economical and cultural interests of students at the European level. Through its member unions, ESU represents over 11 million students in Europe. To find out more about ESU, follow us on Twitter @ESUtwt, check out or Facebook page or visit ESU celebrates its 30th anniversary in 2012.



Wq123 Wq123
03:03 on 26 Oct 15 In short, the microservice architectural style is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an resource API. These services are built around business capabilities and independently deployable by fully automated deployment machinery. There is a bare minimum of centralized management of these services, which may be written in different programming languages and use different data storage technologies. To start explaining the microservice style it's useful to compare it to the monolithic style: a monolithic application built as a single unit. Enterprise Applications are often built in three main parts: a client-side user interface (consisting of HTML pages and javascript running in a browser on the user's machine) a database (consisting of many tables inserted into a common, and usually relational, database management system), and a server-side application. The server-side application will handle HTTP requests, execute domain logic, retrieve and update data from the database, and select and populate HTML views to be sent to the browser. This server-side application is a monolith - a single logical executable[2]. Any changes to the system involve building and deploying a new version of the server-side application. Such a monolithic server is a natural way to approach building such a system. All your logic for handling a request runs in a single process, allowing you to use the basic features of your language to divide up the application into classes, functions, and namespaces. With some care, you can run and test the application on a developer's laptop, and use a deployment pipeline to ensure that changes are properly tested and deployed into production. You can horizontally scale the monolith by running many instances behind a load-balancer. Monolithic applications can be successful, but increasingly people are feeling frustrations with them - especially as more applications are being deployed to the cloud . Change cycles are tied together - a change made to a small part of the application, requires the entire monolith to be rebuilt and deployed. Over time it's often hard to keep a good modular structure, making it harder to keep changes that ought to only affect one module within that module. Scaling requires scaling of the entire application rather than parts of it that require greater resource.
Varun Donala
18:59 on 17 Dec 14 very nice article good one <a href="">merry christmas images</a> <a href="">merry christmas pictures</a>
Bui Tan Thuan
08:24 on 22 Oct 14 <a href="">ve may bay di dai loan</a> | <a href="">du hoc tai nhat ban</a> | <a href="">du hoc tai han quoc</a> | <a href="">du hoc tai singapore</a> | <a href="">du hoc tai australia uc</a> | <a href="">du hoc tai my</a> | <a href="">lop tieng anh giao tiep tai hcm</a> | <a href="">khoa hoc tieng anh giao tiep cap toc</a>
Keu Keu
08:43 on 10 Oct 14 very interesting information thank you for sharing information may be useful <a href="" rel="dofollow">Minyak Ikan</a>
Savior Logan
08:49 on 9 Oct 14 i like to learn.. this blog give me many information <a href="">agen bola</a>
Please log in to comment.