Wikitech-l June 2010

wikitech-l@lists.wikimedia.org

81 participants
58 discussions

Re: [Wikitech-l] Reasonably efficient interwiki transclusion
by Happy-melon 04 Jun '10

04 Jun '10

-------------------------------------------------- From: "Dmitriy Sintsov" <questpc(a)rambler.ru> Sent: Friday, June 04, 2010 11:35 AM To: "Happy-melon" <happy-melon(a)live.com> Subject: Re: [Wikitech-l] Reasonably efficient interwiki transclusion > * Happy-melon <happy-melon(a)live.com> [Fri, 4 Jun 2010 11:10:04 +0100]: >> >> MW 2.0? :-D >> > Not really. These are pretty simple things, comparing to Parser and some > another classes. MediaWiki class isn't that complex. > >> You wouldn't need to remove the globals, at least immediately; you'd >> retain >> them as aliases for the relevant variables of the 'main' wiki; > assuming >> that >> it makes sense to define one primary wiki, which it usually does. >> > That might introduce glitches where one variable in "global / member > pair" has it's value modified, while another isn't. Or, maybe the > references (&$) will help. > Dmitriy > s/aliases/references, yes. --HM

1 0

a wysiwyg editor for wikipedia?
by William Le Ferrand 04 Jun '10

04 Jun '10

Dear all, I've started to develop a simple wysiwyg editor that could be useful to wikipedia. Basically the editor gets the wiki code from wikipedai and builds the html on client side. Then you can edit the html code as you can imagine and when you are done another script converts the html back to wiki code. There is a simple demo here : http://www.corefarm.com:8080/wysiwyg?article=Open_innovation . You can try other pages from http://www.corefarm.com:8080/ (type the article name). It's far from being really usable now but do you think that such a tool would be useful ? The global structure is ok, most of the buttons are working (even if there are no special images to figure out what they actually do); it's just a matter of filling the gaps and support all the wikipedia syntax. You comments are welcomed! All the best, William

14 22

[GSoC] Extension management platform
by Jeroen De Dauw 03 Jun '10

03 Jun '10

Hey all, As a lot of you already know, I'm again doing a Google Summer of Code project for the WMF this year. The goal of this *awesome* project is to create a set user friendly administration interfaces via which administrators can manage the configuration of their wiki and extensions as well as manage extension installation and updating. The user experience should be as *awesome* as the Wordpress one, or even better. After doing research in existing code and talking to the relevant people, I created a little roadmap [0] of how I plan to proceed with my project. Any feedback and comments on this would be very much appreciated (esp the critic ones :). It'd be to bad to reinvent things already achieved by people, simply by me not knowing about it! I hope to start with the actual coding by this weekend, and will update the roadmap, and the docs page itself [1], as well as my blog [2], as I make progress. [0] http://www.mediawiki.org/wiki/Extension_Management_Platform/Roadmap [1] http://www.mediawiki.org/wiki/Extension_Management_Platform [2] http://blog.bn2vs.com/tag/extension-management/ Cheers -- Jeroen De Dauw * http://blog.bn2vs.com * http://wiki.bn2vs.com Don't panic. Don't be evil. 50 72 6F 67 72 61 6D 6D 69 6E 67 20 34 20 6C 69 66 65! --

3 2

New committers
by Tim Starling 03 Jun '10

03 Jun '10

Extension access only: * Cobi Carter (cobi): ClueBot * Ryan Kaldari (kaldari): Staff developer for fundraising -- Tim Starling

4 4

collapsible-navigation
by Bo Boz 03 Jun '10

03 Jun '10

Hi, Really like how the new collapsible-navigation is implemented in Wikipedia. Can I find that code somewhere and can I use it (GPL?) Thanks, Bo

2 1

Python Wikipedia Robot Framework in CodeReview
by Tim Starling 02 Jun '10

02 Jun '10

I've added the Python Wikipedia Robot Framework to MediaWiki.org code review: http://www.mediawiki.org/wiki/Special:Code/pywikipedia The post-commit hook is set up but untested. We'll see if it works when someone commits something. -- Tim Starling

2 1

problem with Maps extension
by Chris Thomas 02 Jun '10

02 Jun '10

