[Wikidata-l] New stuff! (ordering, ranks and a table of content)

List overview All Threads
Download

newer

older

[Wikidata-l] weekly summary #88

[Wikidata-l] DNB 11M bibliographic...

Lydia Pintscher

10 Dec 2013 10 Dec '13

9:44 p.m.

Hey everyone, After a few hick-ups ordering, ranks and a table of content for item pages are now live on wikidata.org together with a load of other small improvements. I hope you enjoy them. There are still a few usability issues with ordering as well as the problem of ordering changes not showing up in diffs. If you find any other issues related to this deployment that do not go away after reloading/purging(add ?action=purge to the URL) the page please let me know. Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Product Manager for Wikidata Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.

Show replies by date

Lukas Benedix

11 Dec 11 Dec

1:58 p.m.

A few notes on usability: First: the load time is extremely bad right now! Even on actual hardware with a good interent connection it takes ~40seconds to load Q42. Ordering: * moving statements is anoying * * if you have more claims in one statement its not easy to move the whole statement block. * * you have to move a claim all the way down in the block before the block moves. Table of content: * there should be a link back to the top in the headlines so a user don't have to scroll all the way up if he clicks the wrong item by accident Ranks: * The three squares on the left are not really self explaining * I think this will lead to big discussions (e.g. the population of Israel: which value should be prefered and which deprecated) * In my opinion the sources and qualifiers should be used to represent the value of a claim (and the clients should decide which claim is the best for them) Lukas Am Di 10.12.2013 21:44, schrieb Lydia Pintscher:

...

Thomas Douillard

3:58 p.m.

Hehe, still a bit of adjustemnt to be done, looks like nobody actually use the test site :) We (the community) should find better ways to actually test the stuffs. PS: to the devteam, wouhou, great to see the efforts on the development ! 2013/12/11 Lukas Benedix <benedix(a)zedat.fu-berlin.de>

...

_______________________________________________ Wikidata-l mailing list Wikidata-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l

Lydia Pintscher

4:31 p.m.

On Wed, Dec 11, 2013 at 1:58 PM, Lukas Benedix <benedix(a)zedat.fu-berlin.de> wrote:

...

A few notes on usability: First: the load time is extremely bad right now! Even on actual hardware with a good interent connection it takes ~40seconds to load Q42.

Yes we're doing firefighting right now.

...

Ordering: * moving statements is anoying * * if you have more claims in one statement its not easy to move the whole statement block. * * you have to move a claim all the way down in the block before the block moves.

You can just move the last one in the block?

...

Table of content: * there should be a link back to the top in the headlines so a user don't have to scroll all the way up if he clicks the wrong item by accident

Will keep that in mind for the UI redesign. Not going to happen before that.

...

Ranks: * The three squares on the left are not really self explaining

Do you have a better suggestion for the symbol?

...

* I think this will lead to big discussions (e.g. the population of Israel: which value should be prefered and which deprecated) * In my opinion the sources and qualifiers should be used to represent the value of a claim (and the clients should decide which claim is the best for them)

Yes there will be discussion but we need to have a way to distinguish for example old data from the current one. Since it is possible to mark several as preferred I hope this will not be too bad however. Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Product Manager for Wikidata Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.

Thomas Douillard

4:48 p.m.

We're figuring out the use of ranking, it's cool but imho it would be great if the results of the discussions are injected back directly into the Wibibase data model. If we give cleat labelling to ranks and the two or three use case that are identified are clearly labelled as such this could be great for usability and would not look like a bit of black magic recepies to the newcomer. Something I would avoid is "If you label this as normal this will be shown is the query data result but not in the infoboxes who will show the results only with preferred ranks with two sources". So maybe we could encode some rules on Wikibase itself, such as "no claim can be ranked as preferred if they are properly sourced", which could display a useful error message to the user if he tries that out, or a tip to why the option is deactivated ? 2013/12/11 Lydia Pintscher <lydia.pintscher(a)wikimedia.de>

...

On Wed, Dec 11, 2013 at 1:58 PM, Lukas Benedix <benedix(a)zedat.fu-berlin.de> wrote:

A few notes on usability: First: the load time is extremely bad right now! Even on actual hardware with a good interent connection it takes ~40seconds to load Q42.

Yes we're doing firefighting right now.

You can just move the last one in the block?

Table of content: * there should be a link back to the top in the headlines so a user don't have to scroll all the way up if he clicks the wrong item by

accident Will keep that in mind for the UI redesign. Not going to happen before that.

Ranks: * The three squares on the left are not really self explaining

Do you have a better suggestion for the symbol?

Andrea Zanni

4:49 p.m.

On Wed, Dec 11, 2013 at 4:31 PM, Lydia Pintscher < lydia.pintscher(a)wikimedia.de> wrote:

...

Ranks: * The three squares on the left are not really self explaining

Do you have a better suggestion for the symbol?

How about numbers? (eg. 1, 2, 3) or the symbol #? Maybe they are clearer. Aubrey

Sven Manguard

4:53 p.m.

