Category: Interaction (with the outside World)

phpBB is a popular open source forum software.
Sometimes, a forum is not enough.
So, the data must be migrated from phpBB to Tiki forums...

If you want to help:
Please post links to similar scripts.
ex.: phpbb to invision board, etc
If/when we do a script, we should do for all major forums.
---
__From kerrnel22 on 11/20/07:__

I have almost completed an integrated TikiWiki forum migration tool for 1.9.8.x and 1.10. Initial release will be to migrate only Tiki forums from one Tiki install to another. However, hooks are in place, and the intention is there, to work on extending the migration tool to importing of phpBB2 (or any other forum software) into Tiki. If you would like more information, email tiki.kerrnel@kerris.com. I expect a general release of the forum migration tool (for Tiki forums only) into cvs of both branches for beta testing by December 1/07. If all goes well, I'll have something released for phpBB2 migration prior to Dec 31.

Tutos uses this one:
http://php-pdb.sourceforge.net/

http://prdownloads.sourceforge.net/tutos/palm-1.2.20050306.zip?download

The use of an outside mail-list system is not unusual.

I'm using [http://feedblitz.com|FeedBlitz.com] to get newsletters to users.

It would be nice to have the FeedBlitz system integrated with the Tiki registration module.

Here is what their Knowledge base says about integrating this kind of requirement.

I would like to suggest an enhancement to TikiWiki 8 to integrate with MantisBT. Specifically the desired outcome would be:

(1) A single sign-on. If you are logged into to TW, you are logged into Mantis and visa versa;
(2) A unified view of user. If you are a registered user on the TW, then you are a user on Mantis and visa versa. Creating an account on TW also creates an account on Mantis.
(3) Either a center module to deliver Mantis content or a menu link to take you to the linked Mantis website.
(4) Users can create links between forum topics and Mantis bugs. Each forum topic links to zero or one Mantis Issue, and each Mantis Issue links to zero or more TW forum topics.
(5) Develop a TikiWiki syntax enhancement to enable users to easily reference Mantis bugs by Bug ID.

It's easy:
http://translate.google.com/translate_tools?hl=en

((SAML))

http://en.wikipedia.org/wiki/Security_Assertion_Markup_Language
http://simplesamlphp.org/

I think it would be very useful to add an SQL tracker field type so as to be able to "link" tracker items to external database data much like item link does for inter-tracker items aka foreign keys.

Why? Because it would massively improve interaction with external data. We could have a DB field in a tracker that pulls data from an external ERP/CRM/MRP/you-name-it database and links it to data in the tracker. eg add a tracker that users rate products, taking the product records from a live ERP database.

Currently the DBReport and SQL plugins cater for that need in wiki pages but nothing can be used in trackers.

How? In order to make it best usable and comparable to item link, it would look exactly the same as the item link with:
*an added option for ''DSN'' selection
*replacing ''tracker ID'' with ''SQL statement''
*replacing ''field ID'' with ''Column Number''
*removing ''Status Filter''

Please see: ((OpenMicroBlogging))

hcal was added to 1.10!

As this is an ongoing process, we'll use a wiki page to coordinate efforts. Please see: ((microformats)).

Please see: ((WebDAV))

NTLM is an authentication protocol which is widely used in Microsoft based network environments. By using it with HTTP you can use that method for single-sign-on (SSO) authentication within your web browser.
This means that without needing to enter additional username or passwords, you can be authenticated at the website you're visiting. This is quite convenient especially for company intranets. NTLM should work with all major browsers (Internet Explorer, Firefox and Opera).

Tiki has internal ((doc:search)). It is fully integrated, checks permissions, and works on shared server, etc.

However, in some contexts, better support for external search technologies would be useful.


Related:
http://framework.zend.com/manual/en/zend.search.lucene.html
http://www.sphinxsearch.com/
http://www.google.com/sitesearch/
http://lucene.apache.org/solr/
http://ir.dcs.gla.ac.uk/terrier/

