It sounds like a lot of the functionality you want - adding a class of objects to a page with properties - is already supported by the Semantic MediaWiki extensions. You can simply create a Semantic Form to add your new material, and fill in values for whatever properties you've defined in your wiki. Then you can query a particular property, property value, or list all materials and properties in a tabular format using the Semantic Results Format extension. -----Original Message----- From: mediawiki-l-bounces(a)lists.wikimedia.org [mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of Albert Coder Sent: Wednesday, June 25, 2014 5:26 AM To: mediawiki-l(a)lists.wikimedia.org Subject: [MediaWiki-l] Need help regarding MediaWiki-extension Hello! My name is Albert. I am making an extension in mediawiki which is capable of storing materials, values of their properties like tensile strength, specific heat etc., add new material, view all stored values of properties, import/export in CSV, JSON etc. format. But I have been able to do this to some extent with the help of two extensions. First extension[1]-> Can add new material, add values for the properties of that material. Second extension[2]-> Can show the all the materials and values of their properties with their timestamp in tabular form. The code of first extension can be seen at [3]. And the code of second extension can be seen at [4]. How can I merge the functionalities of both these extensions to make a single extension? I wish to embed the code of second extension in my first extension. I tried doing this by writing the code of second extension in a new class which extends SpecialPage class within main file of my first extension and then included the name of the new class in $wgAutoloadClasses[' ']. I am not sure if this method is right. In short I wish to have a link "view all properties" on my special page of first extension such that the code of my second extension gets executed and shows all properties. Another query is that I wish to make certain forms like add new property, add new material-type, add new property-type and so on. How can I navigate those forms with the hyperlinks on the special page of my first extension. Or how can I add new pages or special pages perhaps in my extension to achieve the required functionality? I tried to study linker class from [5] but I could not understand because of absence of examples. Also I tried to get help from #mediawiki IRC but could not earn much. Being a beginner I feel it too tough to get a clear view of how to use the inbuilt functions of mediawiki. I would be grateful if you share/help me with a simple extension which clears all my doubts as above. Please see the two extensions working at [1] and [2] respectively. [1]-> http://202.164.53.122/~albertcoder/mediawiki-1.22.6/index.php/Special:Mat_e… [2]-> http://202.164.53.122/~albertcoder/mediawiki-1.22.6/index.php/Special:Joins [3]-> https://github.com/albertcoder/MaterialsDatabase (Specialmat_ext.php has all the coding) [4]-> https://github.com/albertcoder/SqlJoinsMediawiki (SpecialJoins.php has all the coding) [5]-> doc.wikimedia.org/ -- Thanks Albert www.coderalbert.wordpress.com " Eat Sleep Conquer Repeat " _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

