<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">I did a carefully controlled test of a "virgin" (never touched RefWorks before in any version) <a href="http://upei.ca">upei.ca</a> email account completely off campus with no proxying, and I can report:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">1. there was no problem at all with either creating or using the account without any proxy involvement</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">2. I cannot reproduce the edit error when using that account off campus with no proxy involvement</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">I can't imagine what is going on between RefWorks and ezproxy that could interfere with editing, and if anyone from OCLC or RefWorks is reading this, I hope they talk to each other to solve it, but I'm now pretty sure that removing proxying from anything to do with NR is the solution.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Unfortunately, I don't know yet how to get EBSCOhost/EDS to NOT proxy the Export process when the EBSCO session itself is proxied, but I have opened a support ticket about that. Haven't tested any other platforms' "export to RefWorks" yet, e.g. Proquest, Ovid, others to see if they all leave patrons proxied. If they all do, we're going to need to get this fixed by OCLC/RefWorks rather than every platform that exports directly to RefWorks.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Melissa</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 28, 2016 at 3:50 PM, Christopher Gross <span dir="ltr"><<a href="mailto:chrisg@gwu.edu" target="_blank">chrisg@gwu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Interesting! We've had three or four users report that same error message when editing a reference, or adding a new reference manually. When I reported the problem to RefWorks support, they seemed baffled too. It never occurred to me to ask if the users had created new accounts from scratch or migrated from the old RefWorks, but now I think I'll go back and check with them.... If your proxy idea solves the problem, please post to the list! Thanks,<br><br></div>Chris<span class="HOEnZb"><font color="#888888"><br><br>Christopher Gross<br>Electronic Resources Specialist<br>Gelman Library<br>George Washington University<br><a href="mailto:chrisg@gwu.edu" target="_blank">chrisg@gwu.edu</a><br><a href="tel:202-994-3264" value="+12029943264" target="_blank">202-994-3264</a><br><br></font></span></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On Fri, Oct 28, 2016 at 10:30 AM, Melissa Belvadi <span dir="ltr"><<a href="mailto:mbelvadi@upei.ca" target="_blank">mbelvadi@upei.ca</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Hi, all. We think we've isolated the problem to the fact that we were running our New RefWorks links through ezproxy. NR doesn't really need it, but since the legacy one did, we just got used to having our Refworks-related links proxied. We're going to remove that and see if the problem goes away.</div><span class="m_2433376740352158756HOEnZb"><font color="#888888"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Melissa</div></font></span></div><div class="m_2433376740352158756HOEnZb"><div class="m_2433376740352158756h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 27, 2016 at 10:44 AM, Melissa Belvadi <span dir="ltr"><<a href="mailto:mbelvadi@upei.ca" target="_blank">mbelvadi@upei.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Hi, all.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">This is for those who have started to use the New RefWorks, and relates to accounts that are created entirely as NR accounts, not migrated from old accounts.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">It suddenly struck me that every single account I've helped new students create, every one, starts off with the function to edit records broken, and they have to email RefWorks support to get it fixed.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">I am wondering if others are seeing this, or if there could be something wrong with UPEI's institutional account that could be causing this corruption in new accounts.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Here is the precise workflow:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Student comes to appointment with me to set up and learn how to use RefWorks for the first time.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">We do everything on their own laptop, because I plan to include Write-n-Cite installation as part of the session. We're on the campus student wireless network, so unproxied.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">We start with creating the new account. There are no errors in that process. </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">We leave that tab open.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">We open a new tab to our Ebsco Discovery Service and do a sample search to select some records.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">We use EDS's function to export a bunch of selected records to the New RefWorks.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">This creates a new open RefWorks tab even though we had left the original one open, so I close the original tab so we can keep working in the new tab.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">I explain about APA and capitalization, and we immediately click on one of the citations that needs the article title capitalization fixed. We click on the little pencil at the far right to edit it.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">This opens the editing sidebar on the right. <br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">We fix the capitalization in the title, then click on Save at the top of that sidebar.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">We get at the top centre of the window the message in a red and white banner:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><b>"Sorry something went wrong. Please try again."</b></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Trying again does absolutely no good. We are unable to save the editing changes.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">We send Support an email. </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">I don't hear back from the student later, so I don't know if that gets the problem resolved or not.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">I haven't had a single new student that I have NOT had this problem with.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Are others seeing this problem?</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Has anyone found out if there's something that can be done to avoid it or solve it without involving RefWorks Support?</div><span class="m_2433376740352158756m_-3749005334392894441HOEnZb"><font color="#888888"><div><br></div>-- <br><div class="m_2433376740352158756m_-3749005334392894441m_430098270401490143gmail_signature"><div dir="ltr"><div>Melissa Belvadi</div><div>Collections Librarian</div><div>University of Prince Edward Island</div><div><a href="mailto:mbelvadi@upei.ca" target="_blank">mbelvadi@upei.ca</a> <a href="tel:902-566-0581" value="+19025660581" target="_blank">902-566-0581</a></div><div><br></div><div><br></div></div></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="m_2433376740352158756m_-3749005334392894441gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Melissa Belvadi</div><div>Collections Librarian</div><div>University of Prince Edward Island</div><div><a href="mailto:mbelvadi@upei.ca" target="_blank">mbelvadi@upei.ca</a> <a href="tel:902-566-0581" value="+19025660581" target="_blank">902-566-0581</a></div><div><br></div><div><br></div></div></div>
</div>
</div></div><br></div></div><span class="">______________________________<wbr>_________________<br>
Eril-l mailing list<br>
<a href="mailto:Eril-l@lists.eril-l.org" target="_blank">Eril-l@lists.eril-l.org</a><br>
<a href="http://lists.eril-l.org/listinfo.cgi/eril-l-eril-l.org" rel="noreferrer" target="_blank">http://lists.eril-l.org/listin<wbr>fo.cgi/eril-l-eril-l.org</a><br>
<br></span></blockquote></div><br></div>
<br>______________________________<wbr>_________________<br>
Eril-l mailing list<br>
<a href="mailto:Eril-l@lists.eril-l.org">Eril-l@lists.eril-l.org</a><br>
<a href="http://lists.eril-l.org/listinfo.cgi/eril-l-eril-l.org" rel="noreferrer" target="_blank">http://lists.eril-l.org/<wbr>listinfo.cgi/eril-l-eril-l.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Melissa Belvadi</div><div>Collections Librarian</div><div>University of Prince Edward Island</div><div><a href="mailto:mbelvadi@upei.ca" target="_blank">mbelvadi@upei.ca</a> 902-566-0581</div><div><br></div><div><br></div></div></div>
</div>