text:
Princeton University has selected American Campus Communities (ACC) to assist with preparations associated with the redevelopment of the Hibben-Magie site for graduate student housing.
The Austin, Texas-based company is one of the largest developers of student housing communities in the country. The company will work with the University on predevelopment tasks such as conducting focus groups with graduate students and other stakeholders, obtaining regulatory approvals, evaluating design and financing alternatives, estimating costs, and scheduling services. A project design with all regulatory approvals is expected to emerge from this collaboration.
"After a great deal of research, including visits to a number of locations where ACC and others have developed similar complexes, we learned that there are several firms that produce very high-quality products and services," said Michael McKay, vice president for facilities, who directed a team of Princeton administrators through the search for a firm for the project. "ACC is clearly a leader in this field, and they impressed the selection team with both projects and operations that respond to the particular housing needs of graduate students. We're very much looking forward to partnering with them to meet the institution's goals for this site."
The University, with ACC, also has chosen an architect for the project, and negotiations are under way with that firm. The selection process included a request for qualifications from and interviews with a short list of architects. A member of the Graduate Student Government was an interviewer and was critical to the overall decision-making.
The redevelopment project is intended to provide newly constructed housing units for 475 to 625 graduate students. The predevelopment phase is expected to take two years, with construction anticipated to begin in 2012. The construction period will last approximately two years, and plans call for graduate students to occupy the apartments in the summer of 2014. The project is part of the University's Housing Master Plan, begun in 2005 to enhance housing programs for faculty, staff and graduate students, as well as the Campus Plan, begun in 2006 to guide campus development through 2016.
The Hibben and Magie apartments are two adjacent mid-rise buildings located south of Faculty Road and east of Alexander Street occupied during the 2009-10 academic year by 280 graduate students and 54 faculty and staff. Constructed in the 1960s, the 192 units have outmoded building systems and interior layouts, and do not offer residents amenities found in more contemporary housing facilities. Part of ACC's work will be determining the size and mix of units (studio, one-bedroom, two-bedroom or three-bedroom) and whether or not to retain all or part of the existing Hibben-Magie buildings as part of the design.
Members of the selection committee were particularly impressed with ACC's collaborative approach, as well as the standard of development and operations of student housing developments that ACC developed, owns or manages at the University of California-Irvine and Arizona State University, according to Chad Klaus, assistant vice president for facilities.
"It's an honor for American Campus to be selected by one of the world's most prestigious institutions of higher learning to address its graduate student housing needs," said Bill Bayless, American Campus CEO. "We look forward to collaborating with all University stakeholders, and are committed to providing a customized housing solution that meets the objectives and high standards of Princeton. We expect the Hibben-Magie project to set a new standard in graduate student housing."
Upon completion of the project, the University will make Hibben-Magie available only to graduate students. At that point, the Housing Master Plan calls for the Butler Tract (bounded by Harrison Street, Hartley Avenue and Sycamore Road), which housed 370 graduate students last year, to be redeveloped for faculty and staff housing. The redeveloped Hibben-Magie site is expected to meet the majority of the demand of graduate students residing there and at the Butler Tract.
Princeton's goal is to continue to house approximately 70 percent of its graduate students in University-owned and -operated housing. Graduate students, which number slightly more than 2,225, also live in the Graduate College and Lawrence Apartments, as well as in off-campus housing.


