Help:Extension:GWToolset

Introduction
You’re probably reading this because you are considering or planning to make a large amount of content available for reuse by publishing it on Wikimedia Commons. This manual will guide you through the necessary steps.

Technical compatibility analyses
The Toolset has been developed to be used by the most common way GLAMs have organised their content. This means that the Toolset is easy to work with for most organisations, but that some will have to take extra measures before they can use it. The diagram in this paragraph can be used to determine how compatible the Toolset is for your organisation. Every question in the diagram is explained underneath.

Is the XML in flat format?
Er zijn verschillende standaarden waar instellingen gebruik van maken voor het organiseren van de metadata, zoals OAI-PMH, EDM, MARC en Leto. De Toolset kan alle vormen van metadata gebruiken, zolang deze maar aan bovenstaande eisen voldoen.

What is flat format?
The metadata of individual objects have to be on the same level of hierarchy in the XML file, that's what 'flat' revers to. Metadata in a deeper level, further in the hierarchy, is not recognised by the Toolset.

The use of attributes
Attributes of declarations are also not recognised with one exception: the language attribute. This attribute can be used to recognise the descriptions of objects in different languages.

For example , is recognised as a description in English.
 * This is a description

Will be seen by the Toolset as The PhotoID in this example will not be read. Information in attributes can cause loss of information.
 * www.example.org
 * www.example.org

Multiple descriptions in one metadata field
Er zijn velden die meerdere keren voor kunnen komen, bijvoorbeeld . Er is voor gekozen om deze samen te voegen, gescheiden door een pipe ( | ). In sommige gevallen heeft een bestand meerdere omschrijvingen, bijvoorbeeld "voertuigen", "rupsvoertuig", "vlammenwerper" en "gevestvoertuig". Als deze allemaal als  zijn opgenomen worden deze toegevoegd. Het is dus goed om deze in verschillende declaraties te onderscheiden.

Dus niet
 * 


 * "voertuigen", "rupsvoertuig", "vlammenwerper" ,"gevestvoertuig"


 * 

maar


 * 


 * voertuigen


 * 


 * 


 * rupsvoertuig


 * 


 * 


 * vlammenwerper


 * 


 * 


 * gevestvoertuig


 * </dc:description>

Door je elementen te scheiden in je xml zorg je ervoor dat deze op de juiste manier worden weergegeven op Wikimedia Commons.

Can the XML be transformed in flat format?
Mocht de metata omgezet worden om aan bovenstaande eisen te voldoen dan kan dat door:

* een specialist een script op te laten stellen die dat omzet

*  gebruik te maken van xslt:  http://www.w3schools.com/xsl/

* Kiezen voor een standaard die xml plat publiceert, bijvoorbeeld OAI-PMH en tot op zekere hoogte de Europeana API

* Google Refine of Open Refine zou ook kunnen helpen:  https://github.com/OpenRefine

Selecting content
Not all content is suited to be published. File formats, copyright restrictions, organisational restrictions, etc. determine if a work can be published on commons.

Content donation strategies
There have been several large content donations already. All of these were mass donations: one single event where all the content was uploaded to Wikimedia Commons. This is not the only way to do a donation. This chapter discusses different strategies for content donations.

One time mass donation
This is the classic way of donating content: a large scale donation of the content that can be selected with the available sources.

Advantages:

Theme based
Some GLAMs are currently considering theme based uploads. A theme can be an exhibition. This means that selecting the content that will be uploaded to commons can become a part of the process of preparing an exhibition.

Advantages:
 * Ongoing process of uploads, every new upload gains interest
 * Lessons learned from past upload can be

Advantages

Requesting access
To use the toolset you need to:
 * 1) Be a user of the wiki.
 * 2) Be granted access rights to the toolset.

We recommend that you do all testing on the Commons Beta server and only once you feel that the tool is giving you the results you want, use it on the Production server. Because these are two separate environments, you will need to have a user account on each and request access on each. The best way to do this:
 * 1) Commons Production server: leave a message on the Commons notice board to request rights for the GWtoolset. Please introduce yourself and motivate your request.
 * 2) Commons Beta server: contact a developer or bureaucrat on beta to request the rights for the GWToolset user group on beta. You can ask in the commons IRC channel or contact them from these lists:
 * 3) Bureaucrats
 * 4) Developers

Screencast
The following screencast gives you a quick overview of how to use the extension. You can follow along by going to Special:GWToolset and following the wizard instructions. Note: you will need to be a member of the “gwtoolset” group in order to use the extension. Contact a Wikimedia Commons admin to be added to the group.