Last modified: 2012-06-08 19:08:55 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 14426 - service links don't work for many-valued properties
service links don't work for many-valued properties
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Markus Krötzsch
Depends on:
  Show dependency treegraph
Reported: 2008-06-06 05:04 UTC by S Page
Modified: 2012-06-08 19:08 UTC (History)
0 users

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

implement getServiceLinks() for NAry, seems to work (309 bytes, text/plain)
2008-06-06 06:10 UTC, S Page

Description S Page 2008-06-06 05:04:22 UTC
It would be nice to grab pieces of a many-valued property in service links.  For example, a document with a Property:Version composed of filename + revision number  could link to the right version in a VCS.

But it seems many-valued properties don't implement getServiceLinkParams(), so even if you specify [[Provides service::xyz]], no service link shows up.

The simplest approach might be for SMW_DV_NAry.php to invoke getServiceLinkParams() for each element.  That file notes " * TODO: support outputformat", maybe that's the same as this bug.
Comment 1 S Page 2008-06-06 06:10:38 UTC
Created attachment 4958 [details]
implement getServiceLinks() for NAry, seems to work
Comment 2 [[kgh]] 2012-06-08 19:08:39 UTC
I am sure that this patch was implemented upon creation of datatype "Record" in 2010. Thus closing this as RESOLVED FIXED. Please reopen in case this was not considered.

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