I'm running MW 1.12 on Debian Lenny and I installed the Maps 0.5.5 extension. It works, however I get this message for random points when I refresh. The list of points that aren't geocoded change with each refresh. "The following addresses could not be geocoded and have been omitted from the map" When the 0.6 version of Maps came out (yesterday) I installed it and, immediately I get this error: Fatal error: Call to undefined method Parser::getOutput() in /var/lib/mediawiki/extensions/Maps/Services/GoogleMaps/Maps_GoogleMaps.php on line 217 Any thoughts? -Chris

3 11

[gsoc] splitting the img_metadata field into a new table
by bawolff 01 Jun '10

01 Jun '10

Hi all, For those who don't know me, I'm one of the GSOC students this year. My mentor is ^demon, and my project is to enhance support for metadata in uploaded files. Similar to the recent thread on interwiki transclusions, I'd thought I'd ask for comments about what I propose to do. Currently metadata is stored in img_metadata field of the image table as a serialized php array. Well this works fine for the primary use case - listing the metadata in a little box on the image description page, its not very flexible. Its impossible to do queries like get a list of images with some specific metadata property equal to some specific value, or get a list of images ordered by what software edited them. So as part of my project I would like to move the metadata to its own table. However I think the structure of the table will need to be a little more complicated then just <page id>, <name>, <value> triples, since ideally it would be able to store XMP metadata, which can contain nested structures. XMP metadata is pretty much the most complex metadata format currently popular (for metadata stored inside images anyways), and can store pretty much all other types of metadata. Its also the only format that can store multi-lingual content, which is a definite plus as those commons folks love their languages. Thus I think it would be wise to make the table store information in a manner that is rather close to the XMP data model. So basically my proposed metadata table looks like: *meta_id - primary key, auto-incrementing integer *meta_page - foreign key for page_id - what image is this for *meta_type - type of entry - simple value or some sort of compound structure. XMP supports ordered/unordered lists, associative array type structures, alternate array's (things like arrays listing the value of the property in different languages). *meta_schema - xmp uses different namespaces to prevent name collisions. exif properties have their own namespace, IPTC properties have their own namespace, etc *meta_name - The name of the property *meta_value - the value of the property (or null for some compound things, see below) *meta_ref - a reference to a meta_id of a different row for nested structures, or null if not applicable (or 0 perhaps) *meta_qualifies - boolean to denote if this property is a qualifier (in XMP there are normal properties and qualifiers) (see http://www.mediawiki.org/wiki/User:Bawolff/metadata_table for a longer explanation of the table structure) Now, before everyone says eww nested structures in a db are inefficient and what not, I don't think its that bad (however I'm new to the whole scalability thing, so hopefully someone more knowledgeable than me will confirm or deny that). The XMP specification specifically says that there is no artificial limit on nesting depth, however in general practise its not nested very deeply. Furthermore in most cases the tree structure can be safely ignored. Consider: *Use-case 1 (primary usecase), displaying a metadata info box on an image page. Most of the time that'd be translating specific name and values into html table cells. The tree structure is totally unnecessary. for example the exif property DateTimeOriginal can only appear once per image (also it can only appear at the root of the tree structure but thats beside the point). There is no need to reconstruct the tree, just look through all the props for the one you need. If the tree structure is important it can be reconstructed on the php side, and would typically be only the part of the tree that is relevant, not the entire nested structure. *Use-case 2 (secondary usecase). Get list of images ordered by some property starting at foo. or get list of images where property bar = baz. In this case its a simple select. It does not matter where in the tree structure the property is. Thus, all the nestedness of XMP is preserved (So we could re-output it into xmp form if we so desired), and there is no evil joining the metadata table with itself over and over again (or at all), which from what i understand, self-joining to reconstruct nested structures is what makes them inefficient in databases. I also think this schema would be future proof because it can store pretty much all metadata we can think of. We can also extend it with custom properties we make up that are guaranteed to not conflict with anything (The X in xmp is for extensible). As a side-note, based on my rather informal survey of commons (aka the couple people who happened to be on #wikimedia-commons at that moment) another use-case people think would be cool and useful is metadata intersections, and metadata-category intersections. I'm not planning to do this as part of my project, as I believe that would have performance issues. However doing a metadata table like this does leave the possibility open for people to do such intersection things on the toolserver or in a DPL-like extension. I'd love to get some feedback on this. Is this a reasonable approach for me to take on this. Thanks for reading. -- -bawolff

8 12

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l June 2010