I proposed an up arrow, a square diamond, and a down arrow, all from the same Unicode set, in a mockup I sent to Lydia. I still think that those are a better idea, and not just because it was my idea. Sven On Dec 11, 2013 10:49 AM, "Andrea Zanni" <zanni.andrea84(a)gmail.com> wrote:

...

On Wed, Dec 11, 2013 at 4:31 PM, Lydia Pintscher < lydia.pintscher(a)wikimedia.de> wrote:

Ranks: * The three squares on the left are not really self explaining

Do you have a better suggestion for the symbol?

How about numbers? (eg. 1, 2, 3) or the symbol #? Maybe they are clearer. Aubrey _______________________________________________ Wikidata-l mailing list Wikidata-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l

David Cuenca

5:42 p.m.

On Wed, Dec 11, 2013 at 4:53 PM, Sven Manguard <svenmanguard(a)gmail.com>wrote;wrote:

...

The problem with arrows is that it might be confused for voting arrows. Another option could be squares of different sizes, but then the smallest one can be hard to click, and the biggest one hard to place. As for sorting statements, for me drag&drop should be the way of doing it. No idea how much would cost to do it... Micru

Luca Martinelli

10:53 p.m.

First of all, a message to the WD team: AMAZING JOB, GUYS! Now, for the proposals... :) 2013/12/11 David Cuenca <dacuetu(a)gmail.com>om>:

...

On Wed, Dec 11, 2013 at 4:53 PM, Sven Manguard <svenmanguard(a)gmail.com> wrote:

What about coloring the squares? Green for "preferred", blue for "normal", orange or red for "deprecated".

...

As for sorting statements, for me drag&drop should be the way of doing it. No idea how much would cost to do it...

Yeah, I was thinking the same. Also about the "cost". -- Luca "Sannita" Martinelli https://it.wikipedia.org/wiki/Utente:Sannita

Lukas Benedix

5:03 p.m.

...

You can just move the last one in the block?

You can only move ONE claim at a time, the whole statement block only moves if the claim is at the top or bottom of it (depending on the direction you want to move the statement block). I've made an example to illustrate the problem: switching the position of "occupation" and "alma mater" in Q42 http://lbenedix.monoceres.uberspace.de/screenshots/kvhrnxyojz_2013-12-11_16… http://lbenedix.monoceres.uberspace.de/screenshots/h7xiy6yz2w_2013-12-11_16… http://lbenedix.monoceres.uberspace.de/screenshots/lwowf6itfg_2013-12-11_16… http://lbenedix.monoceres.uberspace.de/screenshots/a34zgxmpul_2013-12-11_16…

...

Table of content: * there should be a link back to the top in the headlines so a user don't have to scroll all the way up if he clicks the wrong item by accident

Will keep that in mind for the UI redesign. Not going to happen before that.

Is there any I can have a look at regarding the redesign?

...

Ranks: * The three squares on the left are not really self explaining

Do you have a better suggestion for the symbol?

nope, but I don't think ranks are a good idea in the repo. Judgements about claims should be done at client side based on sources and qualifiers.

...

Old values can be marked with a qualifier, for example: "G.W. Bush" --> "is president of" --> "USA" the qualifier would be "until 2009" or "as of 2003" for a claim that was made 10 years ago.

Lydia Pintscher

5:36 p.m.

On Wed, Dec 11, 2013 at 5:03 PM, Lukas Benedix <benedix(a)zedat.fu-berlin.de> wrote:

...

You can just move the last one in the block?

If you click edit on the bottom statement there in occupation then you only should need one move. And I agree that the usability of this is really not good and needs to be improved.

...

Table of content: * there should be a link back to the top in the headlines so a user don't have to scroll all the way up if he clicks the wrong item by accident

Will keep that in mind for the UI redesign. Not going to happen before that.

Is there any I can have a look at regarding the redesign?

Nothing yet, no.

...

Ranks: * The three squares on the left are not really self explaining

Do you have a better suggestion for the symbol?

nope, but I don't think ranks are a good idea in the repo. Judgements about claims should be done at client side based on sources and qualifiers.

It would not be feasible for Wikipedia for example on a large scale. Sources and qualifiers are in a lot of cases not uniform enough to make such decisions easily in a programmatic way. And time is not the only reason to mark a statement as deprecated or preferred for example. Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Product Manager for Wikidata Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.

Lydia Pintscher

12 Dec 12 Dec

8:40 p.m.

Hey everyone, We just deployed an update with another bunch of performance fixes. This should improve the situation again to roughly the state before the last deployment. We'll be putting more work into this though to improve it even further after Christmas. Cheers Lydia -- Lydia Pintscher - http://about.me/lydia.pintscher Product Manager for Wikidata Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.

3788

days inactive

3790

days old

wikidata@lists.wikimedia.org

Manage subscription

11 comments

7 participants

tags (0)

participants (7)

Andrea Zanni
David Cuenca
Luca Martinelli
Lukas Benedix
Lydia Pintscher
Sven Manguard
Thomas Douillard