Have been waiting for a project to come along to try Mayan EDMS, ever since seeing in the Turnkey Linux repo library a couple of years ago. Bought the book last night and skimmed it all, reading the first 55 pages pretty intently. A great resource and I think very intuitive and succinct.
- creating an educational testing document store, where “question” is our basic “document”
- question must have problem_image, question_text_image, answer_choices[0 to 7], correct answer flag
- assets will be created by workers uploading screen clips of problem_image and question_text_image
- I think having editor-specific watch folders can help make that work
- answer choices could be copied / pasted in as metadata by the editor
Because we are translating these questions among different languages AND developing variants of some, Mayan EDMS has many, many workflow features that we think will ROCK for us. That plus we want a system that is professional and Mayan is that.
- our question = a “compound” document in our parlance. What is the Mayan way to say that?
- my first inclination of having everything magically appear in one “document” doesn’t seem feasible
- are we better off having 3 documents, where one = input a, second = input b, and third = combination of a + b + metadata = questions?
Question: What is the Mayan way to approach this problem – I want to orient myself (and the team) properly so we embrace the philosophy and solve this?
Many thanks for thoughts and feedback!