Here is the detailed explaination of the work done till now in my GSoC project.

1. Flickr Integration

Added capability of adding images directly from Flickr by providing either the photo URL or the photoset URL from Flickr.

• Uploading a single photo : The user can upload a single image by giving its URL, and the wizard would upload the largest available size of the image ( original size in case of pro users ), along with its Licensing information.

• Uploading images from a photoset : When the user enters the Photoset URL, all the images with the allowed licenses are shown to the user in a grid. The user can then select the images to upload, and the images would be uploaded with the licensing information

• The user is only shown the Flickr option, when UploadsFromUrl are enabled on the wiki and the logged in user has the permission to do so.

• The Flickr API key also needs to be set in order to allow the uplaods to take place. If the API key is not set, then again the Flickr interface is not shown.

2. Geolocation integration

The basic feature in for this has been implemented, although it is not reviewed till yet.

• Open Street Maps along with Leaflet library have been used for this purpose.

• On the ‘Details’ step of the wizard, the map is shown with the geolocation co-ordinates extracted from the EXIF data from the media.

• In case the data is not available, the user can chose a point on the map to tag the image with those co-ordinates.

Work left to be done :

• Thinking of a new way to handle with large number of media files, as attaching a single map with each file, would make the page very heavy and cause it to breakdown.

• The default settings, such as the default location and zoom levels have been chosen aribitrary. I need to work on deciding them based on some rational decision, or maybe a setting in the wiki.

• Possible way of tagging the files with direction and altitude, as a lot of cameras suport these functionalities now.

In this update I have extended the existing integration of Flickr into Upload Wizard to also allow upload of images from a Flickr photoset.

Link to the patch : https://gerrit.wikimedia.org/r/#/c/15547/

Changes

• Taking a Photoset URL from the user
• Check the Photoset for all the images under a valid license, and fetch information of them.
• Display the thumbnails of those images in a grid manner for the user to select the images to be uploaded.
• Fetch the available largest size of the image and add it to the list of uploads.

Minor Changes

• Moved the API URL and Key to the Congif file to the config file.
• Fixed interface issues with buttons and input elements.
• Fixed issue with starting of with a new set of uploads after getting finished with one batch of uploads from the thanks step of the wizard.

The project up till now

The user can upload a single image from Flickr, which would get uploaded along with its License fethed from Flickr. The user can also provide the URL of a Flickr Photoset, and all the images in the photoset that have a valid license would be shown to the user. The user can then select the images to be uploaded, and the largest possible size of the image ( Flickr only provides original images for pro users ). Like in the case of a single image upload from Flickr, the license is automatically fetched from Flickr, and the user does not have the option to change the license. Also, uploads from Flickr as well as the local machine can be done in a single batch.

Still Left to do

• Fix certain minor issues with the current code.
• Fetch other details such as description, user information and geolocation from Flickr.
• Writing tests for the code.
• Writing Documentation.

Its been quite some time, and a much needed update on my work in Integrating Flickr in the Upload Wizard extension in MediaWiki. Currently, given a URL of an image, the file gets uplaoded along with its license. Here is a detailed description of the the work :

• Work done so far

  • URL of the image is taken from the user, and the license of the image is fetched through the Flickr API.
  • If the license matches the allowed licenses, then its added to the list of Uploads.
  • If the uploads only contains files from Flickr, then the Deeds step of the wizard is skipped and the user proceeds directly to the Details section of the Wizard as the user can not edit the license of the image fetched from Flickr directly.
  • If the uploads also contains files added locally, then in the Deeds section, the images added from Flickr are
    not shown.
  • In the Details step of the Upload Wizard, the License information of the image is shown to the user.
  • The license of the files uploaded from Flickr is not editable, that is the user can not chose or edit the license, and the retreived license is only used.

The progress of the project can be tracked here : http://bit.ly/KFW9hw
There are still a lot of issues with the current process. Hopefully by the end of the next week, I would be able to resolve these issues and then put it up for testing.

• Still to do
  • Fix the issues with the current code.
  • Fetch other information of the image, which could be prefilled in the
    Details section of the upload ( like Description and Location information)
  • Allow user to uplaod images from an album, by giving the URL of the album and then selecting the images to upload.
  • Writing tests.

On my visit to the Berlin Hackathon, I had worked with Kolossos on Open Street Maps and Open Layers. It was quite a good learning, and a lot of my work was done there regarding my Geolocation support in the Upload Wizard.
This is the work that I have done with respect to the Geolocation integration :

• I have used Leaflet Library along with Open Street Maps, for no specific reason other than that I found it to be lightweight and fit for the simple scope we have.

  • need to edit this I had a small talk with Brion Vibber, and he suggested me to go ahead with Leaflet. I also discussed it with my mentor Ryan Kaldari, and he had no preference for either of them .
    I have not worked sufficient enough on either of the libraries to decide which one is better, and hence I am open to using both for the project as of now.

• There are 2 use cases as of now :

  • The map is shown with the pointer of the image’s location, if the Geolocation information is available in the EXIF data of the image.
    (Need to give user an option of changing the location and marking a new one here)

  • When the Geolocation information is not available, the user can chose the location on the map which gets added to the image’s information.

This is the work that I have done till now, and you can see see it on the patch I have submitted here : https://gerrit.wikimedia.org/r/#/c/12353/.

There is a small bug with the current commit and maps might not show properly, and instead show a hidden grey box. It happens because of the map container being hidden when the map is loaded. I am yet to fix this problem

Work still left to do :

• Decide on some basic elements of the map, as to where should it be centered by default and what layers should be shown.
• Right now, every image has a map attached with it. As the number of images increases, and reaches more than 15-20, then a page would become quite heavy and difficult to load with so many maps in it. Hence I wanted ideas and suggestions as to what would be a better approach for using the maps for this purpose, given the fact that right now we do not have batch functionality in Upload Wizard.
• Implementing the direction support for the Geolocation.
• Giving user an option of editing the location for an media already having a location.
• Integrating it with Flickr to get the location of the image if available on Flickr.

I am Ankur Anand, ( aka drecodeam ), currently working as a Google Summer of Code student for The Wikimedia Foundation.
This is a blog to stay up to date with my project “Integration of Flickr and Geolocation in UploadWizard”.

Project Summary

My project aims at implementing :

• Flickr Integration
  Providing an interface which allows the user to transfer images from Flickr where the UploadWizard extracts license and metadata from the images, converts the license into a Commons License Template and passes on metadata to the next step to generate corresponding WikiText.

• Improving the Geolocation support
  Implementing a JavaScript jQuery plugin which presents a map interface that can be manipulated to select a particular location and report that location in code, preferably as WikiText containing a Location template. The plugin would make use of EXIF data contained in the media file or location data retrieved from Flickr to suggest an appropriate location and could also be manipulated to mark a new location for the media.

Other than implementing the above 2 features, I also aim to implement HTML5 drag and drop support for the files, on which i have already started working on. Moreover i would also work on enhancing the interface and design of the extension according to the Design Recommendations and MediaWiki style guide.

You can read my full proposal here : http://www.mediawiki.org/wiki/User:Drecodeam/GSoC_2012_Application