Last modified: 2008-08-08 21:05:51 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 T16505, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 14505 - enhancement: show *Values* of the property Foo
enhancement: show *Values* of the property Foo
Status: RESOLVED DUPLICATE of bug 13148
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Markus Krötzsch
http://semanticweb.org/wiki/Property:...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-11 02:31 UTC by S Page
Modified: 2008-08-08 21:05 UTC (History)
0 users

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


Attachments

Description S Page 2008-06-11 02:31:52 UTC
In the mail thread "[Semediawiki-user]  Getting the values of a property", ablum wants to list all the *values* of a property.  Property:Foo's page normally lists
  Pages using the property “Foo”
and for each page displays some of the values of Foo on that page.  But:
* The ... elision hides lots of values, which is bad for a property that takes lots of values (e.g. "Employs" or "Has actor")
* The values are spread and repeated among many pages.
So it's very difficult to determine all the values of a property.

It seems a useful enhancement if there was a way to "invert" this to list
  Values of the property “Foo”
and for each value display some of the pages with that value of Foo.  It could be an optional parameter like ?by_value=1 to Property:Foo.

This would require a new SMWStore method, getAllPropertyValues(), but otherwise could reuse much of the SMWOrderedListPage code.

(There's a separate issue that semantic searches can't make the values of a property into the subjects of a query, so it's difficult for users to make a semantic search that displays a list of values.)  A workaround is to populate the "value" pages with the inverse property, and then view the inverse property; but this requires you create a page for every value, and only works for Type:Page.
Comment 1 Markus Krötzsch 2008-08-08 21:05:51 UTC

*** This bug has been marked as a duplicate of bug 13148 ***

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


Navigation
Links