[Ssc-dev] Getting to "round trip"

[Harlo Holmes]

In preparation for inserting 3rd party repositories between the mobile app
and the server, I've reorganized the intake process (and it's on a
brand-new server!)  Here's a quick description of the workflow:

1) user takes a pic/video and it goes automatically to the repository
linked to the organization the media's destined for (GlobalLeaks? Deaddrop?
 Drive?  Dropbox?)
2) Server pulls down new media regularly (10 minute intervals for now, we
might investigate triggers for automatic pull-down) where it is...
3) processed using Svetlana's J3M Parser and...
4) cataloged as a derivative according to Barbara's workflow

I started with Google Drive, as I'm already very familiar with its
server-side API for manipulating shared assets.  As we become familiar with
other platforms, we can write classes extending the base
"Server-pull-stuff-down-from-repo" class.

I've been using Doxygen to document as I go along, that way there is a lot
more transparency in our code. (It's ugly, I'm truly sorry, but it's
important for me to do so as to have better communication with the rest of
the team.)

parked here: http://ec2-54-235-36-217.compute-1.amazonaws.com
lacking any "bells and whistles" like authentication, ssl, etc. just so I
could get the basics up and running.

I'll be updating the mobile app to handle this new workflow automatically
over the next few days.  I do have some thinking to do, however, about how
this is managed.  Any input welcome.

++++++++++++++++++++++++++
Research Fellow, Head of Metadata
The Guardian Project <https://guardianproject.info>

pgp: 0xA4469630
twitter: @harlo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mayfirst.org/pipermail/ssc-dev/attachments/20130627/46ff56df/attachment.html>