As of December 9th, 2013 RefWorks users will no longer be required to enter a group code when logging in to their RefWorks account(s) off-campus or outside of their institutional IP range.  This improvement comes at the request of numerous RefWorks users and administrators and serves to simplify the RefWorks login process.  There are several cases where the group code will still be needed, either temporarily or permanently:

Logging In to Your Account 

If you are a current RefWorks user, simply log in to your RefWorks account as you have done in the past. The removal of the group code will not affect how you normally log in to your account.

If your institution uses Shibboleth or Athens there will be no changes when logging in to RefWorks.

New users that do not yet have a RefWorks account must be on-campus (or within a registered IP range for your Institution) or accessing RefWorks through proxy server when initially creating an account. This is so RefWorks can attach the user to a subscription.  Once the new user has set up their account they will be able to log in from any location, with or without proxy authentication, using only the login name and password.

Logging in to Write-N-Cite

The RefWorks development team will be removing the need for the group code when logging in to WNC 4 in an upcoming release.  Until then, users will log in with WNC4 using the current method, either group code/login name/password or with the authentication code.  Use the group code, login name and password or the login code provided after logging into RefWorks on the WNC login page.

WNC III users will continue logging in with their group code/login name/password or via proxy configuration if off-campus.  We will not be removing the group code requirement from the WNC III login page. 

Logging in to the RefWorks Administrator Tool

The group code is still required when accessing the RefWorks Administrator Tool.

There is no need to update your proxy configuration at this time.

Documentation will be updated and delivered to the production servers when the group code change occurs on December 9th.

A similar plan to remove the group code for the RefWorks servers located at University of Toronto is underway. We will keep those users updated; however, as of now this change will not affect how they log in to RefWorks.

Frequently Asked Questions 

If no group code is required, what happens if the user goes directly to RefWorks while off campus to log in, and their user name is the same as that of another account at another institution?

  • There are no longer any duplicate account login names. This is one reason that this upgrade took a long time to release; we needed to give all our users time to change their login names to something unique. 

Will the group code still be required for mobile access? 

  • The group code is not required for mobile access at this time.    

Many of our students are online only, and many are located in another state. How will they be able to set up a RefWorks account without the group code?  

  • If for some reason RefWorks cannot identify new users that are creating an account, the user will be asked to provide a Group Code just as RefWorks does today.      

We have several alumni, with alumni accounts, that do not have on campus/or proxy server access. We had them set up accounts by going directly to the Refworks site (bypassing the proxy server) and using the group code. How will this change affect them?

  • See above. In these cases a group code will still be needed.  

How will sites that have deployed the auto log in API be affected?

  • There are no changes to the sites that have deployed the RefWorks API’s.  

What about the many RefWorks subscriptions that go to another server in Canada?

We are working with the Scholars Portal Team at this time on deploying the group code changes. Scholars Portal RefWorks sites can look forward to an email from the team as soon as we solidify the deployment. 

Views: 2504

Comments are closed for this blog post

Events

Videos

  • Add Videos
  • View All

Forum

WriteNCite for 2016 - Inser/Edit Citation does not work 1 Reply

Several RW users are reporting troubles with Write N Cite. They have Word 2016, Windows NT Pro, and installed WnC version 4.5.1682 on it. They can see the RefWorks tab in the ribbon and click on the…Continue

Tags: 2016, Word, Write-N-Cite

Started by Jana Machonska in RefWorks. Last reply by Jana Machonska Sep 12.

Suggestion about de-duplicate feature 2 Replies

After running the duplicate checker,  items that result are check-marked by default.In my view, it would be better that none of them are check-marked by default. Then the user can check-mark just the…Continue

Started by Brian Simboli in RefWorks. Last reply by Brian Simboli Aug 30.

Refworks and EZProxy 2 Replies

HelloWe currently support both the *new* Refworks and the *legacy Refworks*.  Both of these platforms are proxied.   Whenever we try and export references from a database, however, only the…Continue

Started by Erin Rushton in RefWorks. Last reply by RefWorks Community Aug 27.

Thesis reference type in Citation Style Editor 2 Replies

I would like to add a ‘degree type’ (or some equivalent) field to the Thesis reference type, under the category of Bibliography. However, it is not listed as an available field in the Citation Style…Continue

Started by Robert Brown in RefWorks. Last reply by Robert Brown Aug 22.

© 2018   Created by RefWorks Team.   Powered by

Badges  |  Report an Issue  |  Terms of Service