DataFlow - Release Update - DataFlow developer discussion

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion DataFlow - Release Update
Received-SPF: neutral (google.com: 74.125.82.45 is neither permitted nor denied by best guess record for domain of stepha...@criticalec.com) client-ip=74.125.82.45;
MIME-Version: 1.0
Date: Tue, 24 Apr 2012 17:22:34 +0100
Message-ID: <CALftN-u37NcezBNY_uGhx7u6zMybpj=fgo2_A4GvCVMJ-yq...@mail.gmail.com>
Subject: DataFlow - Release Update
From: Stephanie Taylor <stepha...@criticalec.com>
To: dataflow-devel <dataflow-devel@googlegroups.com>
Content-Type: multipart/alternative; boundary=f46d043be2728c2c1804be6f294b

--f46d043be2728c2c1804be6f294b
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Further to my previous email, Richard is working with Anusha and Bhavana to
resolve the current issues.
We'll update everyone tomorrow afternoon.

Here is more info from Richard on the specific issues -

Hi Folks,

The error is quite peculiar, we are having some trouble pinning it
down and replicating.  Status at the moment

1/ I found a minor bug in the client which - if it isn't causing
problems now - would cause problems in the future.  This is now fixed,
and committed to the new github repo for the python client:

https://github.com/swordapp/python-client-sword2

2/ We are finding intermittent and not easily reproducible XML parsing
errors in databank.  This is causing databank to return a 500 to
deposit requests, which is likely the real cause of the problem

3/ DataStage is not attempting to auto-discover service documents;
this has no bearing on the deposit error, but it's unclear to me just
yet why this is.  Service document URLs must - for the time being - be
entered manually into the repository configuration

4/ DataStage does not have a mechanism for selecting deposit
collection, which is the reason we are not seeing deposits come
through to the sandbox - they are, in fact, going through to the first
collection in the databank service document, which is "demo"; see:

http://databank-vm1.oerc.ox.ac.uk/demo


So, where next?  I have to try and figure out why databank is giving
us 500 errors, which I can only do with a current databank install.
Since I'm still running the swordification branch, I need to put a bit
of time into upgrading; hopefully this will be quick and simple, but
if there are large changes that I need to take into account this might
take a bit longer.  Once i have that up, I have to try to reproduce
the error and then debug it.  Assuming it is repeatable, I hope that
I'll be able to get it fixed relatively rapidly.

Meanwhile, I also want to try to connect DataStage to my testing sword
server, to make sure that there are no other issues at that end.

I'd anticipate that this work will take at least all of tomorrow; I'll
update you tomorrow afternoon on state of play and try to estimate
when I can get it fixed up.

Cheers,

Richard

-- 
Stephanie Taylor
Director
Critical Eye Communications Limited
Registered Office:
113 Dye House Lane
New Mills
High Peak
SK22 4BA
UK

M: +44 (0)7745 123705
E: stepha...@criticalec.com

W: http://www.criticalec.com

Registered as a Company in England & Wales.
Company Number: 5871413

--f46d043be2728c2c1804be6f294b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<div><br></div><div>Further to my previous email, Richard is working wit=
h Anusha and Bhavana to resolve the current issues.</div><div>We&#39;ll upd=
ate everyone tomorrow afternoon.</div><div><br></div><div>Here is more info=
 from Richard on the specific issues -=A0</div>
<div><br></div><div><span style>Hi Folks,</span></div><br style><span style=
>The error is quite peculiar, we are having some trouble pinning it</span><=
br style><span style>down and replicating. =A0Status at the moment</span><b=
r style>
<br style><span style>1/ I found a minor bug in the client which - if it is=
n&#39;t causing</span><br style><span style>problems now - would cause prob=
lems in the future. =A0This is now fixed,</span><br style><span style>and c=
ommitted to the new github repo for the python client:</span><br style>
<br style><a href=3D"https://github.com/swordapp/python-client-sword2" targ=
et=3D"_blank" style>https://github.com/swordapp/python-client-sword2</a><br=
 style><br style><span style>2/ We are finding intermittent and not easily =
reproducible XML parsing</span><br style>
<span style>errors in databank. =A0This is causing databank to return a 500=
 to</span><br style><span style>deposit requests, which is likely the real =
cause of the problem</span><br style><br style><span style>3/ DataStage is =
not attempting to auto-discover service documents;</span><br style>
<span style>this has no bearing on the deposit error, but it&#39;s unclear =
to me just</span><br style><span style>yet why this is. =A0Service document=
 URLs must - for the time being - be</span><br style><span style>entered ma=
nually into the repository configuration</span><br style>
<br style><span style>4/ DataStage does not have a mechanism for selecting =
deposit</span><br style><span style>collection, which is the reason we are =
not seeing deposits come</span><br style><span style>through to the sandbox=
 - they are, in fact, going through to the first</span><br style>
<span style>collection in the databank service document, which is &quot;dem=
o&quot;; see:</span><br style><br style><a href=3D"http://databank-vm1.oerc=
.ox.ac.uk/demo" target=3D"_blank" style>http://databank-vm1.oerc.ox.ac.uk/d=
emo</a><br style>
<br style><br style><span style>So, where next? =A0I have to try and figure=
 out why databank is giving</span><br style><span style>us 500 errors, whic=
h I can only do with a current databank install.</span><br style><span styl=
e>Since I&#39;m still running the swordification branch, I need to put a bi=
t</span><br style>
<span style>of time into upgrading; hopefully this will be quick and simple=
, but</span><br style><span style>if there are large changes that I need to=
 take into account this might</span><br style><span style>take a bit longer=
. =A0Once i have that up, I have to try to reproduce</span><br style>
<span style>the error and then debug it. =A0Assuming it is repeatable, I ho=
pe that</span><br style><span style>I&#39;ll be able to get it fixed relati=
vely rapidly.</span><br style><br style><span style>Meanwhile, I also want =
to try to connect DataStage to my testing sword</span><br style>
<span style>server, to make sure that there are no other issues at that end=
.</span><br style><br style><span style>I&#39;d anticipate that this work w=
ill take at least all of tomorrow; I&#39;ll</span><br style><span style>upd=
ate you tomorrow afternoon on state of play and try to estimate</span><br s=
tyle>
<span style>when I can get it fixed up.</span><br style><br style><span sty=
le>Cheers,</span><br style><br style><span style>Richard</span><div><div><b=
r></div>-- <br>Stephanie Taylor<br>Director<br>Critical Eye Communications =
Limited<br>
Registered Office:<br>113 Dye House Lane<br>New Mills<br>High Peak<br>SK22 =
4BA<br>UK<br>=A0<br>M: +44 (0)7745 123705<br>E: <a href=3D"mailto:stephanie=
@criticalec.com" target=3D"_blank">stepha...@criticalec.com</a><br>=A0<br>W=
: <a href=3D"http://www.criticalec.com" target=3D"_blank">http://www.critic=
alec.com</a><br>
=A0<br>Registered as a Company in England &amp; Wales.<br>Company Number: 5=
871413<br><br>
</div>

--f46d043be2728c2c1804be6f294b--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
