For alternative interfaces that include editing capabilities, see also my demo here: https://tools.wmflabs.org/reasonator/widee/#q=Q42
(this one is optimized for load speed and readability, but it's been around for a while, so no guarantees...) On Tue, May 3, 2016 at 1:27 PM Markus Kroetzsch < [email protected]> wrote: > Hi David, > > Reasonator has done a lot of pioneering work in this area. We are > copying some of it in SQID (and adding own modifications). In general, > these projects could be nice playgrounds for experimentation here. If > you have suggestions on how to improve these UIs, they are very welcome. > > I believe Reasonator is grouping properties by built-in rules, whereas > SQID is using certain property-classes (P31 on Property pages), where > this is available. One could experiment with further approaches or > switches ... > > Markus > > > On 03.05.2016 13:52, Lydia Pintscher wrote: > > On Tue, May 3, 2016 at 1:08 PM David Abián <[email protected] > > <mailto:[email protected]>> wrote: > > > > Hi, > > > > I think that most elements on Wikidata are nowadays too long to be > > easily read by humans. There are many properties (which is great), > the > > information is too scattered, and this problem (if you consider it a > > problem) will continue growing up. > > > > Some suggestions come to mind... > > > > * Visually group properties by type, using the division of > > <https://www.wikidata.org/wiki/Wikidata:Property_proposal>, or > another. > > > > * Change our current CSS rules to show properties in a more > > compacted way. > > > > * Create a table of contents that automatically appears when more > than N > > properties have been defined for an element. > > > > * Combine some of the above. > > > > Is there something discussed/planned facing this issue? > > > > > > > > Hi David, > > > > Yes this is a problem I already identified. We've worked on it as well > > already. As a first step we improved the loading time of large items. As > > the next step we have moved identifiers into their own section. This > > already helped a lot by removing identifiers from the rest of the > > statements where they were mostly clutter. We have also made a few small > > UI tweaks to improve the spacing. The next step is going to be ordering > > of statements. For that we have to do some groundwork and then community > > input. I hope we can start with that in the next 2 months. > > To summarize: Being worked on but it is an on-going task that will be > > with Wikidata for a long time as it grows. > > > > > > 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 <http://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/029/42207. > > > > > > _______________________________________________ > > Wikidata mailing list > > [email protected] > > https://lists.wikimedia.org/mailman/listinfo/wikidata > > > > > -- > Markus Kroetzsch > Faculty of Computer Science > Technische Universität Dresden > +49 351 463 38486 > http://korrekt.org/ > > _______________________________________________ > Wikidata mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/wikidata >
_______________________________________________ Wikidata mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata
