[ome-devel] OMERO.forms

[Douglas Russell]

Hey,

I'm working on OMERO.forms and it's getting to the point where the approach
for data storage I have taken (Using map annotations) is beginning to look
too messy for comfort. I'm wondering if you have any suggestions for what
the best way of doing this might be without adding a difficult to
install/maintain component (i.e. a database) to OMERO.forms.

This is what I want to store:

   - Form
      - ID - Globally unique name
      - Owner - UID of creator
      - Groups - list of GIDs the form is available to
      - Types - Object types for which this form is valid (e.g. Dataset)
   - FormVersion
      - Version - Version
      - Timestamp - Creation time+date
      - Schema - The JSON string encoded form schema
      - UISchema - The JSON string encoded form UI schema
   - FormData
      - formID - The form used to enter this data
      - formVersion - The form version used to enter this data
      - data - The actual JSON string encoded data
      - objectType - The object type for which this data was entered (e.g.
      Dataset)
      - objectId = The object ID for which this data was entered
      - Timestamp - Creation time+date
      - User - UID of user who submitted form

This is a pretty trivial problem if I could use a relational database and I
would get transactions and data integrity. Right now I am trying to
shoehorn this into Map Annotations attached to a special privileged user
who the OMERO.forms web plugin sudos as, but it is getting increasingly
difficult to do this in a sane way. Updates especially are horrible.

As this is a web extension, I also wanted to keep the install/update
procedure as simple as possible. Adding the use of a local database as a
prerequisite did not seem reasonable.

Any ideas would be most welcome.

Cheers,

Douglas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openmicroscopy.org.uk/pipermail/ome-devel/attachments/20161019/1de1cb1c/attachment.html>