DataFlow - Release Update
Stephanie Taylor
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: step...@criticalec.com
W: http://www.criticalec.com
Registered as a Company in England & Wales.
Company Number: 5871413
Richard Jones
A small update this morning:
1/ I have fixed a minor issue in the python client which would have
prevented datastage from working either way, and have now successfully
deposited from datastage into my local Simple Sword Server. This
bodes well, as it means I can isolate the cause of the problem
somewhere in databank. Since databank also uses the Simple Sword
Server to provide its sword support, that means there are fewer places
in databank to look for the problem. Note that all changes to the
python client are now on github:
https://github.com/swordapp/python-client-sword2
2/ I'm having problems getting databank to install and run at my end,
so not currently able to give any estimates as to time to fix (see
previous email)
Efforts are currently stalled while I try to resolve the install and
run problems that I'm having with databank. If anyone has any
insights as to the errors in my previous email, that would be very
useful.
Cheers,
Richard
> --
> Post to: dataflo...@googlegroups.com
> Unsubscribe: dataflow-deve...@googlegroups.com
> Web: http://www.dataflow.ox.ac.uk/
> http://groups.google.com/group/dataflow-devel?hl=en
> https://github.com/dataflow
--
Richard Jones,
Founder, Cottage Labs
t: @richard_d_jones, @cottagelabs
w: http://cottagelabs.com
Richard Jones
I spent this morning getting databank installed with Anusha's
assistance. I have now got a datastage and a databank installation on
my desktop, and have successfully connected them together with sword.
The outline of the changes that I have made to make this work are:
1/ Fixed a bug in the python client
2/ specified a specific version of lxml to be used by the server environment
Actions required for datastage: to deploy the installation with the
updated client code available at
https://github.com/swordapp/python-client-sword2
Action required for databank: Our current candidate for the problems
caused were incorrect versions of some of the dependencies; Anusha is
now looking into upgrading to lxml 2.3.4 and the server versions of
things. Once deployed on these latest versions I hope that the issues
will be resolved.
Anusha - can you let us/me know how you get on.
Cheers,
Richard