<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Dear Oddrun,<br>
<br>
thank you for the positive feedback.<br>
I also have many ideas in my head, where this could evolve.<br>
One I am currently intensively working on, is to weave in instance
information,<br>
i.e. to be able to see, which profiles and components are used an
how often..<br>
<br>
Regarding the problem of visibility of the full graph:<br>
True, this is not solved optimally yet.<br>
First, I usually try to play around with the parameters:<br>
lower link-distance and lower charge squeeze the graph together.<br>
When resizing the window, the scroll-bars adjust - sometimes,<br>
unfortunately this is currently inconsistent and rather
frustrating.<br>
Third possibility is to Zoom out the browser (Ctrl -).<br>
Funnily, once you get the whole graph into the picture, when
zooming out, <br>
the scroll-bars seem to adjust correctly, when you then go back to
normal view (Ctrl 0).<br>
Then there is always the possibility of exporting the graph.<br>
By clicking on the download link, you get the pure svg opened in a
separate tab,<br>
where provisions where made, to display the full graph.<br>
You can store this as svg, however you cant interact anymore with
the graph.<br>
Depending on the situation, you could also try to traverse the
graph, <br>
meaning you select the last nodes visible, and deselect the
originally selected ones.<br>
This way, the graph should move to the left.<br>
And final possibility: bigger screen ;)<br>
<br>
Hope this helps a bit.<br>
<br>
Matej<br>
<br>
<br>
<br>
Am 28.08.2013 10:08, schrieb Oddrun Ohren:<br>
</div>
<blockquote
cite="mid:2824833243E5EA4CBC49C60421B8B7BC4047E433@NB-MAIL3.nb.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Ren tekst Tegn";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.RentekstTegn
{mso-style-name:"Ren tekst Tegn";
mso-style-priority:99;
mso-style-link:"Ren tekst";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1901207860;
mso-list-type:hybrid;
mso-list-template-ids:199133862 68419585 68419587 68419589 68419585 68419587 68419589 68419585 68419587 68419589;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoPlainText">Hi Matej,<o:p></o:p></p>
<p class="MsoPlainText"><span lang="EN-US">Thanks for the new
version! As I have said before, I find your tool highly
informative and helpful. It also visualizes very clearly
some of the problems with CR as it is today, notably the
many duplicate or near-duplicate components and elements. I
also think that a controlled vocabulary for domains (of
profiles) could make the profile-domains graph really
helpful. Introducing a similar attribute for components
(something like “described object” with an accompanying
vocabulary/ontology) would make the foundation for a
corresponding graph <i>component-described object.</i> That
way, it would be easy to detect components which describe
persons, for example, without having to rely on them being
called “person-“ something or other.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">With further
development, I think CMD Browser could become a
<u>CMD analysis and management tool</u>. For this we would
need facilities like<o:p></o:p></span></p>
<p class="MsoPlainText"
style="margin-left:36.0pt;text-indent:-18.0pt;mso-list:l0
level1 lfo1">
<!--[if !supportLists]--><span style="font-family:Symbol"
lang="EN-US"><span style="mso-list:Ignore">·<span
style="font:7.0pt "Times New Roman"">
</span></span></span><!--[endif]--><span lang="EN-US">profile/component
comparison (e.g. compare selected components in terms of
overlap, inclusion, etc. Relations to investigate must of
course be clearly defined), with textual/tabular report<o:p></o:p></span></p>
<p class="MsoPlainText"
style="margin-left:36.0pt;text-indent:-18.0pt;mso-list:l0
level1 lfo1">
<!--[if !supportLists]--><span style="font-family:Symbol"
lang="EN-US"><span style="mso-list:Ignore">·<span
style="font:7.0pt "Times New Roman"">
</span></span></span><!--[endif]--><span lang="EN-US">detect
profiles/components/elements which are similar to a given
component ("similar" defined partly by user, e.g. "includes
>= 80 % of the same DCs")<o:p></o:p></span></p>
<p class="MsoPlainText"
style="margin-left:36.0pt;text-indent:-18.0pt;mso-list:l0
level1 lfo1">
<!--[if !supportLists]--><span style="font-family:Symbol"
lang="EN-US"><span style="mso-list:Ignore">·<span
style="font:7.0pt "Times New Roman"">
</span></span></span><!--[endif]--><span lang="EN-US">...and
more. We would have to think more about this…<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Even further down the
line, perhaps a <u>
graphical modeling tool </u>could evolve, allowing the
metadata modeler to create/update profiles by
dragging/dropping components, elements and data categories
on to a graphical canvas.<o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><u><span lang="EN-US">Back to the
current version:</span></u><span lang="EN-US"> Using
Chrome, I have a little trouble with graphs extending past
the window borders. The scroll bars don’t seem to cover the
whole canvas. Any attempt to manually move the nodes is
undone by the automatic layout mechanism. I tried freeze,
but then I still can’t get hold of the nodes outside the
accessible part of the canvas. Anything else I could have
done, apart from using the layout parameters in the top
bar?). <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US">Best regards,<br>
Oddrun <o:p></o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoPlainText"><span
style="mso-fareast-language:NO-BOK">-----Opprinnelig
melding-----<br>
Fra: Matej Durco [<a class="moz-txt-link-freetext" href="mailto:xnrn@gmx.net">mailto:xnrn@gmx.net</a>] <br>
Sendt: 27. august 2013 19:42<br>
Til: CLARIN EU developers; Oddrun Ohren<br>
Emne: SMC Browser - update</span></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Dear all,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">there is an updated version of the SMC
Browser available (under the old<o:p></o:p></p>
<p class="MsoPlainText">address):<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><a moz-do-not-send="true"
href="http://clarin.aac.ac.at/smc-browser/"><span
style="color:windowtext;text-decoration:none">http://clarin.aac.ac.at/smc-browser/</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Besides freshly fetched data, there are
also some new features and fixes:<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">* profiles that are still private, but
already have instance data exposed have been also processed,
making it altogether 154 available profiles.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">* introduced new type of nodes:
*profile-groups*<o:p></o:p></p>
<p class="MsoPlainText"> based on profile metadata:
creatorName, groupName and domainName<o:p></o:p></p>
<p class="MsoPlainText"> virtual nodes (for each distinct
value of the three fields) are being generated and linked with
appropriate profiles.<o:p></o:p></p>
<p class="MsoPlainText">so now it is easy to see which profiles
are grouped together or who created which profile (i hope the
authors dont mind being dots in a graph - aren't we all just
tiny dots in a giant graph after all ;) )<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"> especially there is a dedicated group
for profiles, that are not<o:p></o:p></p>
<p class="MsoPlainText"> public yet: "unknown-profile"<o:p></o:p></p>
<p class="MsoPlainText"> you can inspect directly under:<o:p></o:p></p>
<p class="MsoPlainText"><a moz-do-not-send="true"
href="http://clarin.aac.ac.at/smc-browser?graph=/smc/data/smc-graph-groups-profiles-datcats-rr.js&depth-before=1&depth-after=1&link-distance=120&charge=594&friction=75&node-size=4&labels=show&curve=straight&layout=horizontal-tree&selected=profile_group_unknown_profile&"><span
style="color:windowtext;text-decoration:none">http://clarin.aac.ac.at/smc-browser?graph=/smc/data/smc-graph-groups-profiles-datcats-rr.js&depth-before=1&depth-after=1&link-distance=120&charge=594&friction=75&node-size=4&labels=show&curve=straight&layout=horizontal-tree&selected=profile_group_unknown_profile&</span></a><o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">* it is now possible to select different
graphs (param: graph)<o:p></o:p></p>
<p class="MsoPlainText"> currently 4 different ones are
available:<o:p></o:p></p>
<p class="MsoPlainText"> 1. the basic one (profiles ->
components -> elements -> datcats)<o:p></o:p></p>
<p class="MsoPlainText"> 2. additionally rendering the new
profile-groups and relations between data categories (from
Relation registry)<o:p></o:p></p>
<p class="MsoPlainText"> 3. just rendering profiles and data
categories (with direct links between those, skipping all
components and elements<o:p></o:p></p>
<p class="MsoPlainText"> 4. as 3. but again with
profiles-groups and relations<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">3. and 4. are good to better inspect
profile-proximity<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">* all data categories should be resolved
now.<o:p></o:p></p>
<p class="MsoPlainText"> (in the previous version many datcats
had no definitions fetched from<o:p></o:p></p>
<p class="MsoPlainText">isocat)<o:p></o:p></p>
<p class="MsoPlainText"> I also encountered quite a few
concept-links with leading space, and other inconsistencies. I
will soon provide a list of the affected CMD-elements,
perhaps, we can clean this up in the Component registry...<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">* the (statically generated) dataset
(especially the statistics) are getting quite big, so it may
take a bit until everything is loaded.<o:p></o:p></p>
<p class="MsoPlainText">a more dynamic version sending around
smaller chunks of data is scheduled. meanwhile I have to ask
you for patience.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">I hope you like it.<o:p></o:p></p>
<p class="MsoPlainText">looking forward to feedback.<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">best,<o:p></o:p></p>
<p class="MsoPlainText">matej<o:p></o:p></p>
</div>
</blockquote>
<br>
</body>
</html>