Only Organise Matrices in Library

Follow

Peter Kristensen

• July 25, 2018 04:23

In MooD, when I create a matrix, I need to organise it two different places;

• the element that will own the matrix
• the Matrices group in Libraries

I think this is unnecessarily complex - matrices should only have to be organised in one place.

For matrices that are used on a single element's model, it is helpful that this element owns the matrix. However, for matrices used on model masters and for matrices used on multiple models or model masters, their is no single owner, so having to assign an owner becomes artificial. Also, for matrices that are owned by elements but used elsewhere, there is the risk of accidentally of deleting matrices when deleting the element.

It seems like the concept of matrices having an owning element is a leftover from previous versions where MooD did not have model masters (and perhaps libraries).

I would like to see the concept of matrices having an owning element go away, so matrices will become true library components that only need to be organised in Matrices groups.

As a side note, currently I completely ignore the Matrices groups in Libraries. I only have the default group where matrices are automatically placed when created. In essence, I completely ignore matrices as library components. This is currently the only way of avoiding organising the matrices in two different places.

 

Regards,

Peter

1

• 

  Matthew Dodd

  • July 25, 2018 07:05

  Hi Peter, this is something we've wanted to do for a while!  It's Story 9730 - I've added your text to this story.

  (It's a hang over from the days of static publish)

  Matt.

  0

  Comment actions Permalink
• 

  Peter Kristensen

  • July 25, 2018 07:14

  Hi Matt,

  Sounds good!

  I have mentioned this before, but I have lost track of that was made it to a story and what has been discarded, so I am submitting things here as I encounter them.

  -Peter

  0

  Comment actions Permalink
• 

  Karl Hertz

  • December 03, 2018 07:25

  Just to add my voice to this:

   

  I recognise Peter's story above completely, it's the way we've worked for a number of years (ignore the "library" use only elements). It's even gone so far that we've put all matrices in a special theme which is there only as a way of storing/sorting matrices.

  I want to add two things to this:

  a) The reason we choose to go with a "matrix theme" instead of using the library is the library only allows for one level above the actual matrices. Given the number of matrices we have to handle in a repository, this soon becomes very hard to maintain and people start creating their own matrices instead of reusing as and when they should.

  b) The above problem (i.e. that there's only one level "above" the actual matrices) is also applicable to queries. So whether that is a different user story or not, we would like to be able to sort queries in a more hierachical manner so as to avoid a large number of categories and queries in each of those categories.

  /Karl Hertz

  0

  Comment actions Permalink

Please sign in to leave a comment.