[http://freshmeat.net/browse/1099/|bibliography management system] like www.bibwiki.com

http://refbase.sourceforge.net/

Could probably be done by a smart combination of ((doc:wiki)) & ((doc:trackers)) in a [http://profiles.tikiwiki.org|profile].

[http://en.wikipedia.org/wiki/Wikipedia:CITE|This guideline uses the terms "source", "reference", "citing", and "citation" interchangeably.]


Related:
[wish1825|Generate footnotes at the bottom of a wiki page] (a simpler version of the current wish)

Setting feature_tell_a_friend=n doesn't affect the "Email This Post" functionality for the blog, so visitors is always offered to mail the link for a post. Imho the admin should be able to choose if this is allowed or not.

Let's follow the progress on this:
http://intranetblog.blogware.com/blog/_archives/2008/9/25/3900479.html

See also: ((CMIS))

Let's follow the progress on this:
http://intranetblog.blogware.com/blog/_archives/2008/9/25/3900479.html

See also: ((CMIS))

We have: ((tw:PO convertor for TikiWiki))

Should we change the way we handle language.php?: ((Research about different i18n systems))

We'll coordinate at ((diso))

Please see:
http://www.google.com/webmasters/gadgets/

Please see:
http://developers.facebook.com/connect.php
http://www.sociable.es/en/facebook-connect/

http://en.wikipedia.org/wiki/Gravatar
http://en.gravatar.com/site/implement/images/smarty/


https://www.libravatar.org/

Tiki can read and display RSS feeds: good
Tiki can read, combine and display RSS feeds : great


The next step is to import the data into Tiki and treat it like a native article / event / whatever.

If the remote article / event / whatever is modified, the item should be re-imported (but not duplicated). Using the URL to identify the uniqueness. (Some systems many use titles in the URL and if the title changes, we'll end up with a duplicate)

Related:
*[tiki-view_tracker_item.php?itemId=496|RSS feeds on tiki calendar + calendar data sharing via RSS (remote calendars)]
* http://profiles.tikiwiki.org/Collaborative_Watch

No indent
: One indent
:: Two indents

Please see:
http://www.mediawiki.org/wiki/Help:Formatting

MediaWiki/Wikipedia has an interesting way of dealing with meta-data concerning a wiki page. [http://en.wikipedia.org/wiki/Help:Infobox|Infobox] is very flexible and is very suitable to an encyclopedia. It's easy to create new ones and they are very flexible to adapt to the topic. As soon as a bunch of pages have something in common, you can create one and it gives visitors and quick overview of what characteristics this entry has.

There are over a hundred of these templates:
http://en.wikipedia.org/wiki/Category:Infobox_templates

Here is a simple one:
http://en.wikipedia.org/wiki/Template:Infobox_Animal

Here is a more advanced one where special language codes, when parsed, are shown with a nice presentation:
http://en.wikipedia.org/wiki/Wikipedia:Babel

This is a great way to have ad-hoc, organically growing meta-data around wiki pages which share some sort of structured/comparative data.

In TikiWiki, we use ((doc:trackers)) for tabular data. We need to have an even tighter integration.

Goal: that the metadata be stored both in the wiki page and the trackers
That you can update in one or the other. This would permit us to make lists/tables with all the data from all the infoboxes, without duplicating the data. (not sure if/how to do this with MediaWiki)

We'd need a Wiki Page field-type in trackers. Say I have an "Animals" tracker with all the Meta-Data. One of the fields should be the name of the associated wiki page. And that wiki pages "knows" to get latest data from tracker (like we do now for ((doc:PluginTrackerList)) and ((doc:PluginTrackerItemField)).



{img src=images/code.png}%%% {CODE(caption="2008-06-22 on #mediawiki on freenode.net", wrap=1)}
[09:48] marclaporte: Say I have lots of data in various infoboxes, is it possible to make a report/list/table of all these infoboxes and have them link to the various wiki pages?
[09:48] Splarka: you can use Special:Whatlinkshere on each infobox
[09:48] Splarka: (sorta)
[09:49] marclaporte: tks, would you know of an example?
[09:51] Dantman|FS: SMW
[09:51] Dantman|FS: Doing that with data is basically the purpose of SMW
[09:52] Splarka: http://en.wikipedia.org/wiki/Special:Whatlinkshere/Template:Infobox_Aircraft
[09:52] marclaporte: There are some lists here: http://en.wikipedia.org/wiki/Comparison_of_wiki_software -> how to reuse that info in infoboxes on each page
[09:52] marclaporte: tks
[09:53] marclaporte: Splarka: : yes, that's what I am looking for
[10:05] marclaporte: Splarka: : So now I know where the template is used. What if I want to make a mega chart for all the planes from all the infoboxes?
[10:06] Splarka: well, that might be something more for the category system
[10:06] Splarka: (or ask Dan about SMW, unless he means Super Mario World)
[10:08] Dantman|FS: heh
[10:10] marclaporte: Dantman|FS: : What is SMW?
[10:10] Dantman|FS: Semantic MediaWiki
[10:10] Dantman|FS: http://semantic-mediawiki.com/
[10:11] Dantman|FS: It's an extension for MediaWiki
{CODE}

!!Other things to think about:
*When watching a wiki page, how to watch tracker(s) which are associated with that wiki page?
*In page editing of tracker data, have a quick & nice interface like the ((doc:dynamic variable)) feature

Related:
*[wish2102|Support some of the MediaWiki syntax that doesn't conflict with TikiWiki syntax]
*[wish1191|Wiki editing: Preview with diff, like Mediawiki]
*[wish1781|Support for the Wiki creole markup (syntax)]
*[wish1220|MediaWiki import script]