This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Comprehensive manuals or other help to set up Metadata Structure

Former Member
Former Member
Though I always thought that I'm not stupid I have really hard time setting up (rather complex) Metadata Structure.
User guide that I got from M-Files is next to nothing. Unfortunately the help is not better - actually I've never seen worse. M-files offer something (that I doubt would be what I truly need) for "modest" fee of EUR 500+?
Does anybody have advice how to set up Metadata Structure this on budget that does not break my bank account?
What I truly need is the 'best practices' how to use Object Types, in conjunction with Value Lists and Property Definitions in order to get proper Contact type/Contact/Contact Person/Project/Document relationships. So when I select specific Contact type (Client, Prospect, Vendor, ...) only appropriate list of companies appears in Contact property dropdown, and only appropriate list of project names appears in Project property dropdown, and so on. Also how to use Value lists and Sublists - when is appropriate to import values from db, and when enter manually via M-Files client.
Parents
  • Former Member
    Former Member
    100% agree with JasonP, it sounds like we made exactly the same mistakes!

    Looking at others metadata structures will just cloud your solution - make sure you get a good idea of how your users work (they are your stakeholders, and they can make the project impossible to complete if you don't cater to their needs!). User acceptance is a big factor, and they have to understand that it is document management not file storage.

    Don't try to be too clever, keep it simple - a user will typically take the path of least resistance, so will select a class with 5 options over one with 50 if it is quicker for them!

    I would argue that the "Sample" vault is a good starting point for most - just tailor that to meet your needs.

    Paul
Reply
  • Former Member
    Former Member
    100% agree with JasonP, it sounds like we made exactly the same mistakes!

    Looking at others metadata structures will just cloud your solution - make sure you get a good idea of how your users work (they are your stakeholders, and they can make the project impossible to complete if you don't cater to their needs!). User acceptance is a big factor, and they have to understand that it is document management not file storage.

    Don't try to be too clever, keep it simple - a user will typically take the path of least resistance, so will select a class with 5 options over one with 50 if it is quicker for them!

    I would argue that the "Sample" vault is a good starting point for most - just tailor that to meet your needs.

    Paul
Children
No Data