Ticket #34 (closed Feature Request: fixed)

Opened 9 years ago

Last modified 7 years ago

Webclient: Enable "labelling" of an Association resp. "Roles"

Reported by: Malte Owned by: jri
Priority: Major Milestone:
Component: DeepaMehta Standard Distribution Version: 4.0.2
Keywords: Cc: ziegi
Complexity: 8 Area:
Module:

Description

Highly demanded feature for the digiges-transparency use case.

Suggested Default Behavior: A "Role" can has a "Label".

This would allow to store and render simple information as direct part of an association.

Maybe it is also good to think of "Labelled" as parts of a "Role".. resulting in 2 different labels depending from which "Topic" the user is looking at the Association. If then just one "Role" would be labelled, this one label is displayed from both point of views/ topics.

Change History

comment:1 Changed 9 years ago by JuergeN

So your suggestion would result in something like this?


        Label A                              Label B
     ()---------------------------------------------()
   Topic A                                        Topic B 

To me, I think the old version of just one label per association sounds a bit better:


                          Label
     ()---------------------------------------------()
   Topic A                                        Topic B 

Or is this a special requirement for your usecase? Could you add an example of what exactly you want to do with it?

Last edited 9 years ago by JuergeN (previous) (diff)

comment:2 Changed 9 years ago by jri

  • Status changed from new to closed
  • Complexity set to 8
  • Resolution set to duplicate
  • Milestone Release 4.1 deleted

Superseded by #41

comment:3 Changed 8 years ago by Malte

  • Status changed from closed to reopened
  • Resolution duplicate deleted

So, what I had in mind is that DeepaMehta can speak through it's association labels, which is not particular of interest for in-map visualizations, but more for the labels showing up in the page-panel because:

In the page-panel, I've already chosen a focus, I'm at one end of an association looking into the direction of the topic on the other side of this association, thus the role I play in this assocation is my viewport for labelling/expressing relations between 2 topics.

The idea to build on "Role based" labels origins from the topic-map standard (formerley XTM) where a GUI can choose if, for example, they render out of deepamehta a sentence like.

(The opera) "Macbeth" - "was composed by" - "Giuseppe Verdi" or

"Guiseppe Verdi" - "is the composer of" - (the opera) "Macbeth"

depending on the focus a user currently has while navigating the graph.

For in-map visualiations I would probably favour the first of JuergenN's sketch.

The problem with this vision, which could make deepamehta speak, is, additionally there would be just a simple association label needed (for reasons of simplicity), which is not based on labelling both roles. Ideally, both variants will work for users.

comment:4 Changed 7 years ago by jri

  • Cc ziegi added

comment:5 Changed 7 years ago by jri

Meanwhile on the devel-list this approach takes shape: render the association value (as entered in the detail panel) along with the association (as depicted above by JuergeN). The role types would not be involved.

comment:6 Changed 7 years ago by Jörg Richter

Webclient: display assoc labels in topicmap (#34).

In the topicmap the associations are displayd along with their values (as entered in the detail panel when an association is selected).

See #34.

comment:7 Changed 7 years ago by Jörg Richter

Webclient: display assoc labels in topicmap (#34).

In the topicmap the associations are displayd along with their values (as entered in the detail panel when an association is selected).

See #34.

comment:8 Changed 7 years ago by JuergeN

Very good. I like the way the text is allocated along the line and flips sides every 180 degrees. :)
Thank you!

comment:9 Changed 7 years ago by jri

  • Status changed from reopened to closed
  • Resolution set to fixed

Thanks, JuergeN, for feedback!

Note: See TracTickets for help on using tickets.