Make "Show where used" exportable



  • Official comment
    Jessica Robinson

    Thank you for the above request and feedback Karl, I see the value here.  We will look into this and see what the possible options are and how/where it would fit into the backlog.

    I will keep you updated.

    Kind regards


    Product Owner

    Comment actions Permalink
  • Avatar
    Giles Middleton

    (Non committal discussion) 

    So if we follow idea (1) I'm assuming here

    • you'd use a tool like WinMerge, WinDiff, BeyondCompare to do a like-for-like difference view of the two outputs. Or would it be visual inspection?
    • you'd probably just need MooD ID, type and name
    • a deterministic order, possibly excluding date modified/created so the difference is easy

    Format could be CSV or XML, or if it needs to be pretty then you want HTML but it might be less easily comparable with difference-tools.

    Of course, there may be other ways of doing this with more helpful UI and selecting the repository to compare against, or even doing something with deployment packs. 

    Option (2) is probably something that the product does need to help users expose the meta model in general, but is a lot more difficult than (1).


    Comment actions Permalink
  • Avatar
    Karl Hertz

    Hi Giles

    Caveat noted :)

    • For what I am trying to do "visual inspection" is not the key goal but it is closer than the tools you are listing (with less than a stellar understanding of what all of those do). What I want is something is something I can look at outside of MooD and transfer into other formats (e.g. excel) so that I can easily add my own data (i.e. do I keep the thing listed in "Show where used" or should it be removed, justification for that). So "visualisation + ability to add information", basically.
    • MooD ID, type, name, which element the meta-element is on (for matrices) and possibly (and this would be icing on the cake) "referred things" from the element/meta element (i.e. is something else using this thing I am seeing from "show where used") and "Used in" (i.e. the result from "show where used", without all the frills listed above). The two "icing on cake" things are to have a better understand of what manipulating a thing would mean (what could I destroy if I started tampering with things?).
    • Yes, deterministic order, please.

    So long as those CSV or XML are easy to put into e.g. excel that'd be ok. The HTML I suggested because it might be easier to communicate around something which looks nicer, but I ultimately feel it would be fairly easy to transfer any table in HTML to excel when the day comes to get your hands dirty and start making determinations based on the data and loging those determinations somewhere.

    As for other ways of doing this - maybe. What I am after is analytical tools and the ability to make decisions on information based in one repository (which has content and structure, but only owns the content) for what is in another repository (which only has the structure, but which owns/is master data for that structure). I think I could dream up something fancy in this regard but honestly, this is something I think we need to do fairly seldom so just a toolset which allows us to get the information out easily to start manipulating it ourselves is good enough (as opposed to an "all bells and whistles" option which we would rarely use). Of course, the use case could be different for other MooD users (which I haven't factored in for obvious reasons).

    I recognise option 2 to be a fair amount more difficult - but, as you say, it could have other uses beyond what I am after here and so might therefore be a better way to resolve the issue in the long run.

    Hope that helps :)

    Comment actions Permalink

Please sign in to leave a comment.