Note: In my answer below I assumed that the contrib extension was generic and not related to the publication use case, and that anything specific to that use case was done elsewhere.
Thus I may be wrong if this assumption is not correct. Thanks -Vincent > On 20 Aug 2018, at 16:48, Vincent Massol <[email protected]> wrote: > > Hi Anca/Stephane, > >> On 20 Aug 2018, at 16:39, Anca Luca <[email protected]> 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. > > If I had to implement this, I would code it using the Filter Stream > Application framework (see > https://extensions.xwiki.org/xwiki/bin/view/Extension/Filter%20Module and > especially > https://extensions.xwiki.org/xwiki/bin/view/Extension/Filter%20XWiki%20Instance%20module#HExtendit) > as an input filter (since the output filter to copy to a different wiki > already exists). > > Is that how you did it? > >> 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. > > I agree it’s misleading and not a good name ;) > >> >> 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. > > Is the code in Java or is it done as wiki pages? > > Some suggestions: > > If in Java: > > * api-wikicopier > * api-wikicopy > > If in wiki pages: > > * application-wikicopier > * application-wikicopy > > If coded as filterstream input: > > * filter-instance-hql > * filter-instance-hql-input > > Thanks > -Vincent > > >> >> Thanks, >> Anca