Yes - this should definitely be possible. It isn't a complex design. However, you might want to rework the conceptual data structures to be a little less "database-like", and more "semantic-web-like". From your design, I'd do the following: Category: Material Property: Density (range: floating-point number) Property: Boiling Point (range: integer) Property: Melting Point (range: integer) Property: Specific Heat (range: integer) Property: Tensile Strength (range: integer) Property: Material Type (range: enumerated type [metal, non-metal, fluid]) Then you could create a Material template that put the different properties into an InfoBox, and assigned the values to the properties. Then to create the Material table, you'd have another page - a concept page - with something like the following query: {{#ask:[[Category:Material]] |?density |?Boiling Point ... }} To list all the current Boiling Point values, you'd simply go to the Property:Boiling Point page. That should list all the Material - value pairs. -----Original Message----- From: mediawiki-l-bounces(a)lists.wikimedia.org [mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of Albert Coder Sent: Wednesday, June 25, 2014 12:59 PM To: MediaWiki announcements and site admin list Subject: Re: [MediaWiki-l] Need help regarding MediaWiki-extension On Wed, Jun 25, 2014 at 8:00 PM, Ed Swing <Ed.Swing(a)sas.com> wrote: @ Krabina Bernhard and Ed Swing Thanks a lot for the suggestion, I read about Semantic MediaWiki. It's a marvellous extension but I have one query which I couldn't figure out. I have some compulsion to store the data in the database design [1]. Is it possible to store data in this database design using Semantic MediaWiki? [1] http://202.164.53.122/~albertcoder/images/fdb.JPG -- Thanks Albert www.coderalbert.wordpress.com " Eat Sleep Conquer Repeat " _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

The best source is http://semantic-mediawiki.org - it has a number of helpful pages. There is a separate mailing list (aside from this one) that is devoted to Semantic mediawiki usage as well. -----Original Message----- From: mediawiki-l-bounces(a)lists.wikimedia.org [mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of Albert Coder Sent: Wednesday, June 25, 2014 1:59 PM To: MediaWiki announcements and site admin list Subject: Re: [MediaWiki-l] Need help regarding MediaWiki-extension On Wed, Jun 25, 2014 at 10:43 PM, Ed Swing <Ed.Swing(a)sas.com> wrote: Semantic MediaWiki seems to be much promising! I would be grateful if you could provide some useful links to get started with so that I can get a clear view of how things work in SMW and port my extension to it. -- Thanks Albert www.coderalbert.wordpress.com " Eat Sleep Conquer Repeat " _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

Hi Everyone has access since it's a wiki. You can, however, lock the pages that you set properties on. Or alternatively you can use the following extensions: http://www.mediawiki.org/wiki/Extension:AccessControl http://www.mediawiki.org/wiki/Extension:SemanticAccessControl http://www.mediawiki.org/wiki/Extension:SemanticACL Sent from my iPad On Jun 25, 2014, at 11:17 AM, Albert Coder <eralbert9191(a)gmail.com> wrote:

Yes, there is the data type "record" that can store n-ary relations as well as the extension Semantic Internal Objects (which I prefer to use): http://www.mediawiki.org/wiki/Extension:Semantic_Internal_Objects For a start on SMW the user manual on www.semantic-mediawiki.org is quite good, even better ist Yaron Koren's book http://workingwithmediawiki.com/ (not only covering SMW, but MediaWiki in general). There are also user and developer mailing lists I'd recommend you to join: https://semantic-mediawiki.org/wiki/Semantic_MediaWiki_mailing_lists And on October 1-3 whe have the SMWCon in Vienna, Austria :-) regards, Bernhard ----- Ursprüngliche Mail -----

You should ask this on the SMW developer mailinglist... -Bernhard

This is a big problem, why people often unaware of the SMW existence. 26.06.2014 9:38, Albert Coder пишет:

Maybe it's a bigger problem -- mainly the failure of having all the extensions of Mediawiki more clearly organized and presented to the public. It's still amazing to me that the one and only method to announce new extensions, the Extension Matrix, has been broken since October and it seems there are no plans to fix it. None of the extensions are rated, or have been rated (I understand there is a Google summer of code working on that -- hopefully it gets somewhere). The level of knowledge to install an extension varies based on the developer's thoughts. Mediawiki is great software that deserves a better standard for presenting itself to the public. When you compare Mediawiki to Wordpress, Joomla, etc., one quickly realizes Mediawiki is far behind the curve. For comparison look at the plugin for Joomla called Jomsocial and the Mediaiwki extension Social Profile: one has evolved into something that is up to speed in the modern Internet while one has mostly likely not changed since 2008. Of course, some extensions will die, or get old, but the Mediawiki model of presenting extensions is still very poor. I could go on, but it's already too much of a rant. Sent from my iPad On Jun 26, 2014, at 12:44 AM, Vedmaka <god.vedmaka(a)gmail.com> wrote:

Maybe this is something that the MediaWiki release team at MyM [1] should look at. I guess there is no productive MediaWiki site that does not use at least one extension, so it might be sensible to support this as a more essential aspect of the MW develpoment ecosystem and even release management. Cheers, Markus [1] http://wikireleaseteam.org/ On 26/06/14 16:36, Krabina Bernhard wrote:

Hi Phil, Actually you are granting permission to regular users to read the NS_PROJECT namespace. The idea of the $wgNamespacePermissionLockdown statement is that you restrict the permission to only the one that you specify. Ad Op 27 jun. 2014, om 13:50 heeft Legault, Phillip [ITSUS] <PLEGAULT(a)ITS.JNJ.COM> het volgende geschreven: I was looking at the extension Lockdown with these settings in LocalSettings file require_once "$IP/extensions/Lockdown/Lockdown.php"; $wgNamespacePermissionLockdown[NS_PROJECT]['read'] = array('user'); $wgNamespacePermissionLockdown[NS_ PROJECT _TALK]['read'] = array('user'); $wgNonincludableNamespaces[] = NS_ PROJECT; I expected that this would not allow logged in users to read any pages in the NS_PROJECT namespace. Regular logged in users can still read the pages in that namespace. Is there something that I'm doing wrong? Thanks in advance Phil -----Original Message----- From: mediawiki-l-bounces(a)lists.wikimedia.org [mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of Bill Traynor Sent: Wednesday, June 25, 2014 3:44 PM To: MediaWiki announcements and site admin list Subject: Re: [MediaWiki-l] Need help regarding MediaWiki-extension There's also: https://www.mediawiki.org/wiki/Extension:Lockdown https://www.mediawiki.org/wiki/Extension:PrivatePageProtection On Wed, Jun 25, 2014 at 3:25 PM, Chris Tharp <tharpenator(a)gmail.com> wrote: _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l

Ok That works Thank you! -----Original Message----- From: mediawiki-l-bounces(a)lists.wikimedia.org [mailto:mediawiki-l-bounces@lists.wikimedia.org] On Behalf Of Chris Tharp Sent: Friday, June 27, 2014 12:18 PM To: MediaWiki announcements and site admin list Subject: Re: [MediaWiki-l] Need help regarding MediaWiki-extension Hi Actually that makes it so non-logged users can't read the namespace. Change it to sysop for read to have it now you want it. Sent from my iPad On Jun 27, 2014, at 4:50 AM, "Legault, Phillip [ITSUS]" <PLEGAULT(a)ITS.JNJ.COM> wrote: _______________________________________________ MediaWiki-l mailing list MediaWiki-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/mediawiki-l