Last modified: 2014-11-17 10:36:13 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 8160 - ParserFunction for Library of Congress Control Numbers (LCCN)
ParserFunction for Library of Congress Control Numbers (LCCN)
Product: MediaWiki extensions
Classification: Unclassified
ParserFunctions (Other open bugs)
All All
: Lowest enhancement with 3 votes (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: 29473
  Show dependency treegraph
Reported: 2006-12-05 16:07 UTC by Omegatron
Modified: 2014-11-17 10:36 UTC (History)
6 users (show)

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


Description Omegatron 2006-12-05 16:07:18 UTC
This is similar in concept to the magic ISBN numbers we already have, but I
think a different implementation would be superior.

LCCNs have two forms.  Regular form that you would find in books (89-456), and
normalized form, used for machine-readable stuff (89000456).

See for the normalization rules.

We have a template {{LCCN}} to handle them now, but, since we have no string
manipulation capabilities on the user side, it's ugly and hard to use.

The magic ISBN feature is nice, but instead of "LCCN 71-143545" being rendered
directly as a link, I'd rather just have a flexible parserfunction like
urlencode to convert regular form into normalized form.  Like
"{{lccn:n78-89035}}" would output "n78089035".  

Then the numbers can be used in different ways in different places.  The
standard template's link target and display formatting could remain controllable
by users, while the normalized number could be used by itself in
machine-readable COinS tags in citation templates, for instance.
Comment 1 Quim Gil 2014-04-26 06:31:09 UTC
{{Template:LCCN}} still seems to fit the bill, and a parserfunction for LCCN in MediaWiki core sounds a bit of an overkill.

I wonder whether this is a wontfix.
Comment 2 John Mark Vandenberg 2014-04-26 09:35:17 UTC
(In reply to Quim Gil from comment #1)
> I wonder whether this is a wontfix.

I agree.  The Lua string manipulation capabilities now available provide the functionality requested by this bug.

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