I read in display macro documentation that you can display a section?
But how do you specify a section in a document?
I would like to understand this using the wysywig editor and using wiki editor?
And what velocity code would give me a section header and a section body (without the header)?
The only thing I can think of is the heading levels in the wysywig editor, but a document that has a header (level 2) and some text below the header does not seem to have sections if i call
#set($menuSections = $menu1Document.getSections())
Hi,
I've installed the query helper:
http://extensions.xwiki.org/xwiki/bin/view/Extension/jQuery+Helpers
But it looks like the jquery.jquery is empty, contains no object of class javascriptextension?
Why would I need to load the jquerry into such a page, could I not just get it from:
links to the CDN-hosted copies of jQuery?
If this is possible; how do I do this?
If $xwiki.jsx.use('jQuery.jQuery', {'defer': false}) is used the script is always in the header of the html page?
But If I would like to load a script somewhere in the body, how do I do that, not use $xwiki.jsx.use?
Would I need to write it inside a html macro?
Gerritjan
Hello,
Does anyone know if it is possible to set parameters to li elements using
the (%%) syntax?
http://platform.xwiki.org/xwiki/bin/view/Main/XWikiSyntax#HParameters and
the examples do not mention li**, only ul/ol parametrization.
I tried this:
(% class="dir-tree" %)
> * ##/tmp##
> (% class="file" %)** ##file1.tmp##
> (% class="file" %)** ##file2.tmp##
>
It renders as a ul with the .dir-tree class, but the li are not
parametrized.
In fact they are not rendered as li, but as a <strong><span class="file">...
Is it a bug, or the expected result?
Thanks!
The XWiki development team is proud to announce the availability of XWiki Enterprise 4.3.
This release brings several improvements in Workspaces, Extension Manager, Distribution Wizard, the REST API, new field pickers (Date, User and Groups), improved translation registration and new experimental Solr search.
You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki43
Thanks
-The XWiki dev team
Hi.
I've created something similar to FAQ application: a simple class,
sheet, template and pages created from template.
The pages are including the sheet, also have an object of the class.
I don't understand why the default edit mode is 'inline form', i.e. when
I create a livetable with 'actions' column, than 'edit' button goes to
'inline form' edit mode.
If a wiki user does not have 'advanced mode' enabled - he can only edit
the form, not the page itself.
How to make 'wiki' or 'wysiwyg' edit mode as default for such pages?
TIA
R.
Hi,
I am proposing to use XWiki to provide context sensitive help for a cloud
application.
It is likely that our channel partners will require their own branding of
the product and supporting wiki,
Therefore, my question is: does Xwiki have the functionality to use
variables in the text?
e.g. Company Name: [ACME | HAL | DEA]
Thank You
*
*
*John Murphy **|* Technical Writer *|* Mobile: 0415324479 *|*
|Telephone: 02 8999 3170 *|*john.murphy(a)ipscape.com.au*|*
Hello!
I have my xwiki on xwiki farm and have 2 problems:
1. It is very complicated to administrate my xwiki without statistics
application. What can I do to get the ability to have this app?
2. The cyrillic names of applications are not supported and I can't to
create any application to use. I know that this problem is related with data
base encoding method! Is it a bug? Can I repair it?
Thank You!
--
View this message in context: http://xwiki.475771.n2.nabble.com/Cyrillic-font-at-myXwiki-tp7582521.html
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hello!
I have my xwiki on xwiki farm and have 2 problems:
1. It is very complicated to administrate my xwiki without statistics
application. What can I do to get the ability to have this app?
2. The cyrillic names of applications are not supported and I can't to
create any application to use. I know that this problem is related with data
base encoding method! Is it a bug? Can I repair it?
Thank You!
--
View this message in context: http://xwiki.475771.n2.nabble.com/Cyrillic-font-at-myXwiki-tp7582520.html
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hello,
I'm trying to validate if upgrade where annotations have been merged with comments was successful (3.5->4.1.3).
select * from xwikicomments;
returns me 0 records, even though I definitely have page where I have annotations and I as well see them as comments in the bottom of the page.
How can I check if annotations are where they should be?
Regards,
Roman
Hello everyone,
I've activated the statistics on my virtual xwikis, but when I access
the page XWiki/Stats I see the code, but not statistics, as this:
<% period = request.get("period") Calendar cal = Calendar.getInstance();
cal.setTime(new Date()); if (period==null) { period =
cal.get(Calendar.YEAR) * 100 + (cal.get(Calendar.MONTH)+1) }
jour = cal.get(Calendar.YEAR) * 10000 + (cal.get(Calendar.MONTH)+1) *
100 + (cal.get(Calendar.DAY_OF_MONTH)+1)
type = request.get("type") if (type==null) type = "view"
%>
In the xwiki.cfg, this is the section related to statistics:
xwiki.stats=1
xwiki.stats.default=1
xwiki.stats.class=com.xpn.xwiki.stats.impl.XWikiStatsServiceImpl
Any help?
Thanks!
Vito
--
Vitantonio Messa
+358 46 889 48 49 - vitantonio.messa(a)coss.fi
COSS - The Finnish Centre for Open Source Solutions
@ Technology Centre Hermia Ltd.
Hermiankatu 1, FIN-33720 Tampere, FINLAND
Hi!
I configured the xwiki syntax 2.1 as default syntax.
> core.defaultDocumentSyntax = xwiki/2.1
It works if I create a new space.
If I create a new page in an existing space it still use the xwiki/2.0
syntax.
Any hint what I'm doing wrong?
Best Regards,
H.-Dirk Schmitt
--
Signature H.-Dirk Schmitt
------------------------------------------------------------------------
*
H.-Dirk Schmitt <http://www.computer42.org>*
Dipl.Math.
eMail:/dirk.schmitt@computer42.org/
mobile:/+49 177 616 8564/
phone: /+49 2642 99 41 10/
fax: /+49 2642 99 41 15/
Kripper Str. 35, D-53489 Sinzig
pgp: http://www.computer42.org/~dirk/OpenPGP-fingerprint.html
<http://www.computer42.org/%7Edirk/OpenPGP-fingerprint.html>
Hello all,
I'm working with the last version of XE and i get the LDAP authentication on
my Active Directory Domain.
My problem is when i move a user to a different OU in the Active Directory,
the user can't login in Xwiki anymore...(Error : Wrong password).
Is there a way to configure the xwiki.cfg in order the authentication could
"browse" the all Active Directory to find the user and allow him to login ?
Thanks in advance.
--
View this message in context: http://n2.nabble.com/Xwiki-LDAP-Authentication-doesn%27t-work-when-you-move…
Sent from the XWiki- Users mailing list archive at Nabble.com.
We're getting error 401 trying to use the rss macro on XWiki to access a
RSS feed hosted on the same XWiki server through HTTP Basic Authentication.
Using this macro in a XWiki page:
{{rss feed="
http://user:password@myserver.com/xwiki/bin/view/Blog/CategoryRss?xpage=pla…"
content="true" image="false" count="2" /}}
We get this error:
Failed to execute the [rss] macro
org.xwiki.rendering.macro.MacroExecutionException: Error processing [
http://user:password@myserver.com/xwiki/bin/view/Blog/CategoryRss?xpage=pla…]
: Server returned HTTP response code: 401 for URL:
http://user:password@myserver.com/xwiki/bin/view/Blog/CategoryRss?xpage=pla…
at
org.xwiki.rendering.internal.macro.rss.DefaultRomeFeedFactory.createFeed(DefaultRomeFeedFactory.java:65)
at
org.xwiki.rendering.internal.macro.rss.RssMacro.execute(RssMacro.java:128)
at org.xwiki.rendering.internal.macro.rss.RssMacro.execute(RssMacro.java:61)
at
org.xwiki.rendering.internal.transformation.macro.MacroTransformation.transformOnce(MacroTransformation.java:188)
at
org.xwiki.rendering.internal.transformation.macro.MacroTransformation.transform(MacroTransformation.java:135)
at
org.xwiki.rendering.internal.transformation.DefaultTransformationManager.performTransformations(DefaultTransformationManager.java:84)
at
org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentDisplayer.java:250)
at
org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentDisplayer.java:124)
at
org.xwiki.display.internal.DocumentContentDisplayer.display(DocumentContentDisplayer.java:54)
at
org.xwiki.display.internal.DefaultDocumentDisplayer.display(DefaultDocumentDisplayer.java:80)
at
org.xwiki.display.internal.DefaultDocumentDisplayer.display(DefaultDocumentDisplayer.java:38)
at
org.xwiki.sheet.internal.SheetDocumentDisplayer.display(SheetDocumentDisplayer.java:113)
at
org.xwiki.sheet.internal.SheetDocumentDisplayer.display(SheetDocumentDisplayer.java:50)
at
org.xwiki.display.internal.ConfiguredDocumentDisplayer.display(ConfiguredDocumentDisplayer.java:67)
at
org.xwiki.display.internal.ConfiguredDocumentDisplayer.display(ConfiguredDocumentDisplayer.java:41)
at
com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:901)
at
com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:880)
at
com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:911)
at com.xpn.xwiki.api.Document.getRenderedContent(Document.java:603)
at sun.reflect.GeneratedMethodAccessor282.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:395)
at
org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:384)
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:173)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:280)
at
org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:567)
at
org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71)
at
org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342)
at
org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:106)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342)
at
org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:224)
at
org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:184)
at
com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:105)
at com.xpn.xwiki.XWiki.evaluateTemplate(XWiki.java:1765)
at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1705)
at com.xpn.xwiki.api.XWiki.parseTemplate(XWiki.java:854)
at sun.reflect.GeneratedMethodAccessor123.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:395)
at
org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:384)
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:173)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:280)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:369)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72)
at
org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:216)
at
org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:311)
at
org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:230)
at
org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:207)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72)
at
org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:87)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342)
at
org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:106)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342)
at
org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:224)
at
org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:184)
at
com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:105)
at com.xpn.xwiki.XWiki.evaluateTemplate(XWiki.java:1765)
at com.xpn.xwiki.web.Utils.parseTemplate(Utils.java:155)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:241)
at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:116)
at
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:538)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1352)
at com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:120)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1323)
at
org.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:144)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1323)
at
com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:66)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1323)
at
org.xwiki.container.servlet.filters.internal.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:208)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1323)
at
org.xwiki.container.servlet.filters.internal.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:111)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1323)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:476)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:517)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:937)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:406)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:871)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:247)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:110)
at org.eclipse.jetty.server.Server.handle(Server.java:346)
at
org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:589)
at
org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:1048)
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:601)
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:214)
at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:411)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:535)
at
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:40)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:529)
at java.lang.Thread.run(Thread.java:722)
Caused by: java.io.IOException: Server returned HTTP response code: 401 for
URL:
http://user:password@myserver.com/xwiki/bin/view/Blog/CategoryRss?xpage=pla…
at
sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1615)
at com.sun.syndication.io.XmlReader.<init>(XmlReader.java:237)
at
org.xwiki.rendering.internal.macro.rss.DefaultRomeFeedFactory.createFeed(DefaultRomeFeedFactory.java:60)
... 104 more
I can access the same feed URL using curl on the server XWiki is running:
root@server:~# curl -v "
http://user:password@myserver.com/xwiki/bin/view/Blog/CategoryRss?xpage=pla…
"
* About to connect() to myserver.com port 80 (#0)
* Trying 168.62.179.66... connected
* Server auth using Basic with user 'user'
> GET
/xwiki/bin/view/Blog/CategoryRss?xpage=plain&category=Blog.News&basicauth=1
HTTP/1.1
> Authorization: Basic ZmVlZHJlYWRlcjphc2xkZmprbzI5xxxxxxxx
> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0
OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: myserver.com
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: nginx
< Date: Tue, 20 Nov 2012 11:29:23 GMT
< Content-Type: application/rss+xml;charset=UTF-8
< Content-Length: 3411
< Connection: keep-alive
< Set-Cookie: JSESSIONID=dnmy5peu0w1n1ok4ywwxxxxxx;Path=/xwiki
< Expires: Tue, 20 Nov 2012 12:29:23 GMT
< Content-Language: en
< Pragma: no-cache
< Cache-Control: public
<
<?xml version="1.0" encoding="UTF-8" ?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="
http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel rdf:about="/xwiki/bin/view/Blog/News">
<title>News</title>
(content follows)
The same feed URL also works with curl from my laptop, over the Internet.
I appreciate any help.
Hi,
i have a problem with german Umlaute when creating a new Page. The Umlaute
are not displayed correctly, but when i rename the page, then its works
correctly and the Umlaute are displayed. This problem appears only after
creating the page.
There are any solutions known?
Thanks
Regards,
Silvio
--
View this message in context: http://xwiki.475771.n2.nabble.com/Problem-with-german-Umlaute-a-o-u-when-cr…
Sent from the XWiki- Users mailing list archive at Nabble.com.
Hello,
I'm testing installation of an extension with extension manager / extension
repository, on XE 4.3-milestone-2:
- deploy my extension (xar + deps) from maven to a local nexus
- import this extension into the extension repo in my xwiki
- try to install it with EM
I get a conflict:
Dependency [javax.jcr:jcr-2.0] is not compatible with core extension
[javax.jcr:jcr-1.0]
This dependency is a transitive dependency (runtime) of a mstor library
needed by my app. Currently, it is used in xwiki in version 1.0.
I first tried to add an <exclusion> block for it in my pom.xml, redeployed,
reimported, reinstalled, with same result.
I then added jcr 1.0 in a dependencyManagement section in order to override
version 2.0 brought by mstor, but again with same result.
BTW, additionally, the folder targeted by xwiki.data.dir remains empty ...
Seems a bit strange.
How can I solve this issue ?
Thanks,
Jeremie
Hi,
I know there have been discussions on collapsed panel headers
I've had user complaints about the 'complexity' of our website (based on XWiki).
After analysis of the complaints one of the reasons for perceived complexity were the panels
They distracted the focus from the content, because each panel (we use approx 4 on the left and 2 or 3 on the right) (www.cdlsworld.org)) contains links/information.
Sending screen shots of the site with collapsed panels was rated significantly 'easier'. The panel header is descriptive enough.
What is today's recommended strategy to have the panels collapsed by default (i would really like this to be a attribute when you define a panel; like a checkbox; default collapsed!)
We do not require user configuration here; the state of the panel does not have to be remembered per user session. We would rather have 'rules by context' If user has certain rights, if user is in certain space'
But this is a nice to have, not a must have; we would be fine if one single panel is always collapsed when entering a page. And for another panel that it is always open and can be collapsed!
Any recommendation would be highly appreciated...
My own thoughts are that this might be something for javascript; the script could collapse the panel...
Downside of javascript is that 'older' computers or users that have javascript disabled might not benefit, that would suggest a serverside setting of the CSS class ?
Gerritjan
I am just discovering XWiki and I am looking for some advice from more
experienced users on how to structure my wiki.
I am a data analyst at a hospital and would like to introduce a wiki into
our team. I feel XWiki is the best wiki engine for us to use because of the
WYSIWYG editor and the Office importer, which should help in the initial
adoption stage.
The aim of introducing a wiki would be to improve supporting documenting and
create more robust documentation on the following areas:
1. Definitions of measures - what it means, how it is calculated, what may
be excluded from this measure
2. Supporting user documentation to reports produced - how to navigate the
interactive reports, what the various graphs and charts represent
3. Document SQL databases/data warehouse - there are a whole host of
databases in the organisation that either no-one has no knowledge or one
person has knowledge of it. Documentation on the schemas, tables, views,
stored procedures, relationships etc.
4. Procedure information on how to produce reports - step by step on how to
produce a report extract. This documentation already exists in word
documents hosted in SharePoint libraries.
5. Technical documentation on how to produce reports - this would document
the inner workings DTS/SSIS packages or Microsoft Access databases that are
run as part of the procedure information.
Let me give you an example which may help you understand the situation
better.
There are various spreadsheet reports produced based on the number of weeks
patients have waited for treatment, referred to as 18 weeks, with numerous
measures used throughout.
The current documentation on how to produce these reports are split over
multiple word documents as the process is run in two stages on a Monday and
Thursday, both are very lengthy around 30 pages each. The documentation is a
step by step guide on how to produce the reports/extracts e.g. open this
file, copy and paste this, run this DTS package etc. To produce these
reports, another set of procedures need to be complete before as some of the
data produced by this process supports the 18 week process.
The entire process is based on a Microsoft Access database which an
ex-employee created and no-one knows anything about it's inner workings nor
is there any documentation on this database. Having looked at it briefly,
the database connects to an SQL server and uses data stored in some tables
which are produced by scheduled DTS packages - again which aren't
documented.
Thinking about how to logically store all this information within XWiki and
provide some clear structure, my thoughts were as follows:
Create virtual wikis which are based on the target audience/purpose
Create spaces for each of the subject areas/databases
Use tags to provide further categories, in particular for documenting
databases.
This would look something like this:
An XWiki for consumers of reports, this would contain documentation on
measures and supporting documentation on interpreting the various reports
produced. This wiki would be split into various spaces based on the subject
area, e.g. 18 Weeks, Inpatient, Outpatient.
An XWiki for procedural documentation on how to produce the various reports.
This would be split into various spaces based on the same subject areas as
the previous XWiki.
An XWiki for technical documentation on databases/DTS/SSIS packages. This
would be split into spaces for the various databases and would use tags to
distinguish between the different type of pages within the space e.g.
documentation on tables, views, stored procedures, functions.
Whilst the first two XWikis make sense and I don't see any issues with the
structure, it is the technical documentation part which I think may be
difficult to navigate. Perhaps the DTS/SSIS packages would need there own
XWiki as they are at a server level and not database level.
I am hopeful to hear your thoughts on the suggestions above.
Any help if greatly appreciated.
--
View this message in context: http://xwiki.475771.n2.nabble.com/Looking-for-advise-on-structuring-XWiki-t…
Sent from the XWiki- Users mailing list archive at Nabble.com.