Thanks for the information Alexandre and Alain. I am interested in coding this and will take a look at the work that has been done in the sandbox while waiting for your instructions on how to best proceed. My use case is wanting to import and export data in a storage agnostic way. I would like for this import and export to be "complete" in the sense that all available data can be moved from one server to another without loss of data (including all document versions) or functionality. This would also allow data to be converted into Nuxeo XML formats for migration. My first thought was that core-io and the shell would be a good place to start but I am open to other approaches, David
On Wed, Mar 25, 2009 at 2:45 AM, Alexandre Russel <[email protected]> wrote: > Hi David, > > >> Does anyone know how to modify the export mechanism so that relation and >> other data is exported inside the document folder as XML files as described >> in 27.1 of the nuxeo 5.2 book? >> http://doc.nuxeo.org/5.2/books/nuxeo-book/html/nuxeo-core-io.html >> >> It states "Optionally each service in nuxeo that store persistent data >> related to documents like the workflow, relation or annotation services may >> also export their own data inside the document folder as XML files." but I >> am unsure how to enable the option. >> > > - This is not an option, just something a service might do. I am not aware > of any services doing it. > - For the relation and annotation, they rely on the Relation service and > RDF graph to store their data. You could get the information related to the > document you are exporting and output it as XML easily > - For the workflow, I can't think of any use case that would need this > unless you get the all workflows information. You are interested to know if > there are tasks or workflows related to that document, but just the task id > or workflow id is useless if you don't know what they mean. So you would > then need the process instance information and the process definition. It > would be easier to just duplicate the JBPM tables from the database. If you > have a use case that might need workflow information without the whole jbpm > database, please let me know. > > >> >> I am willing to code and contribute if someone can point me in the right >> direction. >> > > If you're willing to code any of this (relations or workflow), let me know > I will create a JIRA with some pointer on how you could do it. > > alex > >
_______________________________________________ ECM mailing list [email protected] http://lists.nuxeo.com/mailman/listinfo/ecm To unsubscribe, go to http://lists.nuxeo.com/mailman/options/ecm
