Hi Clement,
On 27 Aug 2018, at 16:44, Clément Aubin <aubincleme@gmail.com> wrote:
Hi,
On 08/27/2018 04:40 PM, Anca Luca wrote:
Hello all,
I guess we'd be going for application-xcopy . Can you please create the repo? (for now, I think only repo is needed, not yet jira) Thanks a lot!
Here it is : https://github.com/xwiki-contrib/application-xcopy
Thanks. However you need to follow: http://contrib.xwiki.org/xwiki/bin/view/Main/WebHome#HForXWikiAdmins I’ll let you fix it. I’ll create the jira project. Thanks -Vincent
Thanks, Clément
@Vincent: it's not coded with filter stream, is plain XWiki Document API, coded as an async job (which can be launched from a regular script).
Thanks, Anca
On Tue, Aug 21, 2018 at 4:49 PM Ecaterina Moraru (Valica) <valicac@gmail.com> wrote:
For me it would be "Multipage Copy Application", application-multipagecopy, similar to what we have for the Multipage Export Application.
Thanks, Caty
On Mon, Aug 20, 2018 at 11:58 PM Clément Aubin <aubincleme@gmail.com> wrote:
Hi Anca and Stéphane, hi all,
Thanks for sharing that piece of code ; this opens a ton of possiblities and use cases for other XWiki extensions working between wikis!
Regarding the naming of the application itself, application-wikicopy looks nice as it shows a bit what the application does, you could also consider application-xcopy as you are kind of eXtending the copy function of the wiki (also it looks a bit sexier than wikicopy IMO :) ).
Thanks, Clément
On 08/20/2018 04:39 PM, Anca Luca wrote:
Hello XWiki devs,
slauriere and I have worked on an extension that copies pages from one wiki (based on a HQL query selecting them) to another wiki, allowing to exclude some class properties from objects in those pages, if the objects are present. It's coded as an async job, it can be manually triggered or scheduled with a scheduler job.
We used it to implement some publication scenario, where contributors work on a set of documents on a subwiki and then these documents, if validated, get copied (published) to another subwiki periodically. The validation is based on the custom structure of those documents, using the generic feature of this extension that allows to select documents to be published based on a query. Otherwise there's nothing else related to publication in the code of the application itself.
We'd like to publish this application on contrib, so can we please have a repo for it?
However, we have some trouble choosing its name. The name that we used so far is "publication application" but we think it might be misleading esp. because of the similarity with publication workflow with which it has nothing to do.
So, if you have an idea for a name that would correctly illustrate this work (and its future enhancements), please help us choose its name and create the repo.
Thanks, Anca