Last modified: 2014-03-01 20:26:15 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T43969, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 41969 - Import should allow mapping of namespace names and aliases
Import should allow mapping of namespace names and aliases
Status: NEW
Product: MediaWiki
Classification: Unclassified
Export/Import (Other open bugs)
unspecified
All All
: Low enhancement with 1 vote (vote)
: Future release
Assigned To: Nobody - You can work on this!
https://bugzilla.wikimedia.org/show_b...
:
Depends on:
Blocks: 30723
  Show dependency treegraph
 
Reported: 2012-11-10 15:08 UTC by Purodha Blissenbach
Modified: 2014-03-01 20:26 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Purodha Blissenbach 2012-11-10 15:08:27 UTC
Import data and the importing Wiki may contain differing and/or more or less name space names and name space name aliases. Currently, if adjustemns are needed, one needs to know that before the import is started, and has to alter the import data so as to match the importing wikis names space names and aliases. This can be cumbersome and time consuming for. It is error prone, and next to impossible for large automated imports.

We could add an option (checkbox) asking dor a stepwise approach like this:
1) Show a list of all namespace names in the import and in the local wiki with
an automatically generated mapping suggestion.
2) Allow the importer to adjust the mapping.
3) Do the final import.

The downsides:
A) An uploaded file has to be preserved over some time including possibly
multiple data submissions by the importer.
B) The import file has to be read twice. It has to be read and analyzed in its
entirity during the 1st scan already since the the list of original namespaces
in the beginning does not deal with possible occurrences of
name space name aliases embedded in page data. Those need to be part of the
mapping, however.

The good sides:
- Most flexible.
- Often used mappings can be preserved and automagically be recalled by the
import process.
- Step 1) could by the way reveal some statistics to the importer, allowing e.g. to not import implausible data.

This looks like a major revaming of the import code, however.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links