Orbeon Forms community mailing list

building a hierarchy of xform instances

Classic

List

Threaded

3 messages Options

building a hierarchy of xform instances

I'm revisiting orbeon after a long break .. so I have to catch up on basics.

My question: Are there any orbeon tutorials for building a hierarchical tree of xform instances?
(I've searched the forum and wiki).

Typical attributes of tree structure:-

- about 8-10 or more levels of hierarchy of xform instances (tree branch node)

- about 4-6 child nodes per tree branch node

- various attributes and raters to be edited in each xform instance (there will be hundreds of tree nodes)

- multiple users contributing content to the tree structure (via Drupal not Liferay) as a wiki model

- each parent node in the view on click will navigate up to the next higher level in tree.

- each child node in the view on click will navigate down to the next lower level in tree.

...

The nearest orbeon example I've studied might be "bookcast in a hierarchy".
i.e. each top book in orbeon bookcast example would be a branch node in the tree
and beneath this parent node would be added child nodes.

I've read this ..

http://wiki.orbeon.com/forms/how-to/view/edit-hierarchy

Thanks.

Erik Bruchez

Re: building a hierarchy of xform instances

Administrator

DL,

I don't think there is such a thing as a hierarchy of XForms
instances. An XForms instance is an XML document.

Do you mean a hierarchy of XML documents, as you would find in the
eXist database for example?

-Erik

On Tue, Apr 17, 2012 at 1:25 PM, DL <[hidden email]> wrote:

> I'm revisiting orbeon after a long break .. so I have to catch up on basics.
>
> My question: Are there any orbeon tutorials for building a hierarchical tree
> of xform instances?
> (I've searched the forum and wiki).
>
> Typical attributes of tree structure:-
>
> - about 8-10 or more levels of hierarchy of xform instances (tree branch
> node)
>
> - about 4-6 child nodes per tree branch node
>
> - various attributes and raters to be edited in each xform instance (there
> will be hundreds of tree nodes)
>
> - multiple users contributing content to the tree structure (via Drupal not
> Liferay) as a wiki model
>
> - each parent node in the view on click will navigate up to the next higher
> level in tree.
>
> - each child node in the view on click will navigate down to the next lower
> level in tree.
>
> ...
>
> The nearest orbeon example I've studied might be /"bookcast in a
> hierarchy"/.
> i.e. each top book in orbeon bookcast example would be a branch node in the
> tree
> and beneath this parent node would be added child nodes.
>
> I've read this ..
>
> http://wiki.orbeon.com/forms/how-to/view/edit-hierarchy
>
> Thanks.
>
>
>
> --
> View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/building-a-hierarchy-of-xform-instances-tp4565908p4565908.html
> Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.
>
>
> --
> You receive this message as a subscriber of the [hidden email] mailing list.
> To unsubscribe: mailto:[hidden email]
> For general help: mailto:[hidden email]?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
>

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

Re: building a hierarchy of xform instances

Erik

You've confirmed the conclusion I had come to after thinking it through overnight.

I need to create the hierarchy of XML documents (hundreds of nodes .. one xform instance per node) in the eXist database .. and not in the orbeon view (as in the bookcast example).

The orbeon view will be a flat dataset (as in the bookcast example) showing in browser one branch node (parent node) and child nodes for one level. i.e. viewing a fragment of the hierarchy at any time.

I'll need to create a CRUD API to eXist. I can see the eXist REST interface in bookcast example.

However I prefer to use an external eXist database (which I have running on tomcat7 as separate webapp) instead of the integrated eXist DB in orbeon.

And .. as you have suggested in another threads .. variables (such as nodeID) can be in hidden fields.