Skip to main content

Save Your Research Time with FDU Library Access Proxy


In academic writing courses at FDU, you may (or are very likely to) be required to do research for articles and journals for your papers. FDU has support for many websites like SAGE and JSTOR where you can search for articles and view them with your FDU NetID so that you do not have to make your own accounts and pay for subscription fees.

Recently, I have noticed that many students, including me, use Google Scholar to search for research articles and journals, because Google Scholar can list various papers from different sources, hence better variety of content. However, the problem is that FDU does not have support for Google Scholar, meaning students cannot use FDU NetID to log into Google Scholar. It is a drawback, though, as I have noticed, many results from Google Scholar come from sites like JSTOR and SAGE, which are supported by FDU. Here, the inner problem is that students have to use FDU NetID to log into each site at least once after clicking the respective links on Google Scholar, and it is a time-consuming process because students have to enter their credentials again and again for each link from the result list from Google Scholar if the links have been opened continuously and students have not logged in before or the links are different from each other. It will be even worse in the case where students cannot sign in directly through the sites, instead, they have to go to FDU library list to search for the sites and log in, and then come back to the links and reload the links' pages in order to continue their work.
Now I will show you a way to eliminate this whole time-consuming thing while doing research on Google Scholar :)

How?

Go to this link and do your research. That's it!





More interesting things to come if I have free time :D

Comments

Popular posts from this blog

A Way To Deal With Relative Paths in PHP include();

In Assignment 02 (INFO-2106 - Yin M.), we are required to use PHP include() function to grab PHP files from different directories (i.e. __includes ) to our main pages. The problem is that, for many (not all) people that I can see, when we use Adobe Dreamweaver CS6 to work with our files (i.e. header.php , footer.php , menu.php ) in __includes , relative paths are inserted with the root of the paths being in the directory in which such files are located, and when these files are grabbed to pages outside of their directories, the paths stay unchanged, which causes an error where necessary files cannot be located, and therefore our main pages do not display correctly (i.e. the way we want). However, I have recently found a PHP trick that can resolve the problem. Define a Site Root The reason why relative paths break is because they are relative, meaning that these paths start from the directory of the file in which those files are located or to which those files belong (in code...