<div dir="ltr"><div class="gmail_extra"><div><div>Hi,</div></div><div><br></div><div>I've been trying out a few things with the ETL.</div><div><br></div><div>For the issue (2) that I posted previously, I found that I could fix this issue by restarting the server. When I ETLed the same file to the training node (<a href="https://training.eagle-i.net" target="_blank">https://training.eagle-i.net</a>) the location field was correctly populated. When I ETL to the VM (from the VM) I do not see the location. I've tested by carrying out the ETL for 14 services using a test core laboratory in the live Penn repository. I do not see the location on the VM, but I do see the location on the live Penn site. Is testing on the live repository ok?</div><div><br></div><div>Thanks,</div><div>Faith</div>
<br><div class="gmail_quote">On Tue, Sep 30, 2014 at 12:15 PM, Faith Coldren <span dir="ltr"><<a href="mailto:fcoldren@mail.med.upenn.edu" target="_blank">fcoldren@mail.med.upenn.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div><div>Hi,</div></div><div><br></div><div>I am testing ETL in v.3.0.4, and I ran into a couple of problems.</div><div><br></div><div>(1) After loading in services into the publish state, using -p PUBLISH flag, in institutional search results the location field (under Type) is left blank even though the services are loaded into the correct core.</div><div><br></div><div>(2) After running the deETLer, the deETLed resources still appear in the institutional search results.</div><div><br></div><div>Is there something I can do to fix these issues?</div><div><br></div><div>Thank you,</div><div>Faith</div>
</div>
</blockquote></div><br></div></div>