all the cross-links between items in the data stewardship mind map to the knowledge model

ds-wizard / ds-wizard

DSW Common Repository

https://ds-wizard.org

17 stars 1 forks source link

all the cross-links between items in the data stewardship mind map to the knowledge model #11

Closed roper79 closed 5 years ago

roper79 commented 6 years ago

[x] Design decision whether we need just a "reference text" or also an "anchor"
[x] Associated changes in the schema
[x] Update the three existing xref links to the new schema
[ ] Rob puts the cross references into the KM, some of them from A->B as well as B->A.
[ ] UI implementation

MarekSuchanek commented 6 years ago

Some quirks:

Links are bi-directional, but there will be one direction in the KM
How to manage the links to unanswered hierarchy of questions?

rwwh commented 6 years ago

On the first quirck, plus details.

It is better to add each bidirectional link twice: from A to B and from B to A.
I will need a reference text: why are you being referred. E.g. "This question deals with creating reference data. For use of reference data, see: "
We could use use "anchor" for this like in "weblink", but it may be better to have the explanatory text itself not be the link, but use a standard icon for a crosslink. This would need to be decided by the UI designer before we can change the KM schema, and only when the KM schema is adapted, I can add the links.

Can we have it in an hour please? ;-)

MarekSuchanek commented 6 years ago

Let's solve this asap, because #62 is being implemented (server is done and client in progress)...

So, we will have just new (optional?) attribute for xref called... "text" or "description"?

rwwh commented 6 years ago

either is fine. Easier not to make it optional, there is always a reason for the link, even if it is "see also" we can make it explicit.

MarekSuchanek commented 6 years ago

Let's work on this here: https://github.com/DataStewardshipWizard/ds-km/pull/21

I updated the schema to include mandatory description of xref. You can now work on this in branch xrefs. In the mean time, the #62 will be adjusted and prepared...

( You've already started :+1: )

rwwh commented 6 years ago

Remark on the second quirck: To solve this, if a question is still closed, the user interface could trace back to a higher level question that has been opened already. We could even make it such that this will be apparent from the way the link is shown: "link to a question that is not yet open" could be shown in a different way as "link to a question that is already open".

Maybe it is also useful for a user to know whether it is a forward or a backward link?