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
    To me this is indeed the hardest part of any kind of document management. And the best meta data structure is always dependant on the specific requirements, so there's no way to give the best solution that would fit everyone. But like you asked, there are some "best practices" that usually lead to good things.

    I assume that you have studied the sample vault, which gives quite good guidelines on the idea of object types and classes.

    So, what I suggest, is that you will provide here your business diagram or other information of your requirements, and we will try to give you ideas how to develop the meta data structure. Let us know if this is OK with you.

    Best regards,
    Samppa
Reply
  • Former Member
    Former Member
    To me this is indeed the hardest part of any kind of document management. And the best meta data structure is always dependant on the specific requirements, so there's no way to give the best solution that would fit everyone. But like you asked, there are some "best practices" that usually lead to good things.

    I assume that you have studied the sample vault, which gives quite good guidelines on the idea of object types and classes.

    So, what I suggest, is that you will provide here your business diagram or other information of your requirements, and we will try to give you ideas how to develop the meta data structure. Let us know if this is OK with you.

    Best regards,
    Samppa
Children
No Data