text:
Glimpses into yesterday's ITLSS inbox:
Six hours later:Hey Professor,Here is the article about the [Fordham] Con Law Professor giving his students a multiple choice exam that had been sitting online for everyone to see all semester (w/ answers) that I had written to you about earlier. Not as hard hitting an article as I would've written, but it covers the basics.The school's 'solution' (substituting grades from other classes, many of which are easy A 2 credit courses) essentially gifts 80 out of 400 members of the class a better than median grade on the only curved and 4 semester credit class of the semester. You can imagine the consternation this is causing amidst the viciously competitive job market.I see that there was no good solution here, (although giving students the option of a P would have made more sense than allowing them to replace their grade with the grades of non-curved classes) the section in question already suffered 6 weeks of aggravation and stress. What bothers me is the stunning lack of accountability for the Professor who couldn't be bothered to accomplish his one concrete job for the semester. No reprimand, no apology, no consequences. He's an old man who clearly is no longer fit to teach and collect his large chunk of federal loan payments.
Hey Professor, so they have already bowed to public pressure and instituted what looks like a pass/fail, and did so by invoking one of your favorites - the 'balancing test'. They "very much regret the situation" but have announced zero disciplinary measures or repercussions for the highly paid Professor who caused all of this.Four hours after that:
I regularly read ILSS and wanted to get your thoughts on a situation that has occurred at my law school (University of Arizona). I am a 1L and was enrolled last semester in civil procedure. During the course of the semester it was clear to everybody in the class that our professor was not up to snuff. I'm not just talking about quickly brushing off topics or being hard to reach outside of class; I'm referring to basic deviations from professional norms that we are all held to. In the first week of class alone, the professor was late twice, each time students went to her office to find her asleep at her desk . . .
[Long tale of incompetence and subsequent shenanigans related to grading redacted for privacy reasons. Short version: Prof put on administrative leave and the administration is trying to figure out what to do with the class's grades]
The administration is working to come up with a solution that will only help the students (which I predict will look like everybody above median will keep their grade and everybody below median will switch their grade to a pass). My question for you is: do you think the class should press the school to refund our money for the course (at least partially)? The school treated the class like just another expense and took a risk by putting this "professor" in the classroom. The risk did not pan out as they would have liked, but the students are the ones that are skirting the costs and not the school. Any insight that you can provide would be greatly appreciated.
These sorts of incidents are perfectly predictable consequences of an increasingly out of control system, which features less and less accountability for those who exploit and are exploited by it. Law schools charge prices completely unrelated to the value of law degrees because they can. Students borrow sums of money completely unrelated to their subsequent ability to pay that money back because they can. Professors get away with metaphorical murder because they can.
From the look of it I doubt this Fordham guy puts ten hours a week into his "job," and his behavior is hardly unusual, as anyone who works at a law school is perfectly well aware. Yes lots of law professors work hard. Lots don't. After a few initial observations on this theme I haven't pursued it, because it's marginal to the central problem, and references to it become a distraction, since apparently nothing upsets the average law faculty member more than the suggestion that law faculty on average don't work very hard. But in any case it's a side issue: Even if every law prof in America published 100,000 words a year and spent 30 hours per week preparing for classes that wouldn't by itself lower any graduate's debt load or get anyone a job.
Still it's true that the non-work habits of professors are one outcome of the egregious featherbedding that is a prime consequence of having tripled real tuition since the 1980s: it's not an exaggeration to point out that it would possible to get rid of half the faculty at most law schools with no significant loss of educational quality. (Doing so would merely return faculty student ratios to what they were in 1980). And that of course has consequences for long-term reform: a few months ago somebody posted on I forget which law prof blog about a "no-frills" model law school that would charge only $20,000 per year year in tuition, obviously without realizing that no law school anywhere charged even that much (in constant, inflation-adjusted dollars) as recently as the early 1980s.
Housekeeping detail: JD Painterguy has assured me once again that he will no longer post on this blog. COMMENTS REFERRING TO HIM IN ANY WAY WILL BE DELETED, INCLUDING IN THIS THREAD. Please abide by this policy.

subset: commoncrawl


text:
This article talks about ASP.NET the custom Forms Authentication mechanism. We will see how we can use a custom database in unison with the ASP.NET Forms Authentication mechanism to provide the desired level of security to our applications.
We have already seen how we can use ASP.NET Roles and Membership classes to provide authentication and authorization in our applications (refer this). Also, we know about the server controls provided by ASP.NET to facilitate easy implementation of Roles and Membership functionalities in our application.
These Roles and Membership classes come in very handy when we want to provide authentication and authorization in our applications. ASP.NET also provides a way to implement custom Roles and Membership to take more granular control over things.
We might still find ourselves in situations where we need to have our own database for tracking users and their roles. The reasons could be:
In all the above scenarios, we find the need to use ASP.NET Forms Authentication but according to our database schema and our custom written code to handle user management. This is where the beauty of ASP.NET is shown. ASP.NET provides us fully functional and robust functionality for authentication and authorization and yet it gives us the possibility of taking full control and having full customization of the functionalities (which is actually not limited to Authentication related stuff, pretty much all areas of ASP.NET does that).
So what we are trying to do can easily be achieved by having a custom Forms Authentication mechanism. Using a custom Forms Authentication mechanism we can have our own tables to manage users and yet use the existing form authentication mechanism using GenericPrincipal. Let us try to work out an example and see how this can be done.
Let us start by getting our requirements clear. We will be implementing a website that has the following structure:
The top level default page and the login page can be accessed by anyone. The pages in other folders can only be accessed by users in respective roles. Just to understand it in a clear way, let us look at the web.config of the PlatinumUser folder.
<configuration> <appSettings/> <connectionStrings/> <system.web> <authorization> <allow roles="platinum" /> <deny users="*" /> </authorization> </system.web> </configuration>
And the database that we have for user management looks like this.
We have a user table and every user can have multiple Roles. We will be using this table to authenticate the users.
Note: The database is neither optimized nor normalized as that was not the main intent of this article. A real world example of database will be more optimized and perhaps more complex. The passwords will not be in clear text for sure too.
Now before going ahead, let us look at the little algorithm that we will be following to implement custom forms authentication and achieve the desired functionality.
Note: Each point in this algorithm can be found emphasized in the explanation below.
We have the algorithm worked out. We will now look at how each step is done. Let us start with Configure the application to use Forms authentication. To do this we need to set the authentication mode in the web.config file.
<authentication mode="Forms"> <forms loginUrl="Login.aspx" name="MyCustomAuthentication" timeout="30"/> </authentication>
This web.config indicates that Forms Authentication will be used in this application. The default loginUrl is Login.aspx. The name of the authentication ticket cookie will be MyCustomAuthentication and if this cookie is created in non persistent mode, then the timeout period for that is 30 minutes.
Now we have our website set to use Forms authentication and we have also specified the default login page so we also took care of #3 of our algorithm, i.e., Whenever user tries to access the restricted area, push him to the Login page. The next thing is to Create a login page.
Once this login page is done, we need to have some mechanism so that When the user tries to login, verify his credentials using the database. To do this, I have created a small helper class. Ideally this logic will be placed in a Data Access layer or might be present in ORMs. But for the sake of simplicity I have created a small helper class do to this.
public class DBHelper { //Validate the user from DB public static bool CheckUser(string username, string password) { DataTable result = null; try { using (SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["userDbConnectionString"].ConnectionString)) { using (SqlCommand cmd = con.CreateCommand()) { cmd.CommandType = CommandType.Text; cmd.CommandText = "select password from Users where username = @uname"; cmd.Parameters.Add(new SqlParameter("@uname", username)); using (SqlDataAdapter da = new SqlDataAdapter(cmd)) { result = new DataTable(); da.Fill(result); } if (password.Trim() == result.Rows[0]["password"].ToString().Trim()) { //user id found and password is matched too so lets do soemthing now return true; } } } } catch (Exception ex) { //Pokemon exception handling } //user id not found, lets treat him as a guest return false; } //Get the Roles for this particular user public static string GetUserRoles(string username) { DataTable result = null; try { using (SqlConnection con = new SqlConnection(ConfigurationManager.ConnectionStrings["userDbConnectionString"].ConnectionString)) { using (SqlCommand cmd = con.CreateCommand()) { cmd.CommandType = CommandType.Text; cmd.CommandText = "select roles from Users where username = @uname"; cmd.Parameters.Add(new SqlParameter("@uname", username)); using (SqlDataAdapter da = new SqlDataAdapter(cmd)) { result = new DataTable(); da.Fill(result); } if(result.Rows.Count == 1) { return result.Rows[0]["roles"].ToString().Trim(); } } } } catch (Exception ex) { //Pokemon exception handling } //user id not found, lets treat him as a guest return "guest"; } }
Now whenever the user tries to log in, If the login is successful, keep the username and his Roles in Session variable to use it further, and also we need to Create an authentication ticket for the user (an encypted cookie). So let us do all this in the Button click event of the login page.
protected void Button1_Click(object sender, EventArgs e) { string roles; string username = TextBox1.Text.Trim(); if (DBHelper.CheckUser(username, TextBox2.Text.Trim()) == true) { //These session values are just for demo purpose to show the user details on master page Session["User"] = username; roles = DBHelper.GetUserRoles(username); Session["Roles"] = roles; //Let us now set the authentication cookie so that we can use that later. FormsAuthentication.SetAuthCookie(username, false); //Login successful lets put him to requested page string returnUrl = Request.QueryString["ReturnUrl"] as string; if (returnUrl != null) { Response.Redirect(returnUrl); } else { //no return URL specified so lets kick him to home page Response.Redirect("Default.aspx"); } } else { Label1.Text = "Login Failed"; } }
Now before going further, there is one thing to understand. When Forms authentication is being used, whenever the need for authentication arises, the ASP.NET framework checks with the current IPrinciple type object. The user ID and Role contained in this IPrinciple type object will determine whether the user is allowed access or not.
So far we have not written code to push our user specific details in this principle. To do that we need to override a method called FormsAuthentication_OnAuthenticate in global.asax. This method is called each time ASP.NET framework tries to check authentication and authorization with respect to the current Principle.
What we need to do now is to override this method. Check for the authentication ticket (since the user has already been validated and the ticket was created) and then supply this User/Role information in the IPrinciple type object. We can implement our custom Principle type too but to keep it simple, we will simply create a GenericPriciple object and set our user specific details into it [#7 and #8 of our algorithm are covered].
protected void FormsAuthentication_OnAuthenticate(Object sender, FormsAuthenticationEventArgs e) { if (FormsAuthentication.CookiesSupported == true) { if (Request.Cookies[FormsAuthentication.FormsCookieName] != null) { try { //let us take out the username now string username = FormsAuthentication.Decrypt(Request.Cookies[FormsAuthentication.FormsCookieName].Value).Name; //let us extract the roles from our own custom cookie string roles = DBHelper.GetUserRoles(username); //Let us set the Pricipal with our user specific details e.User = new System.Security.Principal.GenericPrincipal( new System.Security.Principal.GenericIdentity(username, "Forms"), roles.Split(';')); } catch (Exception) { //somehting went wrong } } } }
Now when we run the application, we will see that the authorization mechanism is working as specified in the respective web.config files in perfect unison with our own custom database and authentication logic.
Note: Running the sample application, looking at code, and debugging the application is strongly recommended to get a full understanding of the above mentioned concepts.
When I came across the requirements of having custom forms authentication, I was rather intimidated. It was partly because I only knew how the ASP.NET default membership provider worked and partly because the hype about how difficult it is to do custom forms authentication. When I sat on it, I found it rather straightforward and easy.
There is one more major area that is also worth looking into to understand the authentication and authorization mechanism completely and that is implementing a custom Membership Provider. Perhaps I will do that in a separate article.
This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)
I Started my Programming career with C++. Later got a chance to develop Windows Form applications using C#. Currently using C#, ASP.NET & ASP.NET MVC to create Information Systems, e-commerce/e-governance Portals and Data driven websites.
My interests involves Programming, Website development and Learning/Teaching subjects related to Computer Science/Information Systems. IMO, C# is the best programming language and I love working with C# and other Microsoft Technologies.
If you like my articles, please visit my website for more: www.rahulrajatsingh.com[^]
<authentication mode="Forms"> <forms loginUrl="~/Inicio/Login.aspx" name=".CesAUTH" timeout="2" protection="All" slidingExpiration="true" defaultUrl="~/Inicio/Login.aspx" requireSSL="true"/> </authentication> <authorization> <deny users="?"/> <allow users="*"/> </authorization> </system.web> <location path="Inicio"> <system.web> <authorization> <allow users="*"/> </authorization> </system.web> </location>
//Se genera la cookie para la autenticación del usuario HttpCookie authCookie = FormsAuthentication.GetAuthCookie(UsrRUT.ToString(), false); FormsAuthenticationTicket ticket = FormsAuthentication.Decrypt(authCookie.Value); FormsAuthenticationTicket newTicket = new FormsAuthenticationTicket(ticket.Version, ticket.Name, ticket.IssueDate, ticket.Expiration, ticket.IsPersistent, UsrRUT.ToString() + "_" + DateTime.Now.ToString("yyyyMMddHHmmssfff")); authCookie.Value = FormsAuthentication.Encrypt(newTicket); HttpContext.Current.Response.Cookies.Add(authCookie); //Se redirecciona la solictud del login en caso de haber sido generada desde otra página FormsAuthentication.RedirectFromLoginPage(UsrRUT.ToString(), true);
void Application_OnPostAuthenticateRequest(object sender, EventArgs e) { // Referencia al usuraio actual IPrincipal usr = HttpContext.Current.User; if (usr.Identity.IsAuthenticated && usr.Identity.AuthenticationType == "Forms") { FormsIdentity fIdent = usr.Identity as FormsIdentity; // Genera el objeto CustomIdentity personalizado en base a el FormsAuthenticationTicket CustomIdentity ci = new CustomIdentity(fIdent.Ticket); // Genra el objeto CustomPrincipal CustomPrincipal p = new CustomPrincipal(ci); // Agregas los objetos al contexto e hilo de ejecución actuales HttpContext.Current.User = p; Thread.CurrentPrincipal = p; } }
FormsAuthenticationTicket ticket = new FormsAuthenticationTicket( 1, // Ticket version "your-username", // Username associated with ticket DateTime.Now, // Date/time issued DateTime.Now.AddMinutes(30), // Date/time to expire true, // for a persistent user cookie "Your-user-role", // User-data, in this case the roles FormsAuthentication.FormsCookiePath); // Cookie Encryption String hash = FormsAuthentication.Encrypt(ticket); The encrypted string is now in the hash VARIABLE ;-)
<authorization> <allow roles="platinum" /> <deny users="*" /> </authorization>
General News Suggestion Question Bug Answer Joke Praise Rant Admin
Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.


text:
ingrid | The Postscript-based software on which the Data Library is built. |
CPT | Climate Predictability Tool More information |
ferret | Interactive computer visualization and analysis software. More information |
GrADS | Grid Analysis and Display System More information |
matlab | Data analysis and visualization software. More information |
NCL | NCAR Command Language More information |
WinDisp | A public domain software package for the display and analysis of satellite images, maps and associated databases, with an emphasis on early warning for food security. More information |
Full Information Formats
These files contain all of the available metadata. | |
OPeNDAP | A system which downloads data directly to software, such as matlab, Ferret, GrADS, etc. Specific instructions are available in the table above. Note: OPeNDAP was formerly known as DODS (Distributed Oceanographic Data System). More Information |
netCDF (network Common Data Form) | A commonly supported self-describing data format. More Information |
Partial Information Formats
These files contain only some of the available metadata. | |
Columnar Table | A table with separate columns of numbers for each independent variable (i.e., grids) and for the data. This columnar table is available in a variety of file and column formats here. Note: By setting the helper for mime-type text/tab-separated-values, you can have this loaded directly into your favorite spreadsheet. This file will be approximately 14880 bytes, with 2 columns of 1860 numbers. |
Data Only Formats
These files contain just the data without any of the available metadata. | |
Binary direct access | A big-endian, ieee single-precision file in floating-point format. Also known as a binary random access file. This is a random-access file; it is purely data with no record-structuring information. The data is structured to correspond to the independent variables (i.e., grids) in T order, with the first grid varying the fastest. |
DEC ALPHA direct access | Same as the binary random/direct access format above except that it is byte-swapped for DEC ALPHA's and PC's (little-endian). |
Binary FORTRAN sequential access | A big-endian, ieee, single-precision file in floating-point format. This is a sequential-access file with each record containing one point. It must be read using FORTRAN sequential access. Records correspond to T. |
DEC ALPHA sequential access | Same as the binary sequential access format above except that it is byte-swapped for DEC ALPHA's and PC's (little-endian). |
Text with tab-separated-values | Text file where data values corresponding to different T
are separated by tabs and data values corresponding to different
are on different lines. This is readable by most programs, including spreadsheets, but will be about four times larger than the binary or netCDF/HDF files noted above.
As an alternative, you can access a tab-separated file with the following independent variables (i.e., grids) grouped on each line: T | |
Text | Text file where data is arranged in chunks of . There are five values per line and each chunk starts on a new line. This will be about four times larger than the binary or netCDF/HDF files. |


text: Data were also collected aboard the R/V AHI (Acoustic Habitat Investigator), a 25' survey launch owned and operated by the NOAA Pacific Islands Fisheries Science Center in Honolulu, HI. The R/V AHI's survey sensors include a 240 kHz RESON 8101-ER sonar providing bathymetry and imagery data, a TSS/Applanix POS/MV Model 320 which measures position, velocity, attitude and heading, and a Seabird SBE 19 CTD used to measure sound velocity profiles. Sensor configuration for the AHI for cruise AHI-06-04 is documented in the cruise/multibeam metadata file AHI0604_MB_Metadata.txt.


text:
Breaking the Gender Covenant
Gender is a covenant I have broken: a covenant with others and a covenant with myself.
"Did anyone ever teach you to be true to yourself?" a therapist once asked me. I had come to her in the midst of what I call my gender crisis — the physical, mental, and emotional breakdown I experienced after 40-plus years of living as the male I knew I wasn't. I had just told her about my shame about hiding for decades my lifelong sense that I was female. Having failed to keep faith with my own gender identity, how could I now break my covenant with my wife, my children, and all who knew me as a man?
Gender is a covenant, a promise that the maleness or femaleness we present in public represents both our genitalia and our gender identity, our private sense of whether we are male or female. People who visibly fail to keep this covenant, those we call "transgender," are subject to severe penalties: exile from family and friends, loss of employment, and verbal and physical abuse.
Every week, one or two transgender Americans are killed, in a hate crime, for breaking the covenant of gender.
Most of us are literally born into the covenant of gender, when those who deliver us from our mothers' wombs examine our genitals and proclaim, "It's a boy!" or, "It's a girl!" My body entered me into the covenant as male, and, for 45 years, that is the way I presented myself to the world. But though my gender presentation matched my genitalia, I was still breaking the gender covenant, because the maleness I presented to others didn't reflect my own sense of who I was.
Transsexuality — the mismatch between physical sex and gender identity — causes many kinds of suffering; for me, one of the worst was the guilt and shame I felt about pretending to be a man. Those feelings drove me to confess to my college sweetheart, the woman I later married, that I was transgender when we were sophomores in college. She offered me a private version of the gender covenant: As long as I lived as a man, she would love and stay with me, even though she knew my gender identity was female. That was the first gender covenant I could keep, for it meant that at least in one relationship, I could meet the expectation of others without betraying my sense of self.
For the next two decades, I kept this covenant: to be true to my wife, and, later, to our children, by living as a man. I wrote and published poetry, gave divrei Torah and served on the board of our local nondenominational synagogue, completed a doctorate, and finally landed a tenure-track job at the Stern College for Women of Yeshiva University, where I taught, and still teach, writing and American literature. In short, I became what we call "a successful man," which in my case referred to the lines on my C.V. but not to my success at living, loving, writing, and teaching as a man. If I had really been that man, I could have lived happily ever after within the terms of the gender covenant. Instead, I became steadily more miserable; by my early 40s, it literally, physically, and emotionally made me sick to live as a man.
Most people — the vast majority whose physical sex matches their gender identities — don't realize that "covenant" applies to gender until they see someone like me breaking it. Then, they tend to be angry. Some people have told me that my gender transition is pathologically selfish; having lived as a male for 45 years, why couldn't I keep living as a man for the sake of my wife and children? Others have become angry at my now-ex-wife for not staying with me through and despite my transition.
The moral value of a covenant can be measured by how we respond when it is broken. When the Israelites at Sinai broke their brand-new covenant with God (constructing the golden calf), the responses — Moses' passionate pleas for divine presence and God's forgiveness and revelation of the thirteen attributes of mercy — resulted in a greater understanding and a deeper mutual relationship between God and Israel. When the covenant of gender is broken, the responses — blaming, shaming, victim-villain narratives — tend to mirror rather than to expand the narrow binary terms of the gender covenant.
My experience with breaking this covenant has taught me to strive not just for a more embracing, nonbinary conception of gender, but for a more embracing, nonbinary moral language — a language that acknowledges suffering, and the need for growth and forgiveness, on all sides. My transition has not only been from an inauthentic life as a man to an authentic life as a woman. It has also been from a gender covenant based upon physical sex and social convention to a new gender covenant in which gender doesn't mean being male or female, but being true to others by becoming our truest selves.
Reprinted with permission from the journal Sh'ma: A Journal of Jewish Ideas May 2013, as part of a larger conversation on rethinking covenants.


text:
The following content is for Members Only
Membership at Hegre.com costs
less than $0.21 a day!
Membership at Hegre.com costs
less than $0.21 a day!
Prepare yourself for a super-sexy day at the beach with the sensational Muriel.
Let us set the scene for you… imagine yourself on the sands of a golden shoreline with the sun gently warming your skin.
The sky is perfectly blue ,you can hear the sound of the waves gently lapping at the shore and there, right in front of you, Muriel is stretched out naked on the beach. You could say you have landed in paradise!
So enjoy your day at the beach with Muriel as she oils up her full pert breasts in preparation for soaking up some rays. And don't forget to follow her down to the sea where she where she goes for a short but very bouncy jog!
Sexy, summery and very, very hot Muriel is the ultimate beach bum!
Would you like to comment? Join us today, or sign in if you're already a member.
For your convenience some comments has been automatically translated to your language of choice. Click "SHOW ORIGINAL TEXT" on the auto translated comments to read the original.


text:
The Monad.Reader
Jump to navigation
Jump to search
The Monad.Reader is an electronic magazine about all things Haskell. It is less formal than journal, but more enduring than a wiki-page or blog post. There have been a wide variety of articles, including: exciting code fragments, intriguing puzzles, book reviews, tutorials, and even half-baked research ideas.
Please note that the Monad.Reader has moved to http://themonadreader.wordpress.com. This site will no longer be updated.
Older issues,1-13, can be found here.


text:
The security of your personal information is very important to us. We never sell or rent your personal information to any third parties under any circumstances. We value your trust very highly, and will work to protect the security and privacy of any personal information you provide to us and will only use it as we describe here in our Privacy Policy.
Personal Information means information about you which is, or can be, tied to you as an individual. Nutra Relief will collect and use Personal Information of customers and members only as follows:
Our purpose in collecting Personal Information.
We collect Personal Information to deliver the products and services you want; administer our businesses; provide customer service; and respond to legal process (such as subpoenas and warrants).
What Personal Information we collect and how we collect it.
The Personal Information we collect may include:
* Contact information; names, addresses, email addresses and other such information required for us to transact business with you; and
* Technical information (such as your computers operating system and browser type, and the address of a referring website, if any, and the path you take through our web pages) when you visit our websites;
When you visit our website, we may place a "cookie," a small computer file, on your computer to allow our web site to function properly. You may delete this cookie from your computer. You may also set your Internet browser to reject cookies, however, doing so will compromise the functionality of our website.
How we use Personal Information.
We do not sell or rent Personal Information to others.
We do not use cookies to track movements on websites other than our own.
We do not disclose Personal Information to others.
We take reasonable steps to protect your Personal Information.
We maintain reasonable physical, technical, and procedural measures to limit access to Personal Information to authorized individuals with appropriate purposes.
Modifications to our privacy policies.
We reserve the right to change our privacy policies at any time, except as may be prohibited by law. We will post revisions online. Use of our websites or services or the purchase of products after posted changes means that you consent to the privacy policies as changed.
Contact us for more information about our privacy policies.


text:
First Commonwealth
Federal Credit Union
Please read the following before proceeding to:
The website you are about to visit is solely the responsibility of the merchant or other party providing the site. The content of this third-party site, including materials and information, is solely the responsibility of the provider of the site. The Credit Union is not responsible for any such third-party content. Any transactions that you enter into with a vendor, merchant or other party that you access through this third-party site are solely between you and that vendor, merchant or other party. The Credit Union does not endorse the content contained in this third-party site, nor the organization publishing the site, and hereby disclaims any responsibility for such content. The Credit Union Privacy Policy does not apply to this third-party site, and for further information you should consult the privacy disclosures of the third-party site.


text:
Better Budget Process Initiative
There is a growing consensus that the budget process is broken. Deadlines are missed, controls circumvented, gimmicks employed, and the long-term ignored. The Better Budget Process Initiative aims to address this problem through concrete ideas to reform and improve the way the budget is developed, including placing greater focus on the long-term fiscal outlook, dealing with the debt limit, strengthening statutory budget enforcement, revising the content and structure of the Congressional budget resolution, biennial budgeting, and addressing the treatment of tax expenditures.
Click here for a summary list of all of the budget process reform options put forward by the Better Budget Process Initiative.
The Budget Act At 50 – Budget Process Reform Recommendations for the 118th Congress
The Congressional Budget and Impoundment Control Act will turn 50 next year, and the budget process is showing its age. The current budget process is in many ways broken. This paper presents a number of options that could help improve the budget process in three major areas including timely budgeting and accountability; fiscal responsibility; and transparency and straightforward budgeting.
Better Budget Process Initiative: Automatic CRs Can Improve the Appropriations Process
Shutdowns impose unnecessary costs on the public, on federal workers, and on Congress. They are also unnecessary. Fortunately, we can avoid such disruptions. In the wake of the U.S. government's most recent shutdown, bipartisan support surged for legislation to provide for automatic continuing resolutions (auto-CRs). Under current law, if Congress fails to pass new appropriations bills or a CR before the prior funding expires, parts of the government cease operations. Auto-CRs ensure that funding for programs will continue, thereby preventing such government shutdowns. Adopting auto-CRs is one of several important improvements to the budget process that Congress should consider.
Budget Resolution Principles for Fiscal Year 2020
The congressional budget resolution should establish the nation's priorities, the approach to financing them, and a plan to ensure the nation is on a fiscally responsible track. We recommend a series of principles that Congress should adhere to when crafting a budget resolution.
Leon Panetta's Testimony on Budget and Appropriations Process Reforms
On July 12, 2018, Committee for a Responsible Federal Budget Co-Chair Leon Panetta testified before the Joint Select Committee on Budget and Appropriations Process Reform on "Opportunities to Improve the Appropriations Process." His written testimony drew on many of the Better Budget Process Initiative's recommendations.
The Better Budget Process Initiative: Recommendations for the JSC
The congressional Joint Select Committee on Budget and Appropriations Process Reform (JSC) is considering improvements to the budget process. We recommend reforms that encourage timely budgeting and avoid crisis-driven budgets; strengthen budget enforcement and prevent gimmicks; budget comprehensively and reform budget baselines; expand focus on the long term; and improve fiscal outcomes.
Maya MacGuineas's Testimony on Budget Resolution Reforms
On May 24, 2018, Committee for a Responsible Federal Budget president Maya MacGuineas testified before the Joint Select Committee on Budget and Appropriations Process Reform on "The Budget Resolution—Content, Timeliness, and Enforcement."
The Better Budget Process Initiative: Setting the Benchmark: Reforms to Budget Baseline Rules
Budget baselines are among the most important – but widely misunderstood – elements of budgeting and policymaking. The budgetary impact of a given legislative change can be measured in several ways. Baselines allow us to measure the future effect of changes relative to projections under the status quo. Budget baselines are produced by the Congressional Budget Office (CBO), Office of Management and Budget (OMB), and a number of outside organizations. In general, they serve two purposes – to provide projections of current fiscal policy and to offer a measuring stick to compare policy changes. CBO describes its baseline as a "current law" baseline, meaning it projects spending and revenue assuming no legislative changes. In reality, it is a current law baseline modified with CBO's default assumptions. For example, the baseline assumes discretionary appropriations are passed each year (and grow with inflation), various expiring mandatory programs continue, trust fund depletion does not constrain spending on programs paid from those funds, and the debt limit continues to be raised over time. These departures from current law intend to allow CBO's baseline to better serve as a neutral benchmark. However, within the current baseline framework there are opportunities for gimmicks and other fiscal mischief as well as unnecessary confusion. As part of our Better Budget Process Initiative, we have identified six potential changes to baseline rules that would better serve policymakers and the public.
The Better Budget Process Initiative: Senate Budget Procedures - Prospects for Reform
Before the Senate adjourned in July for summer recess, Senate Budget Committee Chairman Mike Enzi (R-WY) released an outline recommending changes to the current budget process. The outline includes fundamental reforms of the budget process such as establishing enforceable fiscal targets, establishing a budget concepts commission, and moving to biennial budgeting. It also includes smaller procedural changes that Congress could act upon as soon as this fall.
The Better Budget Process Initiative: Strengthening the Budget Resolution
One of the key elements of the Congressional Budget Control and Impoundment Act of 1974 (Budget Act) was the provision to adopt a budget resolution, which sets out Congressional priorities on the budget and provides a framework for legislation affecting spending and revenues. The budget resolution is a concurrent resolution, which means it is adopted by the House and Senate but not signed by the President. It establishes internal rules and procedures for legislation that impacts spending and revenues. But currently, the budget resolution mechanism has not been an effective tool in providing a framework for legislative action or imposing fiscal discipline. Congress has repeatedly failed to pass budget resolutions in recent years, and when it does adopt a budget resolution it fails to follow through and enforce the budget.
The Better Budget Process Initiative: Strengthening Statutory Budget Enforcement
In 2010 and 2011, policymakers enacted two important budget process improvements: statutory caps on discretionary spending and the statutory pay-as-you-go (PAYGO) law to prevent tax cuts or mandatory spending increases that are not offset by other changes. Although neither of these laws will prevent the unsustainable growth of the debt, both are designed to prevent policymakers from worsening the overall fiscal situation. Unfortunately, policymakers have negated these rules' effectiveness by finding ways to circumvent them on many occasions.
The experience with the discretionary spending caps and PAYGO requirements originally enacted as part of the 1990 Budget Enforcement Act demonstrated that when lawmakers took these rules seriously, they were more likely to abide by the rules. With debt at a modern record high and projected to grow unsustainably, it is unacceptable for policymakers to avoid hard choices by relying on gimmicks and loopholes. Congress should therefore reaffirm its commitment to strictly enforced budget rules, and enact reforms strengthening these rules to make it harder to evade the letter and spirit of the rules. We recommend several improvements to help them do so.
The Better Budget Process Initiative: Improving the Debt Limit
The debt ceiling was first created in 1917 and established in its current form around 1940. Prior to that, Congress had to approve each issuance of debt, whereas the new ceiling allowed debt to be issued regularly as long as it stayed below a nominal limit. Because spending has generally exceeded revenue collection causing the government to borrow each year, the country has regularly bumped up against the debt limit. As a result, the debt limit has been increased, extended, or suspended a total of 92 times. A number of these increases, in the past, have been used as an opportunity to address our growing national debt or enact Fiscal reforms. As one of the only fiscal speed bumps in the budget process, it has served the purpose of helping to focus Washington's attention on our fiscal situation. This paper outlines options to reform the debt limit.
The Better Budget Process Initiative: Improving Focus on the Long Term
The budget process focuses on the short term, often at the expense of longer-term considerations. This distortion allows policies to be crafted in ways that mask their true costs, and produces results that downplay looming fiscal challenges. The short-term focus leads to many poor outcomes, such as emphasis on short-term deficit reduction (with little improvement in the long-term fiscal outlook), the use of "timing gimmicks" designed to obscure the budgetary impact of policy choices, and the reliance on one-time savings are to ensure "deficit neutrality" within a budget window but deficit increases beyond it. The short-term emphasis is the result of both an overreliance on ten-year budget windows for scoring and analysis, and insufficient enforcement of long-term fiscal goals. Modifying the rules governing the budget process could be a powerful tool to help correct this myopic thinking. We suggest several possible remedies in this paper.
The Budget Act at 40: Time for a Tune Up?
Forty years ago, President Nixon signed the Congressional Budget and Impoundment Control Act of 1974 ("The Budget Act") into law, establishing the modern budget process and institutions. Enacted to settle ongoing clashes between the executive and legislative branches, the Budget Act established procedures and institutions to allow Congress to establish its own budget priorities independent of the executive branch and provide a framework to guide and coordinate legislation affecting spending and revenues within overall budgetary limits.
There is a growing consensus that the budget process is broken. After functioning relatively well for more than two decades, Congress has increasingly moved to dealing with budget issues on an ad hoc basis. Congress adopted an annual budget resolution, approved by both chambers, each fiscal year from 1976 through 1998. Since then, however, there have been eight fiscal years in which Congress has not approved a budget resolution. Furthermore, Congress has increasingly relied on temporary patches to fund parts of the federal government rather than full-year appropriations.
Better Budget Process Summit: Building Momentum for Meaningful Reform
On February 25, the Committee for a Responsible Federal Budget hosted the second Better Budget Process Summit on "Building Momentum for Meaningful Reform." The event convened lawmakers, Congressional staff, policy experts, journalists, and members of the public interested in reforming our broken budget and appropriations process. After two expert panels on budget process reform, the summit concluded with remarks from Senator James Lankford (R-OK) on his bill with Senator Maggie Hassan (D-NH), the Prevent Government Shutdowns Act, and a keynote address from Senate Budget Committee Chairman Mike Enzi (R-WY) and Senator Sheldon Whitehouse (D-RI) on their bill, the Bipartisan Congressional Budget Reform Act.
National Conference Call with Senators James Lankford and Maggie Hassan
On July 24, 2019, the Committee for a Responsible Federal Budget and the Campaign to Fix the Debt hosted a call with Senators James Lankford (R-OK) and Maggie Hassan (D-NH) to discuss their bipartisan Prevent Government Shutdowns Act. The bill would establish an automatic continuing resolution to prevent government shutdowns and would put in place incentives to encourage Congress to reach agreement on new spending bills.
Better Budget Process Summit: Rebuilding Confidence in Congress
On February 26, 2018, the Committee for a Responsible Federal Budget hosted the first annual Better Budget Process Summit on "Rebuilding Confidence in Congress: Breaking Through on Budget Reform." The event brought together budget experts and stakeholders from across the ideological spectrum to discuss ways to improve the current broken budget and appropriations process. After two expert panels on budget process reform, the summit concluded with a session featuring Senators David Perdue (R-GA) and Sheldon Whitehouse (D-RI), members of the newly-formed Joint Select Committee on Budget and Appropriations Process Reform. It aired live on C-SPAN and can be viewed here.
Fixing the Budget Process
As part of our Better Budget Process Initiative, the Committee for a Responsible Federal Budget recently hosted a briefing on Capitol Hill called "Fixing the Budget Process." The event featured remarks from the House Budget Committee Chairman Tom Price (R-GA) and a panel of experts, including our president, Maya MacGuineas; Paul Posner, former federal budget managing director at the Government Accountability Office; Dr. Stuart Butler, senior fellow in economic studies at the Brookings Institute; and Dr. Marvin Phaup, public policy & public administration professor at The George Washington University. The event was moderated by Kelsey Snell, a reporter for The Washington Post. It aired live on C-SPAN and can be viewed here.
Budget Process Reform - Senate Perspectives
Just before summer recess, Senate Budget Committee Chairman Mike Enzi put forward a set of budget process reform recommendations. Chairman Enzi kicked off this event with a keynote followed by a panel of experts, including Charles S. Konigsberg, Principal, Federal Budget Group (@budgetreport); Ed Lorenzen, Senior Advisor, Committee for a Responsible Federal Budget (@CaptainPAYGO); Dr. Roy T. Meyers, Professor of Political Science and Affiliate Professor of Public Policy, University of Maryland, Baltimore County; Dr. F. Stevens Redburn, Professorial Lecturer in Public Policy and Public Administration, The George Washington University, who discussed Enzi's recommendations in the areas of Senate budget procedures, biennial budgeting, a budget concepts commission, and portfolio budgeting. The event was moderated by Ben Weyl, Editor of POLITICO Pro's Budget & Appropriations Brief. It aired live on C-SPAN and can be viewed here.


text:
All U.S. orders get free shipping, and all orders placed on workdays before 1pm EST get shipped that same day. Details here.
Not sure you're ordering the right part? No worries, we can send you a prepaid return label. Details here.
We manufacture all of our products and sell them to you with no middleman, so chances are you won't find lower prices anywhere around.
Not sure which part you need for your appliance? Give us a ring during working hours (Mon-Fri 9am-5pm EST), and we'll help you out promptly:
With these Black & Decker filter replacements, cleaning becomes the easiest chore of the day. Regularly replaced filters improve vacuum performance. Fits BDASV102 Airswivel Vacuums.
Please note the following important information about this product from Think Crucial: (i) it is a generic replacement, NOT a Black and Decker® Original Equipment Manufacturer (OEM) product; (ii) because it is not a Black and Decker® OEM product, it is not covered by any Black and Decker® guarantee or warranty; (iii) use of this generic replacement may violate or void Black and Decker's® guarantee or warranty - it is entirely your responsibility to check, and entirely your risk if you decide to use this product; (iv) we do not guarantee or warrant that this generic replacement is compatible with any product from Black and Decker® or any other provider. Please check your manufacturer's warranty with regard to the use of non-OEM parts. Think Crucial provides no warranty or guarantee with regard to the product or its compatibility with your Black and Decker® product. The Black and Decker® brand and all Black and Decker® trademarks belong to Black and Decker® or its affiliates, and are used here only to explain the compatibility features of the generic replacement product.


text:
Haskell Hackaton in Cambridge, UK, August 12-14, 2011
NEW: post-hackathon report
We'll build a list of everything that happened during the Hackathon on a separate page: CamHac/PostHackathonReport.
Come and spend a weekend in Cambridge hacking Haskell code in great surroundings with fantastic company! Haskell Hackathons are a tradition where everyone is welcome; we get together, work on projects with others or just do your own thing, the overall goal being to improve the Haskell ecosystem.
CamHac will be held from 12-14 August 2011, at Homerton College in Cambridge. As with previous Hackathons, all are welcome -- you do not have to be a Haskell guru. All you need is a basic knowledge of Haskell, a willingness to learn, and a project you're excited to help with (or a project of your own to work on).
There will be lots of hacking, good food, and, of course, fun!
- Organiser: Simon Marlow (JaffaCake on IRC)
- Mailing list: email@example.com
- IRC channel: #camhac on FreeNode
Many thanks to Microsoft Research Cambridge for agreeing to sponsor the event.
We are full, sorry! All 72 places are currently allocated.
We do have a waiting list, which we will use to allocate places if people drop out. If you would like to be added to it, please email firstname.lastname@example.com stating that you would like to be added to the waiting list for the "Haskell Hackathon", with the following information
Full name: Which days you are attending on: day 1: yes/no day 2: yes/no day 3: yes/no Dietary requirements:
We're in the Leah Manning Room of Homerton Conference Centre. It is about 15 minutes walk from the train station, and Cambridge town centre is about 30 minutes walk.
- 0900: arrive any time from 9am, coffee and snacks will be available until 1000. Make sure you pick up your name badge and wifi details from the registration desk on arrival.
- 1045: break (coffee/tea, biscuits)
- 1230: lunch
- 1500: break (coffee/tea, cake)
- 1730: finish (we might be able to extend this a little if necessary)
There will be WiFi access, you will be given details when you arrive. We've been told that extra WiFi has been installed in the meeting room for us.
There will be a projector for giving talks/demos. We will probably reserve a part of the time for talks and demos.
Tea and coffee will be supplied. We will have to go out to find lunch, but there are various places to eat and buy food at the Cambridge Leisure Park a few minutes walk towards Cambridge town centre. In the evening we will probably head towards the town where there are plenty of good restaurants.
We have been advised that only food provided by or purchased from Homerton College can be consumed on the premises.
Local arrangements
Getting to Cambridge
By Plane
- Stansted Airport: Stansted is the nearest of the London-area airports to Cambridge. It is mostly served by flights to and from mainland Europe, Ireland, and elsewhere in the UK. By train it is about 30 minutes to Cambridge, bus about 1 hour.
- Heathrow Airport: Heathrow is the principal London-area airport and one of the busiest in Europe with a wide range of national, European, and international services. By train it is about 1h30 to 2h to Cambridge (Heathrow Express is faster but more expensive).
- Gatwick Airport: Gatwick is the second "London" airport with a wide range of national, European and international services. By train it is about 2h to Cambridge.
- Other airports: Luton Airport, Norwich airport, and Southend airport are other regional airports in the East Anglia region. If you use these, car or taxi is the best option for travel to Cambridge.
Trains from London
London has two train lines into Cambridge, London Kings Cross and London Liverpool Street. There is a regular service on both lines and duration is under an hour on the direct trains. Go to National Rail to check train times.
You can usually buy tickets at the station both at a ticket machine or a staffed counter. You usually will not be able to buy tickets on the train without paying a fine. Tickets can be cheaper if you buy off-peak and return trip. Off-peak tickets are usually valid on weekends and after 10 a.m. on weekdays. Make sure, though, to check National Rail for which trains are eligible for off-peak tickets.
Getting to the venue
Walk from the train station (about 15 minutes)
Local Taxis: Panther Taxis 01223 715715
VisitCambridge: Where to Stay in Cambridge
The nearest hotels to the venue seem to be:
- Travelodge (Cambridge Central) is just a few minutes walk from the venue. It is currently charging £65.80 per night for 11-14 August.
- Helen Hotel
- Bridge Guest House
- Fairways Guest House
- Abbeyfield Guest House
- Rock View Guest House
- Alington House Guest House
- Cambridge Youth Hostel. The hostel does not offer single rooms, but you might be able to organise a group to occupy one 4-bed room.
- Stay in Cambridge Colleges
If you contact any of the above and find they're booked up, please remove them from the list.
Microsoft Research recommends the following hotels to visitors, these are closer to the city centre but are probably a lot more expensive than those above:
Use this space to list projects you are interested in working on, and add your name to projects you are interested in helping with.
- General hacking away at Snap Framework (exact goals TBD), perhaps adding/improving documentation/tutorials at the same time. (Jurriën Stutterheim, Twey)
- Darcs
- Something games/3d related? (Stephen L) [edit: can't think of anything gamesy, so probably will do some graph data-mining stuff]
- LambdaCube 3D engine (Csaba Hruska)
- Discussion about graphics pipeline DSL
- Designing/proposing/implementing a new low-level network package, similar in role to 'network' itself (Ben Millwood, Twey)
- See also User:benmachine/New network package
- A service to help find or contribute examples of usage of a package, under hackage, github.
- Or a clone of Carcassonne (a board game). - Neillb
- Writing a library that implements the ideas of Typing Haskell In Haskell to type-check, say, a haskell-src-exts AST (Ben Millwood, Stijn van Drongelen)
- I've been advised that THIH is actually quite old, and I might want to find a different base to work from. Any input appreciated. --Ben
- Use a constraint-based approach, like the monadic constraint library that was presented at Anglohaskell the other year. Much more pleasant. --Philippa
- Since haskell-src-exts includes GHC-specific extensions, why not round-trip via the GHC AST? That could also be used by other tools. --Nominolo
- Part of the idea was to be more lightweight/modular than GHC, but it would still be a good way to test :) --benmachine 00:22, 12 August 2011 (UTC)
- I've been advised that THIH is actually quite old, and I might want to find a different base to work from. Any input appreciated. --Ben
- wxHaskell (Maciek Makowski)
- System.Process: Provide a way to send arbitrary posix signals to a ProcessHandle. Matthiasg 20:56, 20 June 2011 (UTC)
- Have an option to avoid using package.cache, because it makes working with Open Embedded quite hard. Matthiasg 15:57, 27 June 2011 (UTC)
- Hackage 2 (Ben Millwood)
- Data.Text (Jasper Van der Jeugt)
- unordered-containers (Johan Tibell)
- I probably deserve a real kicking for this, but: a TeX replacement. Specifically, embed TeX in Haskell so you can both parse down to its semantic layer and manipulate the semantic layer stuff (which is still pretty-printable back out to TeX as a bunch of primitives and not-so-primitives). Got a bunch of ideas for this, but it's mostly an itch I just got - am currently reading through the TeXbook to check I've understood how TeX itself works sufficiently though, and who doesn't want a backwards-compatible-including-extensions TeX replacement with better syntax, typechecking and the potential for better debugging? --PhilippaCowderoy 22:04, 3 August 2011 (UTC)
- Not going to be there, so unless anyone's feeling particularly brave I'm guessing this one's a goner.
- Cabal, cabal-install, Haskell Platform, nixpkgs (Andres Loeh)
- A NumPy / PDL style scientific library (Jacek Generowicz)
- Generating bindings using GObjectIntrospection (Will Thompson)
If you have a talk or demo you want to give, add your name to the list below. Let's restrict these to short slots (say 20 mins max). Tentatively we'll have a session of talks and demos on Saturday afternoon, but we can always move things around if necessary.
- Simon Marlow
- Jurriën Stutterheim
- Neil Mitchell
- Jasper Van der Jeugt
- Max Bolingbroke
- Ben Millwood 'benmachine'
- Roman Leshchinskiy
- Gregory Collins
- Martijn van Steenbergen
- Sjoerd Visscher
- Sebastiaan Visser
- Tom Lokhorst
- Erik Hesselink
- Jeff Foster
- Sebastian Korten
- Alessandro Vermeulen
- Vlad Hanciuta
- Ganesh Sittampalam
- Eric Kow
- Alexander Njemz
- Mikolaj Konarski
- Ian Lynagh
- Andres Löh
- Jeroen Janssen
- Nicolas Wu
- Duncan Coutts
- Dominic Orchard
- Jacek Generowicz
- Owen Stephens
- Stephen Lavelle
- Sam Martin
- Alex Horsman
- Andy Georges
- Niklas Larsson
- Raeez Lorgat
- Maryna Strelchuk
- Vincent Hanquez
- Chris Done
- Tomas Petricek
- Thomas Schilling
- Dragos Ionita
- Simon Meier
- Will Thompson
- Sergii Strelchuk
- Lennart Kolmodin
- Steven Keuchel
- Michal Terepeta
- Maciek Makowski
- Johannes Weiß
- Alejandro Serrano
- Mike McClurg
- Stefan Wehr
- David Leuschner
- James 'Twey' Kay
- Simon PJ
- Neill Bogie
- Csaba Hruska
- Bart Coppens
- Stijn van Drongelen
- Jeremy Yallop
- Paul Wilson
- Dmitry Astapov
- Matthias Görgens
- Johan Tibell
- Ian Knopke
- A O Van Emmenis
- Add your name here, once registered...


text:
Privacy Policy
General Data Protection Policy for the Internet Pages of the Ludwig-Maximilians-Universität München (hereinafter the "LMU")
I. Contact Information in Connection with the Internet Presence of the LMU
I.1. Information on the Person Responsible for Data Protection at the LMU
The person responsible for the LMU internet pages within the meaning of the General Data Protection Regulation (DSGVO) and of other national data protection laws or other provisions relating to data protection, is the LMU, which is legally represented by their president. Contact information can be found here (copyright).The particular facilities of the LMU are each responsible for the content offered on the internet pages of the LMU. Please direct any questions relating to a particular internet page of the LMU to the particular contact party who is listed for the particular internet page in the copyright notice.
I.2 Name and Address of the Official LMU Data Protection Officer
The contact data of the official LMU data protection officer is found on the internet page of the LMU at www.lmu.de/datenschutz.
The official data protection officer is available to answer questions about data protection at the LMU. Please use the contact form on the internet page of the official LMU data protection officer for any questions: https://www.uni-muenchen.de/einrichtungen/orga_lmu/beauftragte/dschutz/Datenschutzkontaktformular.html. Please also use this form to report any data protection events which become known to you from your use of the LMU internet pages.
II. General Information about Data Processing on the LMU Internet Pages
II.1 Applicability of the Data Protection Policy
This data protection policy applies to the processing of personal data in connection with the LMU internet presence.
- According to Art. 4 item 1 DSGVO, "personal data" means all information which relates to an identified or identifiable, natural person; the term "identifiable" is deemed to mean a natural person who can be identified directly or indirectly, in particular through assignment of an identifier such as a name, an identifying number, location data, an online identity or one or several special features which are an expression of physical, physiological, genetic, psychic, financial, cultural or social identity of this natural person.
- According to Art. 4 item 2 DSGVO, "processing" means any process executed with or without the aid of automated methods, or any such set of methods in connection with personal data, such as the collection, acquisition, organization, ordering, saving, adapting or changing, read-out, query, use, disclosure by means of transmittal, dissemination or any other form of manipulation, coordination or linking, limitation, deletion or destruction.
II.2 Purpose and Legal basis for processing of personal data
In accordance with Art. 2 para. 6 BayHSchG, Art. 4 para. 1 lines 1 and 2 BayEGovG, on our web pages we offer our services and administrative services, and also information for the public about our activities. Personal data will only be processed on the LMU internet pages provided this is necessary to provide a functioning internet page, to present the particular content, or to provide certain services or offers. The processing of personal data occurs either owing to a legal requirement or based on the user's consent. When processing of personal data is based on a consent, then such processing shall occur based on Art. 6 para. 1 (a) DSGVO. Art. 6 para. 1 (b) DSGVO serves as the legal basis for the processing of personal data required for the performance of a contract to which the user is a party. Insofar as processing personal data is required to fulfil a legal obligation to which the LMU is subject, the applicable legal basis is provided by Art. 6 para. 1 (c) DSGVO. In the event that the vital interests of the affected person or other natural person require the processing of personal data, the applicable legal basis is provided by Art. 6 para. 1 lit. e, para. 3 lit. b DSGVO i.V.m. Art. 4 para. 1 BayDSG. The processing may also be required in fulfillment of a mission which has been assigned to the LMU and which is in the public interest (Art. 6 para. 1 (b) DSGVO). Additional legal basis may also arise from special-legal or other legal regulations, to which reference is made in the particular, individual case.
We use cookies, protocol data files and web analysis tools to prepare business statistics, to implement organizational studies, to check or maintain our web services and to ensure network and information security according to Art. 6 para. 1 BayDSG, § 13 para. 7 TMG, Art. 11 para. 1 BayEGovG. Insofar and inasmuch as the purpose of the processing is not adversely impacted, we will anonymize or pseudomize your personal data.
II.3 Data Deletion and Retention Period
The personal data of users of the LMU internet pages will be deleted or anonymised inasmuch as and provided the particular purpose of the retention has expired and there is no archiving requirement. Deletion or erasure of the data will also occur when a retention period as specified by the European or domestic legislature in EU regulations, laws or other specifications to which the LMU is subject, has expired, unless there is a requirement for continued retention of the data for completion of or fulfillment of a contract. If provided in the referenced regulation, retention for a longer period is possible.
II.4 Data Security
In order to protect your data in a reasonable and comprehensive manner during the processing, and in particular to protect against its transmittal, where necessary and with reference to the prior art, we use appropriate encryption techniques and secure technical systems (e.g. SSL/TLS).
III. Specific Information on Data Processing on the LMU Internet Pages
Every time you visit an LMU website, the LMU system automatically collects data and information from the computer system of the accessing computer. In addition, we process your personal data to the extent you provide such data via the LMU internet pages. In the processing of your personal data we take into account in particular the principles of data protection relating to necessity, purpose, data minimizing, legality, correctness and integrity.
III.1 Use of Active Components and Cookies
Sometimes cookies are placed merely due to a visit to the LMU internet, for example, to identify user-sessions, and also to configure the internet pages in a user-friendly manner. Cookies are text files that are stored on the Internet browser or by the Internet browser on the user's computer system. If a user visits an internet page, a cookie may be stored in the user's operating system. This cookie contains a unique character sequence that permits the browser to be specifically identified upon a subsequent visit to the internet page.
A session-ID is saved in the cookies for public offers exclusively for identification of the user-session (session-cookie). These session-cookies are automatically deleted at the end of your visit by closing your browser.
Cookies are stored on your computer and transmitted to the LMU internet page by your computer. Therefore, you as a user have full control over the use of cookies. You can deactivate or restrict the transmission of cookies by changing the configuration of your Internet browser. Cookies that have already been saved can be deleted at any time. This can also occur automatically.
The saving of these cookies can be turned off at any time by making a corresponding setting in the internet browser; this can also be done automatically.
However, several elements of our internet pages require that the calling internet browser can also be identified even after a page-change. If cookies are deactivated for the LMU internet pages, it is possible that not all functions of the LMU internet pages can still be accessed.
The following services can only be used when the saving of cookies is allowed:
- Web forms
- The event calendar : www.mcqst.de/news-and-events/events/events-overview.html & www.uni-muenchen.de/aktuelles/veranstaltungen/index.html
- All offers saved via the central authentication mechanism
The transmission of flash-cookies cannot be disabled via the settings in your internet browser, but by changing the setting of the flash player.
III.2 Use of Webpage Analysis Tool Matomo (formerly PIWIK)
Programs for evaluation of user behavior on the LMU internet pages are only used by the LMU in an anonymized form. On several internet pages we use the Open-Source-Software-Tool Matomo (formerly PIWIK) for analysis of your surfing behavior. This software places a cookie on your computer. If individual pages - even sub-pages - of our internet pages are called, then the following anonymized data is saved.
- Two bytes of the IP address of the calling system (user's system)
- The called internet page
- The internet page from which the user has arrived at the called internet page (referrer)
- The sub-pages which are called from the called internet page
- The dwell-time on the internet page
- The frequency of call-up of the internet page
- Information about the operating system, type of browser, video display resolution
The software Matomo is set up so that full IP addresses are not saved, but rather two bytes of the IP address are masked. In this way an unambiguous association with the calling computer is not possible. Therefore, your IP address is also always anonymized before any evaluation.
The software runs exclusively on the servers of the LMU. Any saving of data occurs only on these servers. Any transmittal to third parties does not occur. Additional information on Matomo is found at https://matomo.org/docs/privacy/ (external link).
The use of Matomo can be disabled in general by making a corresponding setting in your internet browser.
You can decide whether an unambiguous internet analysis cookie may be saved in your browser in order to allow the operator of the internet page to acquire and analyze various statistical - not personal - data. The use of an internet analysis cookie serves the purpose of improving the quality of the internet pages and their content, and for improving user convenience. Web analysis cookies make it clear how the internet page is being used, so that the offering can be optimized.
However, if you decide against it, then please disable the checkbox to set the Matomo deactivation cookie in your browser.
Your visit to this webpage is currently detected and anonymized by the Matomo web analysis tool. Please click here so that your visit will no longer be detected.
The use of Google Analytics on the LMU web servers does not occur for reasons of data protection.
III.3 Use of Social Media Icons or Internet Links
No automatic transmittal of your personal data occurs when using Social Media icons of Facebook, Twitter, Instagram, YouTube, etc. on the LMU internet pages. To prevent automatic data transmission to the vendor of social media, an internet link to these media is disabled on the internet pages of the LMU. For reasons of data security, active social media plugins are not used.
Our social media presence is a part of our publicity work. Our endeavor is to provide and to exchange information with specific target groups.
All our social media vendors are certified under the EU-US Privacy Shield and are transparent to any person, so that a legally reasonable level of protection exists for personal data, for example:
- Linkedin Corporation (https://www.privacyshield.gov/participant?id=a2zt0000000L0UZAA0&status=Active)
- Twitter Inc. (https://www.privacyshield.gov/participant?id=a2zt0000000TORzAAO&status=Active)
- YouTube | Google LLC (https://www.privacyshield.gov/participant?id=a2zt000000001L5AAI&status=Active)
III.4 Use of RSS
An RSS feed is a form of the classical newsletter that you can read either with your browser or with a special program (RSS reader). When we offer an RSS feed, we will use it to inform you about current events. A list of central RSS feeds is provided at https://www.en.uni-muenchen.de/funktionen/rss.
If personal data is collected within the scope of an application for an RSS feed, then this information will be processed exclusively for the purpose of performing the RSS, and will be deleted as soon as it is no longer needed, that is, either after you log off, or after cessation of the RSS.
III.5 Protocols and Preparation of Logfiles
Due to occurring security-related events, e.g. attempted hacking attacks, relevant access data will be saved for every access on all central hosted webpages. The LMU internet server is operated for the LMU by its IT department ( Department VI), Geschwister-Scholl-Platz 1, 80539 München, E-Mail: email@example.com.
Depending on the used access protocol, the protocol data set contains data with the following content:
- IP address for the inquiring computer
- Date and time of the inquiry
- Access method/function requested by the inquiring computer
- Input values (file name etc.) transmitted by the inquiring computer.
- Access status of the web server (data file transmitted, data file not found, command not executed, etc.).
- Name of the requested data file
- URL from which the file was requested/the desired function was initiated
- Information on browser type
- The user's operating system
- Internet pages from which the user's system accessed the LMU internet page
- Internet pages that are called from the LMU internet pages
a) Purpose of the protocol
The saved data are used for purposes of identification and tracking of allowed access and of impermissible access attempts, for maintenance of the internet page functionality on the internet server, and - in anonymized form - for optimizing of the internet offering. Temporary saving of the IP address is also necessary in order to enable delivery of the LMU internet page to your computer. For this purpose the user's IP address must remain stored for the duration of the session. This data is not stored by the LMU together with other personal data.
b) Retention period
The recorded data are saved for a maximum of seven days and then deleted. A longer retention period may occur in an individual case, provided a violation related to security was discovered. Irrespective thereof, retention for an even longer period is possible. In such a case, your IP address will be deleted or scrambled so that an allocation to the calling client is no longer possible.
c) Evaluation of the protocol
Evaluation of the protocol occurs by the authorized employee of the IT department (Department VI), Geschwister-Scholl-Platz 1, 80539 München, E-Mail: firstname.lastname@example.com under contract with the LMU and observing the provisions of data protection law.If the data is urgently required for maintenance of the internet page and the saving of the data in logfiles is required for operation of the internet page, then you will not be entitled to a right of objection.
III.6 Contact Form and Use of Email
You can contact the LMU via the LMU internet pages. Please use the contact form found on the particular internet page, or the email address mentioned on the internet page.
a) Use of a contact form
If you make use of the contact form to communicate with us, then the data provided in the particular input mask will be transmitted to the LMU and saved. Usually this data will pertain to the first and last name, and an email address. The specific data can be found in the particular contact form or in the particular reference to the facility responsible for the content of the particular internet page. Required fields, without which the inquiry cannot be processed, are identified as such in the contact form. We obtain your consent for data processing in the course of the submission process and include a reference to our privacy policy.
In addition to the data you provide, the following data is also stored at the time the message is sent:
On the application server:
- Referrer (URL from which the form was called up)
- User's email address provided in the form
- Receiver's email address for the form
The personal data processed during the application process serve to prevent misuse of the contact form and to ensure the security of our information technology systems.
By using a contact form you will be informed about the data collected and about your particular rights.
b) Use of an email address
In addition to the contact form, it is also possible to send an email to an LMU email address provided for use of the particular internet page. If you send us an email, then your email address and the other data provided by you will only be used for correspondence with you, and will be saved only as long as necessary for this purpose, unless some other legal grounds will justify its continuing retention.
Please note that the use of a non-encrypted email is fundamentally unsecure, that is, it may possibly be read, changed or captured by third parties along the transmission route. Please remember this when you send us information in an email. Therefore the sending of confidential messages should be either by regular mail or by S/MIME (X509-) encryption.
In the event that you wish to send us an encrypted message, please use the public X509-certificate for encryption of your message.
In order that we may also send you confidential messages, please also give us your postal address, if requested. Otherwise there is the possibility that no information can be shared.
In the event that you want to send us a non-encrypted email, then please use preferably a function address at the LMU, provided such an address is provided on the internet page.
Please note that in the case of an email inquiry, we cannot verify your identity and do not know who is concealed behind the email address. A legally secure communication by means of a simple, unsigned email is not ensured, not even if it is encrypted.
At the LMU we sometimes use filters against unwanted advertising (spam filters) that can also sometimes wrongly classify and delete emails as advertising. Emails that can contain harmful programs, e.g. viruses, are deleted automatically.
If you want to receive an encrypted email from us, then please provide us with the necessary information.
III.7 Collection of Other Personal Data, e.g. Newsletter Subscription
It is possible to input your personal data on the LMU internet pages. Your data basically will be encrypted (https) along the transmission route, unless the particular offers specifically make reference thereto.
If personal data is collected for a newsletter subscription, then it will be processed only for the purpose of sending you the newsletter. The particular newsletter can be canceled at any time. To do so, please use the email address oder website provided for the person responsible for sending the newsletter. Additional information will be provided together with your subscription to the newsletter.
III.8 Use of embedded Google maps
Some of the LMU internet pages use the Google Maps service. This service is provided by Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA. The referral occurs exclusively by means of an API (two-click method). The data will only be sent to Google by this program interface after you click on the "Switch to Google Maps" button.When using the Google functions, Google will process your IP address and possibly other personal data (e.g. information about your use of this internet page or subsequent pages or the data offered in Google Maps). Google thus obtains information that you have called up our internet page or the corresponding subsequent pages. This information is usually sent to and saved on a Google server in the USA. This will occur independently of whether Google has set up a user account that you have requested, or whether no user account exists at all. If you are logged in to Google, your data will probably be assigned directly to your user account. If you do not want this data to be assigned to your profile at Google, then you must first log off your user account at Google before you switch to Google Maps. But Google will save your data (even for users not logged on or registered) as a user profile and will evaluate this data for their own internal purposes for advertising, market research and needs-based structuring of their internet pages, and may also inform other users of the social network about your activities on our internet page.You have a right to object to the formation of this usage profile; to exercise this right you must apply directly and exclusively to Google. The LMU as provider of our internet pages has no influence on this data processing. If you do not agree to the transfer of your personal data to Google, then do not click on "Switch to Google Maps." Then no data will be transferred to Google, however, a map will also not be opened.Your personal data will only be collected and transferred to Google by our internet page if you click on the button "Continue to Google Maps." The use of Google Maps is not absolutely necessary to obtain information about our internet pages and is thus voluntary for you. The incorporation of Google Maps into our internet pages occurs in the interest of a responsive presentation of our internet offers and to ensure a fast and convenient finding of sites available on our internet pages. This represents a justifiable interest within the meaning of Art. 6 para. 1 f) GDPR. In addition, Google Inc. is certified under the EU-US "Privacy Shield" Data Protection Agreement, whereby Google ensures a level of data protection equivalent to that of the EU in regard to data processing.More information on the handling of usage data is found in the Google terms of usage at
- http://www.google.de/intl/de/policies/terms/regional.html
- or for Google Maps at https://www.google.com/intl/de_US/help/terms_maps.html
- The Google data privacy policy is found at https://www.google.de/intl/de/policies/privacy/
- and the data privacy policy for Google Maps is found at https://www.google.com/intl/de_de/help/terms_maps.html
IV. Your Data Protection Rights as an Affected Person
As a part of the LMU internet presence, personal data is processed within the scope stated above. To this extent you are an affected person within the meaning of the DSGVO and are entitled to the following rights with respect to the LMU:
IV.1 Right to information
You can ask the LMU to confirm whether we process personal data concerning you.
If such data is processed, you can request the following information from the LMU:
- The purposes of the processing for which the personal data are intended;
- The categories of personal data processed;
- The recipients or categories of recipients to whom personal data concerning you have been or will be disclosed;
- The period for which the personal data will be stored, or if that is not possible, the criteria used to determine that period;
- The right to request from the responsible officer to correct or delete your personal data, a right of restriction of processing or a right to object to processing as well as the right to data portability;
- A right to complain to an oversight authority, in the case of the LMU the directly cognizant data protection oversight authority is the Bavarian State Officer for Data Protection ( https://www.datenschutz-bayern.de) (external link);
- All available information regarding the source of the data if personal data was not collected from you;
- The existence of automated decision-making, including profiling, referred to in Article 22 para. 1 and 4 DSGVO and, at least in those cases, meaningful information about the logic involved, as well as the significance and the envisaged consequences of such processing for the affected person.
You have the right to request information concerning whether your personal data will be transferred to a third country or international organization. In such cases, you may request to be informed of the appropriate guarantees pursuant to Art. 46 DSGVO as related to this transfer.
Your right to information is subject to legal restrictions and is not absolute, rather, it is limited in particular in the following cases:
- If a large volume of information is saved for an affected person, then the LMU may request that the information be restricted to that information or processing which relates to the request for information.
- Obvious unfounded or excessive requests, or frequent repetitions may result in rejection or in compensation of costs.
- The granting of information must not affect the rights of the LMU or other persons (in this regard, professional secrets, business secrets, data with reference to other persons are exempted).
- The information may be withheld under the circumstances stated in Art. 10 BayDSG.
- In the case of data processing for scientific or historical research purposes and for statistical purposes, your right to information may additionally be restricted if it is likely that the completion of the research or statistical work will be made impossible or seriously hampered, and the restriction is necessary to complete the research or statistical work (Art. 25 BayDSG).
IV.2 Right to Rectification
You have the right to rectify and/or to complete inaccurate and/or incomplete personal data saved by the LMU. The LMU will make the correction without delay.In the case of data processing for scientific or historical research purposes and for statistical purposes, your right to rectification may be restricted if it is likely that the completion of the research or statistical work will be made impossible or seriously hampered, and the restriction is necessary to complete the research or statistical work (Art. 25 BayDSG).
IV.3 Right to Restriction of Processing
Under the following circumstances you may request a restriction of processing of your personal data:
- If you contest the accuracy of the personal data, the restriction will extend for a period enabling the LMU to verify the accuracy of the personal data;
- The processing is unlawful and you oppose the erasure of the personal data and request the restriction of its use instead;
- The LMU no longer needs the personal data for the purposes of the processing, but it is required by you for the establishment, exercise or defense of legal claims;
- If you have objected to processing pursuant to Article 21 para. 1 DSGVO pending the verification whether the legitimate grounds of the LMU override those asserted by you.
IV.4 Right to Deletion
a) Deletion requirement
You can request the LMU to delete your personal data without delay. The LMU is required to delete this data without delay, provided one of the following reasons applies:
- The personal data concerning you is no longer necessary in relation to the purposes for which it was collected or otherwise processed and the processing for other purposes is not permissible.
- You withdraw consent on which the processing is based according to Art. 6 para. 1 (a) or Art. 9 para. 2 (a) DSGVO, and where there is no other legal grounds for the processing.
- You object to the processing pursuant to Art. 21 para. 1 DSGVO and there are no overriding legitimate grounds for the processing, or you object to the processing pursuant to Art. 21 para. 2 DSGVO.
- Personal data concerning you have been unlawfully processed.
- The personal data concerning you have to be erased for compliance with a legal obligation in Union or Member State law to which the responsible person is subject.
- The personal data concerning you have been collected in relation to an offer of services of the information company referred to in Art. 8 para. 1 DSGVO.
b) Notification to third parties
Where the LMU has made the personal data public and is obliged pursuant to Art. 17 para. 1 DSGVO to erase the personal data, the responsible officer, taking account of available technology and the cost of implementation, shall take reasonable steps, including technical measures, to inform officers who are processing the personal data, that you have requested the deletion by such officers of any links to, or copy or replication of, that personal data.
c) Exceptions
The right to erasure does not apply to the extent processing is necessary
- For exercising the right of freedom of expression and information;
- For completion of a legal obligation which requires the processing according to the laws of the EU or of member states to which the LMU is subject, or to complete a task in the public interest or in exercise of official authority which has been conferred upon the LMU;
- For reasons of public interest in the area of public health in accordance with Art. 9 para. 2 (h) and (i) as well as Art. 9 para. 3 DSGVO;
- For archiving purposes in the public interest, scientific or historical research purposes or statistical purposes in accordance with Art. 89 para. 1 DSGVO in so far as the right referred to in letter a) above is likely to render impossible or seriously impair the achievement of the objectives of that processing; or
- For the establishment, exercise or defense of legal claims.
IV. 5 Right to notification
If you have asserted your right to rectification, erasure or restriction of processing vis-a-vis the LMU, then we are obliged to communicate any rectification or erasure of personal data or restriction of processing to each recipient to whom the personal data have been disclosed, unless this proves impossible or involves disproportionate effort (Art. 19 DSGVO).
You have the right to be informed by the LMU about such recipients.
IV. 6 Right to data portability
Regarding the demands of Art. 21 DSGVO you have the right to receive the personal data concerning you which you provided to the LMU, in a structured, commonly used and machine-readable format. In addition, you have the right to transfer this data to one or another responsible officer without hindrance by the LMU, provided
- the processing is based on consent pursuant to Art. 6 para. 1 DSGVO or Art. 9 para. 2 DSGVO or on a contract pursuant to Article 6 para. 1 (b) DSGVO; and
- the processing is carried out by automated means.
IV. 7 Right to object
You have the right to object, on grounds relating to your particular situation, at any time to processing of personal data concerning you which is based on Article 6 para.1 (e) or (f) DSGVO.In such cases, the LMU shall no longer process the personal data concerning you unless the LMU can demonstrate compelling legitimate grounds for the processing which override your interests, rights and freedoms or for the establishment, exercise or defense of legal claims.In the context of the use of information company services, and notwithstanding Directive 2002/58/EC, you are entitled to exercise your right to object by using automated means, in which technical specifications are applied.
In the case of processing of your personal data for scientific or historical research purposes and for statistical purposes pursuant to Art. 89 para. 1 DSGVO, you have the right to object to this data processing for reasons relating to your particular situation.Your right to objection may be restricted if it is likely that the completion of the research or statistical work will be made impossible or seriously hampered, and the restriction is necessary to complete the research or statistical work (Art. 25 BayDSG).
IV. 8 Right to revoke consent to data processing
You have the right to revoke your consent to data processing with future effect; however, this revocation shall not affect the legitimacy of the data processing already occurred based on your consent given until the time of revocation. This revocation must always be submitted to the agency within the LMU which has received the consent.
IV. 9 Right to lodge a complaint with an Oversight Authority
Without prejudice to any other administrative or judicial remedy, you have the right to lodge a complaint with a data protection oversight authority, in particular in the Member State of your habitual residence, place of work or place of the alleged infringement if you consider that the processing of personal data relating to you infringes the DSGVO. In the case of the LMU the directly cognizant data protection oversight authority is the Bavarian State Officer for Data Protection ( https://www.datenschutz-bayern.de) (external link); The supervisory authority with which the complaint has been lodged shall inform the complainant on the progress and the outcome of the complaint including the possibility of a judicial remedy pursuant to Art. 78 DSGVO.If you believe that the processing of your personal data is in violation of the DSGVO, then we request that you first turn to the officer responsible for the content of the particular internet page, who is named in the copyright statement, and/or to the official data protection officer at the LMU, since this will allow a rapid examination or remedy, if necessary, of your concerns. It is our goal and responsibility to examine all arriving questions of data protection immediately and to solve potential problems under data protection law.
V. Applicability of the General Data Protection Policy and Scope of the Supplemental Data Protection Policy of the Person Responsible for the Content of the Internet Page
The general data protection policy applies to those internet pages of the LMU for which the LMU bears responsibility. A supplemental data protection policy may also apply to a particular internet page of the LMU, provided the person responsible for the content of the internet page is performing additional processing of personal data and gives notice of such processing. This applies in particular when specific services are offered by individual departments. The supplemental data protection policy can expand, but not replace, the general data protection policy. The general data protection policy is a part of any supplemental data protection policy.
VI. Status, Revisions and Applicability of the LMU General Data Protection Policy
This general data protection policy was created on 03/2019. We reserve the right to update this data protection policy on a regular basis in order to take proper account of current legal requirements and technical changes, and also to implement our services and offers in compliance with data protection. The most recent version of this policy applies to your visit to an LMU web page.